What we keep about you
About your account: your email address, whether and when you verified it, your password turned into an argon2id hash (never in the clear), your name if you give one, your language, which version of these terms you accepted and when, and the two-step verification secret if you enable it. If you sign in with Apple or Google we store the identifier that provider gives us instead of a password. For security we also store the failed sign-in counter and how long the account is locked.
About each device: the alias you choose, the platform, the OS and app version, the WireGuard public key, the internal address we assign it inside the VPN, an install identifier that lets us recognise a reinstall on the same device, and when it was last seen, to the hour. We identify devices by that alias and identifier, not by serial numbers or advertising identifiers.
About your settings: kill switch, auto-connect, local network access, protocol, DNS mode and the DNS server you set if you choose your own, the list of apps you decide to exclude from the tunnel (only the package identifier you tick), theme, language, and which notices you want. Plus the push notification token if you enable them.
About your connections: for each tunnel session we store which of our servers it went to, when it started and ended, why it ended, how many bytes went up and down, and the measured latency. Yes: that is a dated list of your sessions, and we keep it for 30 days in order to bill, support you and detect abuse. What is not in that list is where you connected to.
About your billing: the plan, subscription status and period, invoices with amount, currency and tax, and the identifying details of the payment method the gateway returns to us (brand, last four digits and expiry). The full card number never passes through our servers.
About support: the messages and tickets you write to us, and the diagnostics you choose to send (protocol, MTU, operating system, connection type and the tunnel’s latest incidents).
About telemetry: nothing, unless you turn it on yourself. Analytics, crash reports and performance metrics ship switched off and there is a toggle in Settings. If you enable them, the data is processed by Google Firebase. We do not use an advertising identifier.