How your data is protected

The security design of ViauMarky Password, in plain terms and in full detail.

In short: your private vaults are encrypted on your own devices with keys made from two secrets, your master password and your Secret Key. Neither ever reaches us. Our sync service stores only ciphertext, so it can’t read your data, and a stolen copy of it can’t be used to guess your master password.

Two kinds of vaults

The app keeps two kinds of vaults side by side. Everything else on this page is about your private vaults.

Your private vaultsThe ViauMarky vault
Who it’s forYour own logins, cards, notes and identitiesThe agency’s shared client and agency logins
Where it’s storedThe ViauMarky Password sync service, on CloudflareThe business’s ViauMarky dashboard (its own server and database)
Who can read itOnly you, on your own devices. The server stores ciphertext it can’t decrypt.Signed-in ViauMarky staff, following ViauMarky’s rules (admin-only entries, every reveal recorded in Activity)
EncryptionEnd to end, with your master password and Secret Key, on your deviceOn the ViauMarky server with its own encryption key, over HTTPS

The ViauMarky vault keeps the security model of the ViauMarky dashboard. The app adds a Face ID lock in front of it and never stores revealed ViauMarky passwords on your device.

Two secrets: master password and Secret Key

Every account has:

The Secret Key adds about 128 bits of randomness, so even a full copy of our database can’t be used to guess master passwords offline. You need both to sign in on a new device. Neither can be recovered by us: losing both your Emergency Kit and every signed-in device means losing the vault.

Secret Key format

VM1-XXXXXX-XXXXX-XXXXX-XXXXX-XXXXX: the version VM1 and 26 characters picked uniformly at random from the 30-character alphabet 23456789ABCDEFGHJKLMNPQRSTVWXYZ, which leaves out characters that are easy to confuse (0, 1, I, L, O, U). That’s 26 × log2(30) ≈ 127.6 bits. When you type it in, dashes, spaces and the VM1 prefix are ignored, and letters don’t have to be capitals.

How keys are made

All of this happens on your device. HKDF is HKDF-SHA256 (RFC 5869) and PBKDF2 is PBKDF2-HMAC-SHA256.

password   = your master password (UTF-8, trimmed, Unicode NFKD)
salt       = 16 random bytes made when the account is created
iterations = 650,000

p   = PBKDF2(password, salt, iterations, 32 bytes)
s   = HKDF(the 26 Secret Key characters, salt "VM1", info "ViauMarky Password secret key")
muk = p XOR s                     (the master unlock key, only ever in memory)

auth_key   = HKDF(muk, info "ViauMarky Password auth")
unlock_key = HKDF(muk, info "ViauMarky Password unlock")

How your data is encrypted

Encryption is AES-256-GCM with a random 96-bit nonce for every value. Each item is bound to its vault and item IDs, so the server can’t swap encrypted items between vaults or items without decryption failing. Moving an item to another vault re-encrypts it with that vault’s key.

Changing your master password, or making a new Secret Key, makes a new unlock_key (with a fresh salt) and re-encrypts only your account key. Your vaults and items don’t need to change.

On your devices

On our servers

What this doesn’t protect against

Found a security problem? Please email support@viaumarky.com.