Security
Everything is encrypted on your device before it leaves. The server only ever holds scrambled data for a short time, and it can’t unscramble it.
What the server sees
| Thing | What we see | What we promise |
|---|---|---|
| A Dipp | Encrypted bytes, size, expiry | Never readable by us. Deleted on first open or at expiry |
| A Dipp’s key | Nothing. It stays after the # in the link | Only people with the full link can read it |
| A passphrase | Nothing | A second lock if the link leaks |
| Room messages | Encrypted messages, room ID, random member IDs, IP addresses | Encrypted end to end. Deleted when the room ends |
| Card items | Nothing until you approve, then one sealed copy | We never see your number or handles |
How it works
- Each Dipp gets its own key, made on your phone (AES-256-GCM through the Web Crypto standard). An optional passphrase is stretched with PBKDF2, 600,000 rounds.
- Opening a Dipp takes a tap on Reveal, so link-preview bots in iMessage, Slack or Gmail can’t burn it first.
- Fetching and deleting happen in one step on the server, so two people can’t both open it.
- Removing someone from a room changes the room’s key, so their old link stops working.
What no app can stop
- A second phone’s camera.
- Screenshots on iPhone. The app tells everyone when one is taken. Android blocks them.
- A web page can’t block screenshots at all, which is why we say screenshot-resistant, never screenshot-proof.
- Someone you shared with choosing to copy what they saw.
Check our work
The code that encrypts on your device will be open source before launch, so anyone can check it.
Found a security problem? Email support@dippme.com with “Security” in the subject. Please give us time to fix it before you share it.