How Dobr protects your files
The design behind the encryption, what it protects against, and what it can't.
The short version
- Files are encrypted with AES-256-GCM on your phone before they're written to storage. Every item has its own key.
- The key comes from your pattern plus a secret held in the phone's secure hardware, so the files can't be opened on another device, even by someone who knows the pattern.
- Nothing about your pattern is stored. There's no reset and no recovery, for anyone, including us.
- The app has no internet permission and Android's app backup is switched off, so no copy of a vault leaves the phone.
From pattern to key
- You draw at least 6 dots on a 4 by 4 grid. Dobr turns the order of the dots into a short string. That string is never saved.
- PBKDF2 with SHA-256 runs 150,000 rounds over it, using a random 32 byte salt created when Dobr was installed. This makes every guess slow to check.
- The result is mixed with HMAC-SHA256 using a key generated inside the Android Keystore, in StrongBox when the phone has it. That key never leaves the secure hardware, so this step only works on your phone.
- Two values come out: a vault id, which names the vault's folder, and the vault key. A different pattern gives a different id, which just points at a folder that doesn't exist. That's why Dobr keeps no list of vaults, and why nothing in the app shows how many there are.
How files are stored
- Each item gets its own AES-256 key, derived from the vault key and the item's random id with HMAC-SHA256. Its preview and its record get separate keys of their own.
- Files are encrypted in 64 KB chunks with AES-GCM. Every chunk has its own nonce and authentication tag, and its position in the file, plus whether it's the last chunk, are bound into that tag. A file that has been altered, reordered or cut short refuses to open instead of showing something wrong.
- File names, types and dates live inside an encrypted record for each item. On disk, folder and file names are random.
- Before Dobr offers to delete an original from your gallery, it reads the encrypted copy back and decrypts it in full to make sure it's intact.
Viewing, memory and temporary copies
- Photos are decrypted into memory to be shown. Videos play straight from the encrypted file, a chunk at a time. Neither is written to storage as a readable file.
- Two actions do make a readable copy, because that's what they're for. Save a copy outside Dobr saves one where you choose. Open in another app hands a temporary copy to the app you pick, and that copy is deleted when Dobr locks.
- When Dobr locks, the vault key is wiped from memory and cached previews are dropped.
Locking
- Leaving the app locks it. So does turning the screen off.
- When Dobr itself opens the photo picker, the file picker, the Google Play purchase sheet or another app, it waits up to two minutes before locking, so you aren't thrown out halfway through. Turning the screen off still locks it straight away.
- Screenshots and screen recording are blocked inside the app, and the recent apps screen shows Dobr as a blank card.
What leaves the phone
- Nothing. Dobr has no internet permission, so it can't connect to anything, and it has no analytics, ads or crash reporting.
- Android's cloud backup and phone-to-phone transfer are switched off for Dobr. A new phone starts with no vaults.
- Purchases go through Google Play. The app only asks Google Play on your phone whether you've bought Unlimited. Details are in the privacy policy.
What Dobr protects against
- Someone scrolling through your gallery or photo apps.
- Private photos ending up in a cloud backup or a leaked account.
- Someone who copies the app's files off the phone. Without your pattern and this phone's secure hardware, they're unreadable.
- Being made to open the app. With Unlimited, a second pattern opens a separate decoy vault, and nothing on screen says another one exists.
What it can't protect against
- Someone who knows your pattern or watches you draw it. Pick one that's hard to guess, use 8 dots or more, and cover the screen when you draw it.
- Guessing on your own phone. Dobr doesn't lock you out after wrong patterns, so nobody can lock you out either. Each guess takes the phone a moment to check and long patterns have a huge number of possibilities, but a short, obvious shape is easy to try.
- A phone that's already compromised. Malware with full control of the phone, or someone with your unlocked phone while the vault is open, can see what's on screen.
- A forensic look at the phone's storage. On a rooted phone, or from a forensic copy of one, someone can see how many vault folders exist and roughly how many items each holds. They still can't open any of them. A decoy vault works against someone looking at the screen, not against a forensic examination.
- Copies that exist somewhere else, such as photos you've sent, photos already backed up before you added them, or copies you've saved out of Dobr.
- Losing the vault itself. Uninstalling Dobr, clearing its storage, resetting the phone or losing it deletes your vaults for good, and a forgotten pattern can't be reset. Keep a copy of anything irreplaceable somewhere you trust.
Can I check any of this?
Yes. The code that does everything on this page is public on GitHub at DOBR-APP/dobr-crypto: the key derivation, the file format, how vaults are stored, the hardware key, and the locking. It comes with the tests the app is built against, a full write-up of the design, and a second version written in Python from that write-up, so you can check the two agree. The screens and Google Play billing aren't included.
Dobr's Play listing also shows its permissions and its data safety section, and neither includes internet access or any data collection. If you think something here is wrong, or you find a problem, email [email protected].