Locket
Download
Back to Locket
Draft for Review

Privacy Policy

Plain-language disclosure of how Locket operates. Verified strictly against the open project codebase.

1. No Accounts or Identity Data

Locket does not require an account, phone number, email address, or username. You never register an identity with us.

Rooms are created with ephemeral 6-digit alphanumeric codes or QR codes. When you close a room or exit your session, that identifier expires.

2. Encrypted Store-and-Forward & Zero Content Access

Messages, voice/video calls, and file transfers travel directly between you and your peer over WebRTC peer-to-peer data channels whenever both participants are online. If a recipient is offline:

  • Encrypted Envelopes Only: Messages sent to offline peers are held temporarily on the server as opaque, end-to-end encrypted envelopes (AES-256-GCM) for up to 7 days, then automatically purged. Once delivered and acknowledged by the recipient, envelopes are deleted immediately.
  • Zero Server Access: The server never holds or receives room decryption keys. Message content, sender/recipient display names, and avatars cannot be read or decrypted by the server.
  • Server Metadata Visibility: The server only observes opaque routing metadata: room ID, timestamp, ciphertext size, and cryptographic key version.
  • Files Stay Strictly Peer-to-Peer: File attachments and media packets never touch or reside on server storage. File transfers wait until both peers are connected online and transfer directly device-to-disk.

3. Local Storage on Device

Because there is no central database, your conversation state resides exclusively on your local device:

  • Browser Storage: Active chat records and preferences reside in your local browser IndexedDB and localStorage.
  • Disappearing Messages: When a vaporize countdown timer expires, messages are permanently deleted from local storage on your device.
  • Emergency Panic Purge: Tapping the Panic Purge button immediately wipes local IndexedDB, clears localStorage, terminates all active WebRTC connections, and resets the interface.

4. Platform Boundaries & Screenshot Protection

We are honest about hardware and browser limitations:

  • Android App: The native Android APK enforces window FLAG_SECURE, preventing operating system screenshots and screen recordings.
  • Web Browsers: When using Locket in a web browser (Safari, Chrome, Firefox) on desktop or mobile, web standards do not provide an OS-level mechanism to prevent screenshots.

5. Diagnostics & Third-Party Services

Locket includes zero advertising libraries, zero Google Analytics, and zero third-party tracking SDKs. Call connection diagnostics (packet loss, ICE candidate type) are queried locally on your device via pc.getStats() for your live display and are never transmitted to external logging servers.

6. Customer Support & AI Assistance

Support chats are not end-to-end encrypted. AI replies are generated with Google Gemini. We remove emails, phone numbers and codes first. Don't share passwords or keys. Support transcripts are stored encrypted at rest with AES-256-GCM and deleted after 90 days.