Help
How Didji keeps your secrets: the technical detail
For the curious: here's exactly what stands between your secrets and everybody else.
Every record is sealed with AES-256-GCM, an encryption standard used by banks and governments, under one 256-bit key made on your first device. Titles, labels, category names and notes are sealed as well as the passwords: nothing in Didji's store can be read without the key.
Each sealed record is also bound to its own place. Its kind, its identity, the record it belongs to and its revision are authenticated with the ciphertext, so a sealed record moved onto another record, or an attachment moved to another record, fails to open rather than being read in the wrong place.
The key lives in your iCloud Keychain, which Apple protects end to end, and is synchronised only to devices signed in to your Apple Account. That is the one promise Didji borrows rather than makes: "Apple can't read it" holds for your vault because the key travels only inside the Keychain's end-to-end encryption, which is Apple's to keep. Face ID, Touch ID or your passcode decide when Didji opens on a device; the key decides who can read what is inside. Your vault travels through your private iCloud database already sealed, so Apple stores records it cannot read, and Didji Studios has no server to store anything on at all.
Your recovery kit holds a key of its own: 32 bytes, with four bytes of a SHA-256 checksum added, taken over a prefix of the kit's own, so that a single character typed wrongly is caught and a kit's code is never mistaken for a vault key's. The kit key opens nothing itself. It unwraps a copy of the vault key, sealed with AES-256-GCM and kept in your iCloud and in each backup. Making a new kit seals the vault key again under a new kit key; once the new kit's printed code has been checked against that copy, the old kit's copy is gone. Each backup is sealed under a key of its own, which is sealed in turn under the vault key and under the kit in use that day, so an old kit opens the backups of its own day and nothing else. The Key ID is the first six bytes of the vault key's SHA-256 fingerprint, and the Kit ID the same of the kit key's, over a prefix of its own: enough to tell keys apart, and nothing that helps anybody find one.
A Didji passcode is never stored. What is kept, sealed in the vault with your other preferences, is a verifier: a random 16-byte salt and PBKDF2-HMAC-SHA256 over the passcode with 600,000 rounds, compared in constant time. Checking one takes about a third of a second, by design; wrong tries are counted in the vault, five of them start a wait that doubles up to an hour, and nothing is ever erased. The passcode stands in front of the vault, not inside the encryption: Face ID still opens it when it succeeds, and the recovery kit's code, which is the key itself, is the only thing that removes a forgotten one.
A backup carries a sealed manifest of everything in it. Before anything is restored, the whole file is checked against that manifest, and a file with anything added, removed or changed is refused outright.
Sharing never uses your own key. Each person you share with has a separate space, sealed under a key of its own that is handed over in the invitation; stopping sharing takes the space away. An Apple Watch is given a key of its own too, so the vault's key never reaches your wrist.
The breach check sends Have I Been Pwned only the first five characters of a password's SHA-1 hash, and compares the two thousand or so answers that share them on your phone, so nobody, not even the service, learns which password was checked. Passkeys are P-256 keys sealed in the vault, used only to sign for the site they were made for. While unlocked, Didji keeps secrets on show out of screenshots, recordings and screen sharing unless you allow them for ten minutes; that rests on iOS, and is a safeguard rather than a guarantee.
Good to know
- Unlocking reads and checks every record before anything is written. A vault that can't vouch for every record stops writing, so a fault never seals over good data.
- Nothing here depends on trusting us: there's nothing of yours on any computer of ours.
- AutoFill needs iOS to know what to offer before Didji is opened, so while it is on, Didji gives iOS's own credential store on your phone the website and username of each login in use, and the site and account name of each passkey and sign-in code. Never a password, a code or a key, and nothing archived or deleted. iOS keeps that list on the device.
- Printing a record with its values asks for Face ID again, as every durable copy does: the print sheet can save a PDF as well as print.
See also
Still stuck?
Write to us at hello@didji.app, and tell us which device you’re using if you can.
Never send a password or your recovery code to anybody, us included. What we can’t do for you.