1. Information Collected

No cookies, analytics, or third‑party trackers are implemented. All sessions occur through Tor routing and ephemeral RAM instances with automatic flush. No IP addresses or request headers are stored beyond runtime memory.

2. Transmission Security

All communications between client and Kerberos Onion servers use native Tor encryption and optional PGP message exchanges for user‑initiated support. Content integrity is verified by SHA‑512 hash comparison during each update deployment.

3. Encrypted Contact Channels

Users can send PGP‑encrypted messages using the official Kerberos Public Key (fingerprint 9A3C 1F58 889D 2C9E 7F92 AB12 7E9A 5AA4 8D3F 9E77). Decrypted messages are handled offline only by designated administrators on air‑gapped devices. No plaintext copies persist after response.

4. Data Retention Policy

None of the Kerberos services retain personal logs or messages. Server RAM is flushed every 12 hours, and content delivery occurs through volatile instances without persistent disks.

5. Third‑Party Interaction

No external CDNs except Font Awesome and Google Fonts are used; they load anonymously through Tor and do not receive tracking data. Kerberos Online partners share no information outside PGP‑signed bulletins visible publicly.

6. Policy Updates

This policy may change with project expansion, but all modifications are PGP‑signed and timestamped for public verification on the Kerberos Wiki ledger.

7. User Rights and Control

Every visitor of Kerberos Online retains the absolute right to review, modify or delete any content they have submitted through PGP‑signed channels. Because the platform does not store metadata, these requests are handled via one‑time confirmation tokens generated within Tor. Users may request audit logs signed and published in Kerberos Wiki for public verification.

Transparency is maintained through periodic cryptographic proofs of integrity. These proofs are publicly posted and can be validated without revealing visitor identity. The Kerberos team believes privacy equals freedom — no data should exist without explicit consent and control.

8. Additional Data Protection Clauses

In accordance with modern security principles, Kerberos Online follows the concept of “privacy by design”. All systems are ephemeral containers which self‑wipe after each session. Administrators audit source code under open GPL and keep a PGP‑signed revision trail. The market infrastructure utilizes onion routing with multi‑hop latency balancing to avoid traffic profiling. Physical servers are geo‑distributed across multiple jurisdictions providing legal diversity and redundancy against single point of failure.

This policy is governed solely by cryptographic consensus — the primary proof of authenticity remains each PGP signature. If a user detects a forged policy copy, they should compare hash SHA512 with the checksum published on kerberos‑online.com/wiki.html#integrity.