Legal Center
Last Updated: October 9, 2026·Effective: October 9, 2026
PrivacyVerified Codebase Spec

Data Retention & Deletion Policy

The complete technical lifecycle matrix documenting exact retention durations, automated memory purging, and data zeroization triggers.

1. Data Lifecycle Principles

Traditional platforms treat user communication as permanent corporate assets stored indefinitely in relational databases. ENCLAVE follows a strict ephemeral-first paradigm: communication state exists only as long as the conversation is actively occurring. When a room closes, its data is permanently dissolved from volatile RAM.

2. Comprehensive Data Retention Matrix

Below is the verified lifecycle schedule for all data processed across the ENCLAVE system:

Data CategoryStorage LayerMaximum Retention WindowErasure TriggerMethod of Deletion
Encrypted Message PacketsVolatile RAM (Ring Buffer)Duration of active room session (max 50 packets)All participants leave OR room idle timeoutArray zeroization and memory dereferencing
Encrypted Media BuffersVolatile RAM (`encryptedMedia` Map)Duration of active room sessionRoom exit OR reaper triggerMap eviction and garbage collection
Room Cryptographic MetadataVolatile RAM (`roomStore`)Duration of room sessionRoom dissolutionState set to DESTROYED; purged within 30 seconds
Rate Limit RecordsVolatile RAM (`rateLimitStore`)5 minutes from last attempt5-minute inactivity window expiryAutomatic Map deletion
Account Profile & SessionsClient Browser (`localStorage`)Until user executes self-service deletionManual deletion via Profile consoleClient-side `localStorage.removeItem()`

3. Automated In-Memory Reaper Specifications

The ENCLAVE server executes a background reaper routine every 10 seconds to detect and dissolve abandoned or inactive rooms:

Waiting Room Idle Limit
3 Minutes

Rooms in WAITING state with no participant join activity are automatically destroyed after 180 seconds.

Active Room Inactivity
15 Minutes

Active rooms experiencing 15 minutes of zero message or heartbeat activity are permanently reaped.

Abandoned Room Timeout
10 Minutes

Rooms created but never joined by any client are purged after 600 seconds.

4. Room Dissolution & Cryptographic Erasure

When a room transitions to DESTROYED state:

  1. Active WebSocket / polling connections are immediately disconnected.
  2. All stored ciphertext packets and encrypted media buffers are wiped from memory.
  3. The room identifier is blacklisted from receiving subsequent connections.
  4. Client browsers execute memory cleanup, zeroizing session keys and clearing message displays.

5. Account Data & Client Zeroization

Registered accounts and profile identities exist in client-side storage until deleted. When you click "Delete Account Permanently" in your Profile:

  • All local authentication tokens are cleared from browser localStorage.
  • Active device session registers and pending verification tokens are wiped.
  • The client is logged out and redirected to the homepage.

6. Server Backups & Persistent Logs

Because chat messages and room states are never committed to permanent databases or disk drives, no server backup archives contain your messages or media attachments. When memory is cleared, the data is gone permanently.

7. Verifying Deletion on Client Devices

To ensure complete local cleanup after leaving a conversation, simply close your browser tab or clear browser session data. Once the tab is closed, all client-side decryption keys held in JavaScript memory are automatically destroyed by the browser engine.

Inquiries & Grievance Redressal

For formal data rights requests, security disclosures, or regulatory inquiries concerning this policy, submit a verified request through our official channels.

Related Legal & Privacy Documents