Privacy Policy — Kerberos Documentation Hub

Last Updated: January 2026

Kerberos Documentation Hub operates on a strict principle of data minimalism and anonymous access. This page serves as a legal disclosure of how we handle, store, and protect information in the context of a darknet documentation service. The hub is not a commercial entity; it collects no user data and retains no transaction records.

1. Information Collection and Logging

Kerberos does not collect personal data. There are no cookies, analytics scripts, or tracking pixels. We do not record IP addresses or user agents. When accessing via Tor, metadata is inherently stripped by design. Server logs are disabled; all requests exist in volatile memory and expire instantly after transmission is complete.

2. Static Infrastructure

The entire Kerberos hub is rendered as static HTML served from decentralized nodes. No database or dynamic backend exists, which eliminates attack surfaces and logging points. Caching occurs only locally within the user’s browser; you may clear it anytime via Tor settings.

3. PGP and Cryptographic Integrity

All published content is PGP‑signed to prove authenticity. If any text is altered by third parties, its signature verification will fail. Users should perform their own GPG checks on any mirror archives or configuration files downloaded from Kerberos.

4. Third‑Party Content

Kerberos pages do not embed external media or scripts. The only third‑party resource is a font stylesheet and icons from CDN, both public and cacheable. We encourage advanced users to self‑host these assets through offline mirroring if preferred.

5. User Communications

Support emails and messages sent to Kerberos administration must be encrypted with the official PGP key. Unencrypted correspondence is dismissed to protect both parties. Message metadata is removed upon decryption and not stored after reply.

6. Retention Policy

There is no retention of visitor data. Logs are never kept; audit records exist only as cryptographic hashes for checksum verification of files. This method prevents reconstruction of user patterns or behavioral profiles.

7. Cookies and Local Storage

No cookies are set by Kerberos. Local storage is used only for client‑side preferences (such as menu state on mobile) and is never transmitted to any server.

8. Legal Jurisdiction

As a Tor‑based documentation hub, Kerberos operates without centralized infrastructure or binding jurisdiction. Its purpose is educational, and no part of the project facilitates commerce or illicit transactions.

9. Your Rights and Control

Because Kerberos does not collect identifiable data, there is nothing to correct, export or delete. You maintain full control of your interaction simply by closing your browser session.

10. Security Measures

Pages are delivered over end‑to‑end encrypted .onion tunnels. PGP signatures authenticate authorship, while SHA3 hash manifests confirm content integrity. Administrators use cold signing keys kept offline for releases.

11. Updates to Policy

Updates occur every January. Users should review policy hashes published on the Official Mirrors page to verify authentic releases.

12. Contact Methods

Contact the Kerberos Security Team via encrypted email listed in PGP Settings. No unencrypted messages are processed.

By continuing to use Kerberos Documentation Hub you acknowledge that you understand and accept this Privacy Policy as a core part of our commitment to anonymous education and transparency.