Privacy Policy / Kerberos Documentation Hub (2026)
This Privacy Policy explains how Kerberos Documentation Hub (“we”, “our”, or “the project”) processes and protects any information collected through its clear‑net and .onion sites. Kerberos was built by security researchers and exists solely to educate users about privacy models; we keep zero logs and pursue maximum anonymity by design.
/1 – Information We Don’t Collect
No personal data, IP addresses, cookies, or tracking identifiers are stored. Unlike standard web analytics, Kerberos operates without Google Fonts tracking, CDN cookies, or scripts that harvest usage data. Requests are served statically and discarded after session delivery. Even error logs are scrubbed of header information prior to temporary storage for debugging purposes.
/2 – Cryptographic Integrity of Data
All published documents are signed with Kerberos PGP keys. User‑submitted content or reports must be cryptographically signed as well. This guarantees authenticity and detects tampering or unauthorized modifications. Each release of this policy includes a hash checksum posted in the links section.
/3 – Zero‑Log Infrastructure
Kerberos is hosted on bare‑metal servers configured with ephemeral memory. Logs are disabled at the operating‑system and service levels. Incoming requests are read into RAM only, processed, and never stored on disk. If maintenance requires temporary logging, files are encrypted and purged within 24 hours.
/4 – User Rights and Control
Because no identifiable records exist, there is nothing to delete or rectify. However, users may verify and validate PGP‑signed content and report anomalies using our contact fingerprint. We encourage privacy enthusiasts to clone and audit this repository for transparency.
/5 – External Resources and Mirrors
Links to external sites (e.g., Tor Project) are provided for educational purposes only. Kerberos is not responsible for privacy policies of third‑party resources. Always review external PGP signatures and avoid entering personal data elsewhere.
/6 – Security of Transmission
All connections are forced through HTTPS and .onion services with HSTS. We do not use CAPTCHAs, embedded iframes, or external JS dependencies that could expose visitor information. Our goal is complete end‑to‑end encryption across all layers of transport and storage.
/7 – Community Contributions & Transparency
Edits to the documentation are tracked via PGP‑signed commits. History and differences remain public to proof integrity. We do not store usernames or IP metadata for these actions. All contributors are encouraged to use detached signatures for identity validation.
/8 – Changes to This Policy
If this Policy is updated, the new hash, date, and signature will appear both on clear‑net and .onion versions. Historical copies remain accessible for audit. Major changes are announced through the Kerberos PGP channel and via newsletter (relayed through public PGP).
/9 – Contact
To reach the Kerberos Privacy Council, sign your message with a verified PGP key and send it through our secure onion portal. Unsigned emails are discarded without review. We answer publicly to preserve accountability and avoid individual tracking.