PRIVACY_PROTOCOL

We collect minimal operative metadata required for mission success. This includes your chosen Operator ID and Network Uplink (IP Address). No biometric or persistent personal identifiers are harvested.

To maintain the integrity of the BIT-SEC-CON mainframe and CTF environments, we monitor Network Uplinks for unauthorized intrusion attempts or automated scripts. This data is used solely for Anti-Cheat detection and real-time defensive mitigation.

Your data is held in a volatile secure buffer. In compliance with our security mandates, all anti-cheat logs and temporary profile metadata are permanently purged from our systems within 24 hours of the final conference transmission.

All transmissions between your local terminal and our servers are protected by AES-256-GCM encryption (SSL/TLS). Unencrypted handshakes are automatically rejected by our firewall.

We utilize external nodes for specific mission-critical functions: Luma (Logistics) and YouTube (Signal Transmission). These nodes operate in isolation; we do not share your internal BIT-SEC-CON telemetry with them.

BIT-SEC-CON maintains a Zero-Tracker Policy. We do not utilize third-party analytics scripts or marketing pixels. Your activity on our network is not tracked for advertising purposes.

Your Operator ID is temporarily retrieved from the buffer at the end of the conference to generate your Cryptographic Certificate of Attendance. Once the PDF is generated, this data link is severed.