BEX Strict Zero-Logs Privacy Policy & Data Handling Specifications

1. Overview & Zero-Logs Core Philosophy #

The BEX platform is architected under the strict legal and technical framework of Privacy by Design and Zero-Logs enforcement. Operating exclusively on a diskless, RAM-only server infrastructure, BEX ensures that no personally identifiable information (PII), connection telemetry, source/destination IP pairings, or browsing activities are ever written to permanent storage. This specification outlines the legally binding privacy guarantees, data handling rules, and system boundaries protecting master distributors, resellers, and end-users.

2. Explicit Non-Logging Commitments #

BEX explicitly commits, both legally and cryptographically, that the following data categories are NEVER recorded, logged, stored, or analyzed across any portion of the BEX network architecture:

• No Source or Assigned IP Logging: Real incoming IP addresses of users and assigned egress IP addresses are strictly volatile and never written to logs.
• No Connection Timestamps: Connection establishment times, disconnect timestamps, and total session durations are completely omitted from system records.
• No Browsing & DNS Telemetry: Destination domain names, visited URLs, DNS query histories, and application-layer protocols are never intercepted or recorded.
• No User-Mapped Traffic Metadata: Bandwidth consumption is metered strictly in aggregate byte counts via eBPF maps without associating volume data with individual IP addresses or real identities.
• No Packet Payload Retention: Deep Packet Inspection (DPI) payload content, TCP/UDP headers, and metadata logs are never captured or archived.

3. Technical Ephemerality & Operational Data Isolation #

To conduct real-time user authentication and token accounting without compromising user privacy:

• Volatile RAM Handshakes: Session handshake parameters exist solely within volatile system memory (RAM) and are permanently purged the millisecond a connection terminates.
• Cryptographic Decoupling of Billing & Network: The BEX token accounting ledger operates on dedicated, logically isolated database clusters completely segregated from edge gateway nodes. A network session token cannot be linked back to a reseller’s payment method or personal identity.
• Zero Cross-Session Identifiers: Network sockets do not assign static client IDs, preventing longitudinal traffic profiling or cross-session user tracking

4. Independent Verification & Warrant Canary #

To provide verifiable proof of adherence to these privacy commitments beyond written legal text:

• Independent Third-Party Audits: BEX undergoes periodic source code and infrastructure audits conducted by independent cyber-security firms to verify that logging daemons are permanently disabled (/dev/null routing) and servers operate in RAM-only mode.
• Cryptographic Warrant Canary: BEX publishes a weekly PGP-signed Warrant Canary confirming that no secret subpoenas, gag orders, data extraction requests, or government backdoors have been received or installed.

5. Key Strategic & Legal Benefits #

• Complete Immunity to Subpoenas: Technical inability to produce data logs provides absolute protection against third-party discovery orders and legal demands.
• Global Regulatory Alignment: Full compliance with international privacy mandates, including EU GDPR, California CCPA, and global ePrivacy directives.
• Uncompromising Whitelabel Trust: Provides B2B partners and resellers with ironclad privacy credentials to offer their end-client networks.