Zenclave Privacy Policy
September 16, 2026•523 words
Last Updated: September 16, 2026
At Zenclave, privacy isn't a feature; it is the fundamental mathematical constraint of our architecture.
We built Zenclave to provide a secure, ephemeral workspace where your data is yours, and yours alone. This policy outlines our "Zero-Knowledge" approach to your data. Because of how the app is engineered, it is cryptographically impossible for us to read your messages, view your files, or identify you.
1. What We DO NOT Collect
To ensure absolute anonymity, Zenclave is designed without traditional user accounts. We do not collect, request, or have access to:
Names, Usernames, or Email Addresses.
Phone Numbers or Device Contacts.
Location Data (GPS or Cell Tower data).
Device Identifiers (IMEI, MAC addresses, or Advertising IDs).
2. Zero-Knowledge Architecture & End-to-End Encryption (E2EE)
All data transmitted through Zenclave is secured using AES-GCM 256-bit encryption.
Local Key Generation: When you create or join a Zenclave room, the cryptographic keys required to encrypt and decrypt data are generated dynamically in your device’s local memory (RAM).
Blind Relay: We utilize Google Firebase as a "blind relay" to sync encrypted data between participants. The encryption keys never leave your device and are never transmitted to the cloud. Therefore, the relay server only stores and processes unreadable mathematical noise.
Sealed Sender: Any metadata (such as your generated Alias and the timestamp of your message) is encrypted inside the payload before it leaves your device. The server cannot determine who is talking or when the message was actually written.
3. Data Retention and Ephemerality
Zenclave is built for transient collaboration.
The Burn Protocol: When any user initiates a "Burn," the encrypted data is permanently and irreversibly deleted from the relay server for all participants.
Total Burn: Initiating a "Total Burn" destroys your local cryptographic keys, permanently locking you out of the session and erasing all local traces of the room.
Automated Purging: Even if a room is abandoned without utilizing the Burn protocols, the encrypted ciphertext stored on the relay is strictly temporary and is subject to automated purging.
4. Device Permissions
Zenclave requests zero invasive OS-level permissions. We do not require access to your Camera, Microphone, or Location services to function. If you choose to upload a file to the Secure Vault, you only grant the app temporary access to that specific file via the native system picker.
5. Third-Party Services
We use Google Firebase strictly for infrastructure routing (NoSQL document syncing). Because all data is encrypted client-side before transmission, Firebase cannot read, parse, profile, or monetize your communications or files. We do not integrate third-party analytics or advertising SDKs.
6. Children's Privacy
Zenclave does not collect any personal information and does not target children under the age of 13. Given the anonymous nature of the application, we cannot verify the age of our users.
7. Changes to This Policy
If we make changes to our architecture that affect this policy, we will update the "Last Updated" date at the top of this document. However, our core commitment to a Zero-Knowledge, accountless architecture will never change.
8. Contact Us
For security audits, vulnerability reports, or privacy inquiries, please reach out to us at: zenclave@proton.me