Privacy policy
Last updated: 2026-09-27
Pending legal review.What is stored
The account email, a password hash held by the identity provider, the subscription and its quota counters, wallet and ledger rows, and payment records. Each of these is append-only: a change adds a row, it does not rewrite history.
What is not stored
No browsing history, no destination domain list, no packet payload. Traffic counters are aggregated per subscription and per node, not per site visited.
Cookies
The console sets one httpOnly session cookie after sign-in. This site sets no cookies before consent, and no third-party font, CDN or analytics request is made on first load.
Devices
To enforce the plan's device limit, nodes report an opaque per-device key (a hash) with the time it was seen. It is used for that limit and nothing else.
Retention
Ledger, order and audit rows are kept for accounting and dispute handling. Traffic counters age out with the monthly usage partitions. Deleting an account is handled by erasure, not by rewriting history.
Contact
Privacy questions go to the operator address published in the console under Settings, or to the operator who invited you.