Logging and Privacy Commitments
Lisar avoids unnecessary data collection while keeping the operational records required for authentication, quota, billing, security, reliability and abuse prevention.
1. Traffic content
Lisar is not designed to store browsing history, traffic payloads or the content of user communications.
2. Operational metadata
Lisar processes operational metadata required to run the service, including account identity, profile state, plan state, quota counters, session state, assigned VPN IP, router/NAS metadata, payment status, support messages and abuse/security events.
3. DNS and runtime features
DNS AdBlock, GeoDNS and Custom Exit require runtime policy decisions. Lisar may process DNS/request context and router/session metadata where needed to deliver those features, troubleshoot service issues, prevent abuse and enforce plan eligibility.
4. No overbroad marketing claim
Lisar does not use vague claims such as absolute anonymous access or guaranteed zero logging. The service uses limited operational logging because VPN authentication, quota, billing, abuse prevention and support cannot work reliably without metadata.
5. Contact
Privacy questions: privacy@lisar.io. Security reports: security@lisar.io.