Privacy Policy
Last updated: 12 October 2026 · Pre-launch draft
1. Scope
This draft covers browsing the website, account registration and sign-in, and the test checkout. It does not describe the full data processing of future VPN apps, gateways or live payment providers.
An account number alone does not mean that no data is processed. We do not make a blanket zero-logs claim in this draft.
2. Account data
| Category | Data stored |
|---|---|
| Account | Internal account ID, keyed hash of the secret account number, creation date and disabled status. |
| Subscription | Any subscription linked to the account. |
| Session | Hashed session token, associated account, creation and expiry timestamps. |
The secret account number is not stored as readable text.
When you register or sign in, the account service processes the number to authenticate you. Session records link a hashed session token to the account and include creation and expiry timestamps.
3. Session cookie and request information
The hp_account_session cookie keeps you signed in. It is an HttpOnly session credential with a seven-day validity period and SameSite=Strict. Logging out removes the corresponding active session record.
Web servers necessarily receive connection information such as the source IP address and HTTP request headers. The account API uses client addresses in memory to limit repeated authentication attempts. Hosting and infrastructure logging must be reviewed and described in the final notice.
The current website does not load third-party advertising or analytics scripts.
4. Test checkout and external links
Your entered email address and payment-method choice stay in the current checkout interface. Continue does not send or persist them, create a payment or send a receipt. Real payment processing will require an updated notice identifying the relevant providers and data flows.
Support, news and community links open Telegram. Information you choose to send there is handled by Telegram and the recipients. Do not post your account number in the community chat.
5. Retention
Expired account sessions are removed by background cleanup; the seven-day authentication validity is not a promise that every expired database row is deleted at that exact instant.
Account records currently have no automatic deletion deadline. The final notice must define account retention, deletion procedures, backup retention and any legal obligations before public launch.
6. Questions and items to complete
For current project questions, contact @highpriority_bot. The operator's legal privacy contact remains to be specified.
The launch-ready notice must identify the controller and contact details, purposes and lawful grounds, recipients and processors, storage countries and transfer safeguards where relevant, retention periods, and the process for exercising applicable access, correction, deletion and other rights. This draft does not establish that process.