Privacy by architecture

What Vazie sees—and what it cannot.

This is a readable product overview, not a legal privacy policy. A formal policy will be published before the first release.

CUSTOM PATH

Vazie learns nothing

  • No account required
  • No contact with Vazie infrastructure
  • Secrets encrypted on device
  • Traffic goes to your server
ACCOUNT / MANAGED PATH · LATER

The minimum needed for service

A future service will need account, session, entitlement, and operational records. Fields and retention periods remain TBD; this path is not live.

Vazie never collects

Browsing history, DNS queries, visited domains, destination addresses, traffic contents, raw configurations, keys, passwords, subscription URLs, advertising or hardware identifiers, precise location, or contacts.

Analytics

Product analytics is opt-in and off by default. This website includes no analytics, so it needs no cookies or consent banner.

An important boundary

Vazie is responsible for what Vazie does. The operator of your own VPN server sees what a VPN operator normally can; our guarantees do not extend to them.

Full document

There is no legal policy before release. The canonical technical model lives in the repository and will be the source for the future policy.