Privacy Policy

doxx.net corp, a Delaware corporation
Version 2.0 • Effective date: February 7, 2026

1. Our Commitment

doxx.net was built from the ground up with a single purpose: to protect the privacy and freedom of our users. This is not a marketing statement. It is an engineering decision embedded in every layer of our infrastructure.

We operate a fully vertical technology stack. We do not rely on third-party services for any core function of the platform. Every component, from our DNS resolvers to our authentication system, from our human verification to our network routing, is designed, built, and operated in-house by doxx.net engineers. This means no third party ever touches your data, because no third party is involved.

2. Vertical Infrastructure: No Third Parties

Unlike other privacy services that depend on external vendors, doxx.net owns and operates:

  • Our own autonomous network – We operate our own BGP-peered network across 20+ global points of presence. Your traffic never passes through a third-party VPN provider.
  • Our own DNS infrastructure – We wrote our own DNS resolver from scratch in Go. We do not use BIND, Unbound, or any public DNS software. Our DNS servers are custom-built, purpose-designed, and run on our own anycast network.
  • Our own human verification (DOXX POW) – We do not use Google reCAPTCHA, Cloudflare Turnstile, hCaptcha, or any third-party verification service. Our proof-of-work system runs entirely on our servers with zero external API calls.
  • Our own authentication system – Token-based, no passwords, no email required. No Auth0, no Firebase, no Okta. Globally isolated private authentication infrastructure built in-house.
  • Our own monitoring and statistics – No Google Analytics, no Mixpanel, no Datadog, no Sentry. Our real-time monitoring system is custom-built and stores data only in volatile memory.
  • Our own certificate infrastructure – Self-signed certificates with client-side pinning for transport security, eliminating dependency on public certificate authorities for core VPN operations.
  • Our own encrypted mesh network – All doxx.net servers are interconnected via a private WireGuard mesh backbone. User-to-user traffic (such as VoIP calls, messaging, or any peer-to-peer communication between doxx.net users) travels entirely over this encrypted mesh and never exits to the public internet. Even if two users are on different continents, their traffic stays within our private network.

The only external service involvement is Apple App Store for iOS subscription payment processing. We do not associate Apple payment records with VPN activity.

3. No-Logs Policy

We do not collect, store, monitor, or log:

  • Browsing history or website visits
  • DNS queries or resolutions
  • Connection timestamps, duration, or frequency
  • Real IP addresses (source IPs are never stored; see Section 6)
  • Bandwidth usage per user
  • VPN session metadata
  • Any content of your communications
  • User agent strings or device fingerprints

We have no ability to associate network activity with any individual user. This is not a policy choice. It is an architectural reality. The systems are not built to capture this data.

4. What We Collect

We collect the minimum data necessary to operate the Service:

  • Account token: A randomly generated authentication string. No email address, no username, and no password is required to create an account.
  • VPN tunnel configuration: WireGuard public keys and internally assigned VPN IP addresses. These are internal network addresses used for routing, not your real IP address.
  • Feature preferences: Your settings such as DNS blocking configuration, firewall rules, location spoofing preferences, and transport options. These are configuration choices you make, stored to persist your settings.
  • Optional recovery information: If you voluntarily provide an email address or phone number for account recovery, it is stored. Most users do not provide this.
  • Recovery codes: Stored as one-way cryptographic hashes. The original codes cannot be recovered from storage.
  • Subscription data: For iOS subscribers, Apple's original transaction ID and subscription status are stored for seat management. This data is not linked to VPN activity.
  • Terms of Service acceptance: A record that you accepted the terms, and when. No IP address or device information is recorded.
  • Custom DNS domains: If you register a .doxx domain on the parallel internet, the domain name and ownership are stored.
5. Security Dashboard & Statistics (Opt-In Only)

If you choose to enable security statistics, the following data is processed to power your real-time security dashboard:

  • Blocked domain names and security events are held in volatile RAM (server memory) only. This data is never written to disk and is permanently lost if the statistics server restarts or is interrupted.
  • Data is organized into time-series buckets (1-second through 6-hour windows) for your dashboard visualizations.
  • All data is keyed to a tokenized tunnel reference, not to your identity. The token is an opaque identifier with no connection to your real name, email, or IP address.
  • This data is available only to your authenticated session via an encrypted WebSocket connection. No one else can access your dashboard data.
  • It is not shared with any third party or used for any purpose other than displaying your personal security dashboard.

If you enable bandwidth statistics, upload and download byte counts are processed in the same volatile, in-memory manner described above. No per-user bandwidth records are written to disk.

6. IP Address Handling

doxx.net does not store real IP addresses anywhere in our systems.

  • TOS acceptance: No IP address or user agent is recorded.
  • Human verification (DOXX POW): A one-way SHA-256 hash of your IP is temporarily stored for abuse prevention. This hash cannot be reversed to obtain your actual IP address. Challenge data expires and is automatically deleted within one hour.
  • VPN tunnel IPs: The IP addresses stored in your tunnel configuration are internally assigned VPN addresses (e.g., 10.x.x.x), not your real public IP address.
  • Server logs: We do not log client IP addresses in application logs.
7. Connection State

We maintain a record of whether your VPN tunnel is currently active and which server it is connected to. This is operational data used for load balancing and service health, not a connection log. Only the current state is stored; no history of connections is maintained. When your tunnel disconnects, the status is updated to reflect that.

8. Cookies & Web Tracking

The doxx.net portal uses session cookies for authentication only. We do not use:

  • Analytics trackers of any kind
  • Advertising pixels or retargeting tags
  • Third-party scripts that phone home to external servers
  • Fingerprinting libraries
  • Any form of cross-site tracking
9. What We Never Do
  • We never sell, rent, license, or share user data with any third party.
  • We never serve advertisements or participate in ad networks.
  • We never use third-party analytics or monitoring services.
  • We never inject content, headers, or tracking into your traffic.
  • We never cooperate with data brokers.
  • We never retain data beyond what is described in this policy.
10. Legal Requests

We may receive legal requests for user data. Because we do not log user activity, we have no traffic data, browsing history, DNS queries, or connection metadata to provide in response to such requests. Our architecture ensures we cannot produce records that do not exist. We will comply with valid legal process to the extent we are able, which in practice means confirming whether an account token exists and when it was created.

11. Data Retention
  • Account data: Retained while your account is active. Upon account deletion, all associated data is permanently removed from our database cluster across all nodes.
  • DOXX POW data: Expires and is automatically deleted within one hour.
  • Security dashboard data: Exists only in volatile RAM. Lost permanently on server restart. Not recoverable.
12. Children's Privacy

The Service is not directed at children under 13. We do not knowingly collect data from children under 13.

13. Changes to This Policy

We may update this Privacy Policy periodically. The effective date at the top indicates the most recent version. Continued use of the Service after changes constitutes acceptance.

14. Verification

This privacy policy was verified against the doxx.net production codebase, database schema, and server infrastructure by an independent AI code audit (Claude Opus 4.6, Anthropic) on February 7, 2026. The audit reviewed the database schema, all APIs and source code, the DNS resolver, the statistics server, and the human verification system to confirm that the statements in this policy accurately reflect the system's actual data handling practices.

15. Contact

For questions about this Privacy Policy, please contact us at: legal@doxx.net