How Aranor protects your vault

Your vault is stored on your phone and nowhere else unless you choose to copy it.

• No vault on our servers. Logins, cards, notes, one-time-password seeds and the list of sites you have accounts at stay on the device. Aranor's servers never receive them, in plain text or encrypted.
• The domain list is treated as a secret. Which sites you use is a map of your life, so Aranor doesn't fetch website icons or do anything else that would put a saved site's address on the network.
• Copies only where you send them. Moving to a new phone works by QR code between the two phones, with nothing on the network, or by an encrypted file you choose where to keep. Premium backups to Google Drive are encrypted before they leave the phone.

Two layers of encryption, both opened by a key that only your master password can produce.

• Key derivation: Argon2id. Your master password is turned into a 256-bit key with Argon2id, the memory-hard function recommended by RFC 9106. Aranor uses 64 MiB of memory (32 MiB on slower phones), four lanes, and at least three passes, more on fast phones, tuned so unlocking takes about a quarter of a second. Each guess costs an attacker the same memory and time.
• An encrypted database. The vault is a SQLCipher database, so the file on disk is encrypted as a whole.
• Each item sealed on its own. Inside it, every entry is encrypted again with AES-GCM, which also detects any tampering.
• Biometric unlock stays in the phone's hardware. If you turn on fingerprint or face unlock, the vault key is sealed with a key held in the Android Keystore that only opens after Android confirms it's you. Aranor only learns whether it succeeded, never your fingerprint or face.

Aranor's servers do a few narrow jobs, none of which involve your vault.

• Premium, if you buy it. A sign-in account and a record of your plan, so a purchase works across reinstalls.
• Crash reports. The app is built so vault fields never enter logs: release builds strip logging calls along with their arguments, and the build fails if new logging is added.
• Usage statistics, only if you turn them on. They're off by default and never include anything you've saved or typed.

The full list, with retention periods, is in the Aranor Privacy Policy.

Aranor can tell you if a password has appeared in a known breach without anyone learning which password you checked. It hashes the password on your phone and sends only the first five characters of that hash to Have I Been Pwned. The service replies with every leaked hash that starts the same way, hundreds of them, and the comparison happens on your phone.

You can try the same check on the Aranor page.

There's no reset, by design. If we could reset your master password, so could anyone who broke into us.

• Recovery code. When you create your vault, Aranor shows a recovery code once. It's the only way back in if you forget your master password. Write it down and keep it offline.
• Emergency kit. You can make an encrypted copy of your vault plus a separate passphrase for someone you trust, so they can reach your accounts if you can't. Keep the file and the passphrase apart.
• A lost phone. Without your master password, the vault on it stays encrypted. Your accounts come back from a backup or transfer you've made.

Encryption protects a locked vault. Some attacks happen around the vault instead, and we'd rather you knew them:

• A compromised phone. Malware, a rooted phone, or a hostile keyboard, accessibility service or screen recorder can see what you see while the vault is open.
• A weak or reused master password. Argon2id makes every guess slow, but a password that's already on a leaked list is guessed first.
• An unlocked vault. Anyone holding your phone while the vault is open can use it. Keep auto-lock on.
• Lost recovery material. Lose both your master password and your recovery code, and the vault can't be opened by anyone, including us.

For high-risk moments Aranor has decoy and travel modes and a panic wipe.

If you think you've found a security problem in Aranor or murvianlabs.com, emailcontact@murvianlabs.com with "Security report" in the subject. Tell us what you found and how to reproduce it. Please don't include anyone's real passwords or vault exports.

• We'll acknowledge your report and keep you updated while we fix it.
• Give us reasonable time to fix the problem before you publish details.
• Test only against your own accounts and data, and don't disrupt the service for others.

Our contact details for security reports are also published at/.well-known/security.txt. When an independent security audit of Aranor is completed, we'll link the report here.