What gets written down, and what never does

Every statement below matches a setting on the running server rather than a promise about the future.

Sites and addresses

The connection journal on the server is fully disabled. After your session the log file stays empty — you can see that with your own eyes, we show it on request.

Name server queries

Not recorded: the separate name-logging setting is switched off.

Your address when fetching settings

The web server that hands settings to your app keeps no access journal. Repeated requests create not a single line.

Device fingerprint

We do not enforce device limits, so your phone model and identifier are of no use to us. The table is cleared automatically every night.

What we keep and why

Account

Account name, subscription expiry, link to your settings. Without these we cannot connect you or remind you in time to renew.

Traffic volume

How many gigabytes passed through the account. We need it to see how loaded a server is and add capacity before it hurts. Not one address and not one per-site timestamp lives in that data.

Contact

Whatever you gave us to reach you — email or Telegram. Used for support and service notices only.

Payments

We keep a payment identifier from the payment provider. Card details never reach our servers at all.

What no provider can promise

Hosting

The datacenter sees the volume of network traffic reaching the server. That is how networks are built, and claims to the contrary are untrue.

An open connection

While a connection is live, details of it exist in the server's memory, otherwise the tunnel could not function. They are never written to disk and vanish when the connection closes.

Jurisdiction

Servers are in Estonia, inside the European Union, and we answer lawful requests. What we can hand over is limited to the list above: an account name, an expiry date, a traffic total. Browsing history does not exist on our side to be handed over.

Back home