Our infrastructure is designed as a security fortress. We prioritize **Data Minimization** to ensure that your private life remains private, even in the event of external cyberattacks.
We do not store traffic logs. All persistent routing data is wiped at the kernel level using /dev/null.
We collect the bare minimum required to maintain a stable, resilient service and to ensure we can rebuild our infrastructure in the event of a ransomware attack or critical failure.
| Data Point | Status | Purpose |
|---|---|---|
| Activity Logs | NOT COLLECTED | We never log websites, IPs, or data content. |
| Usernames | COLLECTED | An Alias for account login and disaster recovery. |
| Email Address | OPTIONAL | Only required for password recovery. |
| Subscription Dates | COLLECTED | Used for billing cycles and active account status. |
Note on Recovery: If you choose not to provide an email, we have no way to verify your identity. If you lose your password, your account and subscription cannot be recovered. This is a security feature by design.
To protect our users from catastrophic service loss, we maintain a secure, database of account metadata (Usernames and Billing Status). This ensures that if our infrastructure is targeted by ransomware or hardware failure, we can restore service to our paying members without compromising their browsing privacy.
We do not sell data. We do not use trackers, pixels, or intrusive analytics. We utilize secure, industry-standard payment gateways for Bitcoin and Monero processing. These gateways are isolated from our VPN tunnels to prevent any correlation between your financial identity and your web traffic.