Who is responsible
BiTTU VPN is the product brand, powered by BITTU ICLOUD. The legal operator, contact address and applicable jurisdiction have not yet been confirmed for a public VPN service. Planned privacy contact: privacy@bittuvpn.com. Email routing is pending; use the signed-in support form for a request that is stored in the operator queue.
Website and account records
Hosted sign-in provides a site-specific user identifier, email and display details. We use these to associate your device requests and support conversations with your account. Device requests contain a name, platform, chosen country and WireGuard public key. Never submit a private key, password or payment details.
Support and operator records
The application stores support subjects, categories, messages, operator replies and request states in its hosted database. Operator records include planned nodes, public endpoints and keys, coarse heartbeat reports, draft plans, release notes, policy edits and audit events. These records support the workflows shown in the dashboard; they do not establish that a gateway peer has been activated.
Local preferences and hosting
Theme and favorite-country preferences are stored in your browser. Hosted authentication can use session technology. This build includes no advertising or analytics SDK. The hosting and authentication services may process operational request metadata under their own service arrangements. Hosting locations, processor details and retention procedures must be reviewed before launch.
VPN activity and reference data
The website does not create a device-wide VPN tunnel. No public BiTTU gateway is deployed. Country, timezone, protocol and vulnerability reference records are external public datasets, not customer browsing data or BiTTU exit servers. A gateway operator controls its own host/network logs; no independently audited no-logs claim is made.
Requests and retention
Use the Data request category in your signed-in account to request access, correction or deletion review. Submission creates an operator review request; it does not automatically delete all records. No universal retention deadline is promised here. Before public launch, the operator must establish and publish appropriate retention, verification and deletion processes.