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

Privacy Policy

How ENCLAVE processes, minimizes, and protects your information across ephemeral communication rooms and account services.

1. Core Privacy Principles

ENCLAVE is engineered around the principle of Privacy by Design. Traditional communication platforms collect, index, monetize, and permanently store user messages and metadata. ENCLAVE inverts this architecture: our server operates strictly as a blind, ephemeral courier. We collect the minimum technical information necessary to establish encrypted rooms and route ciphertext between active participants.

Mathematical Invariants
  • • Zero server plaintext: Server never receives or stores unencrypted message content or media.
  • • Zero long-term chat storage: Rooms exist only in volatile server RAM and dissolve upon exit or timeout.
  • • Zero third-party trackers: No analytics beacons, advertising pixels, or behavioral tracking SDKs.

2. Categories of Data Processed

We process only the specific data elements required to authenticate users, manage room lifecycles, and relay encrypted packets:

Data CategorySpecific ElementsStorage LocationPurpose
Account IdentityDisplay Name, Email address, Account IDClient localStorage / Account StoreUser identification and workspace session authentication.
Cryptographic MetadataRoom ID, Salt (Base64), Auth Commitment (SHA-256), Wrapped Secret BundleVolatile Server RAM (`roomStore`)Enabling authorized participants to verify room access and unwrap room keys.
In-Transit CiphertextAES-256-GCM ciphertext, 96-bit CSPRNG IV, sequence counter, timestampTransient RAM ring buffer (max 50 packets)Relaying encrypted messages between active participants in real-time.
Presence StateActive participant count, heartbeat timestamp, room state (WAITING/ACTIVE/ENDING/DESTROYED)Volatile Server RAMSynchronizing real-time membership and triggering automated dissolution.

3. Content vs. Cryptographic Metadata

We maintain a strict architectural distinction between message content and routing metadata:

Message & Media Content

Message text, images, and video attachments are encrypted in client browser memory using AES-256-GCM with keys derived via Argon2id. The server has no mathematical access to decryption keys and cannot view, search, index, or decrypt content.

Operational Metadata

The server processes ephemeral metadata (packet ID, room ID, sequence number, timestamp) strictly to route bytes and prevent packet replay. This metadata is never tied to advertising profiles and is purged upon room destruction.

4. IP Addresses & Technical Logs

To prevent denial-of-service (DoS) attacks and brute-force access attempts against protected rooms, ENCLAVE maintains a temporary in-memory rate-limiting table (rateLimitStore).

• Rate-limit keys (combining client IP and Room ID) are stored purely in volatile RAM and automatically reset after 5 minutes of inactivity.
• ENCLAVE does not maintain permanent IP access logs or link network addresses with account profiles.
• Web server network infrastructure logs (such as transient edge reverse proxy logs) are retained strictly for operational security and discarded on rotating schedules.

5. Encrypted Media & File Routing

Photos and videos sent within an ENCLAVE room undergo client-side metadata stripping (removing EXIF, GPS coordinates, and camera serial numbers) and are encrypted with unique AES-256-GCM media keys before upload to the ephemeral media endpoint (/api/rooms/[roomId]/media).

Encrypted media payloads reside exclusively in the room’s in-memory record. They are never written to permanent disk storage or cloud object buckets and are permanently purged when the room dissolves.

7. Subprocessors & Infrastructure

ENCLAVE minimizes third-party dependencies. We do not integrate with advertising networks, behavioral tracking tools, or external customer analytics platforms.

Entity / ProviderRole / ServiceData HandledAccess Level
Hosting & Edge Network ProviderApplication compute & HTTP routingEncrypted in-transit HTTP/WebSocket packetsBlind transit (TLS encrypted)
Email Verification Gateway (Optional)Transactional verification token deliveryDestination email address & verification tokenTransient delivery only

8. Data Retention & Ephemeral Erasure

ENCLAVE implements automated cryptographic erasure and in-memory garbage collection:

  • Room Dissolution: When the last participant exits a room, all packet buffers, active socket references, and media records are immediately zeroized in memory.
  • Automated Reaper: Rooms idle for more than 15 minutes or abandoned waiting rooms (idle > 3 minutes) are automatically purged by the server reaper process.
  • Client Account Deletion: Users can execute self-service account deletion via the Profile console, immediately zeroizing all local authentication tokens and active session records.

9. Your Data Protection Rights

In accordance with the DPDP Act 2023 and global privacy frameworks, you have specific statutory rights regarding your personal data:

Right of Access & Summary

Request a summary of personal data processed and identities of data fiduciaries.

Right of Correction & Erasure

Update inaccurate display names, modify email records, or request complete account erasure.

Right of Grievance Redressal

Submit formal complaints regarding data processing practices directly to our compliance desk.

Right to Nominate

Designate an individual to exercise privacy rights in the event of incapacity or death.

10. Children’s Privacy

ENCLAVE is intended for individuals who are at least 18 years of age (or the age of majority in your jurisdiction). We do not knowingly collect personal data from children or track behavioral profiles of minors. If you believe a minor has provided personal data, please contact our privacy desk for immediate deletion.

11. International Data Handling

Because ENCLAVE routes encrypted ciphertext via global edge nodes, ephemeral data packets may transit international network routes. All transmissions are protected by transport-layer encryption (TLS 1.3) and client-side end-to-end encryption (AES-256-GCM). We ensure compliance with statutory data transfer restrictions.

12. Contact & Grievance Redressal

To exercise your privacy rights, submit a data inquiry, or contact our designated Grievance Officer under the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules and DPDP Act:

Compliance & Privacy Desk: enclave.support.legal@gmail.com
Grievance Redressal Channel: enclave.support.legal@gmail.com
Response Timeline Target: Acknowledged within 48 hours; resolved within 30 days.
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