Privacy Policy

1. Fundamental Architecture: Zero-Knowledge by Design

Twosome Chat ("we", "us", or "our") operates the web application at app.twosomechat.online and the informational website at twosomechat.online. Our core principle is simple: we believe your conversations should belong solely to you and the one person you choose to speak with.

We employ client-side End-to-End Encryption (E2EE). Cryptographic key generation, message encryption, and message decryption happen exclusively on your device. Our servers act merely as encrypted payload delivery relays and have zero mathematical capability to read your messages, view your media, or eavesdrop on your voice or video calls.

2. Information We Do NOT Collect

Unlike conventional messaging platforms, we deliberately minimize data collection:

• No Plaintext Content: We never receive, store, or log the unencrypted text of your messages, filenames, or call streams.
• No Address Book or Contact Syncing: We never request access to or upload your phone contacts.
• No Behavioral Profiling or Ad Trackers: We do not deploy third-party advertising trackers, retargeting pixels, or surveillance analytics scripts.
• No Location Tracking: We do not track or log your precise GPS location.

3. Information Processed to Facilitate the Service

To establish and deliver encrypted sessions between you and your partner, we process minimal technical data:

• Encrypted Message Payloads: Ciphertext blobs are held temporarily in our database to allow delivery to your connected partner. Once delivered or cleared by room retention rules, these payloads are deleted.
• Cryptographic Session Metadata: Ephemeral public keys and room identifiers necessary to negotiate end-to-end encrypted sessions between the two participants.
• WebRTC Call Signaling: Temporary session description protocol (SDP) offers, answers, and ICE candidate data used to establish direct peer-to-peer audio and video streams. This signaling data is discarded once the call connection completes.
• Basic Account Identifier: A pseudonymized account identifier or authentication token used solely to authorize access to your designated room.

4. Cryptographic Keys and Device-Only Storage

Your private encryption keys are generated locally within your browser using standard cryptographic APIs and stored strictly in your browser's local sandbox (IndexedDB or LocalStorage). Private keys are never uploaded to our servers, never backed up to any cloud provider by us, and cannot be retrieved by our staff.

Consequently, if you clear your browser data or switch to a new, unlinked device, existing encryption sessions cannot decrypt past messages. This design choice prevents unauthorized parties from reading your historical communications even if credentials are breached.

5. Ephemeral Media and Disappearing Messages

Photos marked as "View-Once" are encrypted prior to upload. Upon being decrypted and rendered by the recipient device, the media is deleted from local memory and its ciphertext envelope is immediately removed from the database, preventing re-opening.

When disappearing messages are enabled, our retention routines automatically purge expired message documents on both client devices and intermediary storage.

6. Physical Realities and Screenshot Limitations

While we enforce technical restrictions wherever possible, client-side cryptographic guarantees protect data in transit and on servers, but cannot prevent the physical recipient of a message from capturing their own display.

7. Data Deletion and Room Purging

Either participant in a room has the right to delete chat history or leave the room. Deletion requests permanently remove stored ciphertext envelopes and room metadata from our systems.

8. Contact Us

If you have questions about this Privacy Policy or our cryptographic design, please reach out to:
Email: support@twosomechat.online