Kerberos Privacy Policy

Effective Date: January 2026

This document explains how the Kerberos Darknet Documentation Hub protects user privacy and manages zero‑knowledge data flows through encrypted infrastructure. We commit to full transparency and compliance with privacy‑first principles across every server and mirror.

1. No Personal Data Collection

Kerberos does not request names, emails, wallet addresses, or identifiable metadata. All pages are static HTML served via anonymous reverse proxies without cookies or session trackers.

2. Anonymous Logging Protocol

To ensure integrity audits without identity tracking, only aggregated technical metrics (uptime and error counts) are collected. No IP address, user‑agent, or browser fingerprint is logged or stored permanently.

3. Encryption & Transport Layer Security

All connections are served over TLS v1.3 (for clearnet mirrors) and native Tor encryption layers (for .onion domains). All data is encrypted both in transit and at rest using AES‑256‑GCM and ChaCha20‑Poly1305 schemes.

4. PGP Verification Requirement

Every public update or announcement issued by Kerberos admins is PGP‑signed. The fingerprints are listed on the Official Mirrors page, allowing anyone to authenticate integrity of information before trusting it.

5. Rights Under GDPR & Data Sovereignty

Although Kerberos collects no personal data, users retain the right to inspect any stored logs generated by error routines. All inspection requests must be signed with a valid PGP key for identity protection. We honor "Right to Deletion" immediately upon request.

6. Third‑Party Disclosure Policy

No data is ever shared, sold, or transferred to any entity — commercial, governmental, or external. Kerberos infrastructure is independent and operates under community oversight and PGP multi‑signature auditing.

7. Content Integrity & Tamper Protection

All HTML/CSS files are hashtagged with SHA‑512 and stored under multi‑sig repository. Any change triggers signed alert to users. This prevents malicious injection or backdoor code in Kerberos documentation content.

8. User Responsibilities

Users must apply end‑to‑end encryption for all communications, avoid reusing wallet addresses, and verify mirror fingerprints weekly. Kerberos is not liable for loss resulting from user side negligence or third‑party phishing.

9. Policy Updates & Contact

This privacy policy may be updated periodically to reflect security developments in 2026 and beyond. Updates will always be PGP‑signed and visible through the official Kerberos onion mirrors. For enquiries, use PGP‑encrypted message to our public key listed in the PGP Center.