In short
We store what billing and abuse handling require — timestamps, byte counts, destination hosts — and nothing of what passes through the tunnel. Request bodies and response payloads are never written to disk.
1. What we collect
We collect three categories of data and nothing else:
- Account data: the email address, company name and billing details you provide
- Connection metadata: timestamp, gateway, exit country, bytes transferred and destination hostname for each session
- Site analytics: aggregate page counts with no cookies and no cross-site identifiers
2. What we never collect
Request bodies, response payloads, headers beyond what routing requires, and the content of any page you retrieve are not logged, buffered to disk, or inspected. Traffic terminates in memory and is forwarded.
3. Why we hold it
Connection metadata is required to produce accurate invoices, to answer support questions about a specific failed session, and to identify accounts that breach the acceptable-use terms.
4. Retention
Connection metadata is kept for 30 days, then aggregated into daily totals and the per-session records are deleted. Invoices are retained for seven years as tax law requires. Account data is deleted within 30 days of account closure.
5. Sharing
We share data with our payment processor to take payment, and with hosting providers that run our infrastructure. We do not sell data and we do not share it for advertising.
We disclose data to law enforcement only on receipt of a valid legal order from a jurisdiction that applies to us, and we notify the affected customer unless the order forbids it.
6. Your rights
You can request a copy of your data, correct it, or ask for deletion by emailing us. We respond within 30 days. If you are in the EEA or UK, the lawful basis for processing connection metadata is our legitimate interest in billing accurately and preventing abuse.
7. Cookies
This marketing site sets no cookies and loads no third-party scripts. The customer dashboard uses a single session cookie that is strictly necessary for authentication.
Questions about this document? Email [email protected].