PURGE-CHAT // PRIVACY POLICY

PRIVACY & DATA POLICY

Zero-Knowledge, Zero-Logs, and Permanent Data Vanishing by Design.

1. Zero-Knowledge AES-256 Client Encryption
Your private backup keys and message payloads never leave your browser unencrypted.

purge-chat implements a true Zero-Knowledge security model. When you initiate a room backup, all messages are encrypted client-side using Web Crypto API (AES-256-GCM) with keys derived via PBKDF2 (SHA-256, 100,000 iterations).

The server only stores an opaque encrypted binary blob and an un-linkable SHA-256 hash of the room identifier. Server administrators cannot inspect, decrypt, or recover your backup without your client-generated secret key.

2. Automatic & Cascade Data Vanishing
When a room expires or is manually purged, all message history vanishes instantly.

Active messages exist only during the designated room duration (10 minutes, 1 hour, or 24 hours). Messages are stored in an ephemeral relational database linked via foreign key constraints with ON DELETE CASCADE.

Upon room expiration or owner manual purge:

  • The room entry is deleted from the datastore.
  • Relational cascading deletion instantly purges all linked messages from disk.
  • In-memory metadata cache automatically evicts room keys via native TTLs.
  • Client connections receive an instant termination signal to clear local React memory.
3. Lightweight In-Memory Metadata Caching
Memory caching is reserved strictly for lightweight ephemeral metadata.

purge-chat keeps memory consumption to a minimum by holding only lightweight, short-lived metadata in memory while keeping room state ephemeral.

Native TTL keys expire automatically when room lifespan completes, preventing memory leaks, persistent logs, or un-purged data.

4. Zero Logging, No Analytics & No Cookies
Complete anonymity without persistent identification or tracking scripts.

purge-chat does not collect or store:

  • No IP addresses or location data.
  • No tracking cookies or analytics telemetry.
  • No personal names, email addresses, or phone numbers.
  • No persistent user profiles or account registries.

Sender aliases (e.g., Cipher Lynx) and sender IDs are generated locally in your browser and stored temporarily in your browser's localStorage.