Security

Designed so you don't
have to trust anyone.

What Sigilkeep protects, how, and where its protection ends.

Status

Sigilkeep has not had an independent security audit. It is built from standard, well-studied primitives, has automated adversarial tests and a recorded security test campaign, and its design is described on this page. It is pre-release software: do not rely on it as the only copy of important files.

Cryptography

Standard, well-studied building blocks, used the way they were designed to be used.

Encryption

XChaCha20-Poly1305 for everything stored in a vault, so every object is both encrypted and authenticated.

Passwords

Argon2id, with 256 MiB of memory and 3 passes by default, so every guess is slow, even on special hardware.

How Argon2id works

Keys

One random root key per vault, stored only wrapped under your credentials. HKDF-SHA256 and HMAC-SHA256 split it into a separate key for each purpose.

Keyfiles (optional)

A 256-bit random file. In keyfile mode the vault can’t be opened without it, and the key derivation itself enforces that.

Tamper detection

Swapped, cut, repeated or rolled-back pieces of a vault are detected and reported, not silently accepted.

No back door

No master key, no escrow, no recovery phrase and no reset. Nobody else can open your vault, including me.

In plain English

How Argon2id protects your password

Your vault is not locked with your password itself. Sigilkeep feeds your password, together with a random value called a salt that is different for every vault, into a recipe called Argon2id. The recipe’s result is the key that opens the vault.

How your password becomes the vault key Your password and a random salt that belongs to this vault go into Argon2id. Argon2id fills 256 MiB of memory and works through it three times, and only then produces the key that opens your vault. The key is never written down. Your password••••••••••plus a random saltinArgon2idPass 1 of 3Pass 2 of 3Pass 3 of 3Fills 256 MiB of memoryand mixes it 3 timeskeyVault keyOpens your vaultNever written downpasswordsalt How your password becomes the vault key Your password and a random salt that belongs to this vault go into Argon2id. Argon2id fills 256 MiB of memory and works through it three times, and only then produces the key that opens your vault. The key is never written down. Your password••••••••••plus a random saltinArgon2idPass 1 of 3Pass 2 of 3Pass 3 of 3Fills 256 MiB of memoryand mixes it 3 timeskeyVault keyOpens your vaultNever written downpasswordsalt
The same password and salt always give the same key. Anything else gives a key that opens nothing.

Heavy on purpose

Each time Argon2id runs, it has to fill 256 MiB of memory and stir through all of it three times before it gives an answer. You hardly notice: you type your password and wait a moment.

No shortcut for a thief

Someone who has stolen a copy of your vault has to guess the password, and every guess goes through the whole recipe, memory and all. Trying millions of passwords means doing that work millions of times.

Why guessing is slow You type your password once, and Argon2id runs once: a short wait. Someone who has stolen a copy of your vault has to run Argon2id in full, with its 256 MiB of memory, for every single password they try, so millions of guesses cost millions of times that work. Youtype the rightpassword onceonceArgon2idruns one timeopenA short waitthen your vaultis unlockedA thiefwith a stolen copytries millionsper guessArgon2idruns in full,every single timecostMillions of timesthe memory andthe work Why guessing is slow You type your password once, and Argon2id runs once: a short wait. Someone who has stolen a copy of your vault has to run Argon2id in full, with its 256 MiB of memory, for every single password they try, so millions of guesses cost millions of times that work. Youtype the right password onceonceArgon2idruns one timeopenA short waitA thieftries millions of guessesper guessArgon2idruns in full,every single time:millions of timesthe memory and work
The wait you notice once is the price a thief pays for every guess.

Why memory matters

The special chips attackers use to guess quickly are fast at sums but short of memory. Needing 256 MiB for every guess makes each one costly for them too.

Why the salt matters

Every vault has its own salt, so an attacker can’t prepare a list of answers in advance, and the same password in two vaults gives two different keys.

What it can’t do

It slows guessing down, but it can’t make a weak password strong. Use a long passphrase of several unrelated words, or add a keyfile: then the password alone opens nothing.

Against a hostile storage provider

Sigilkeep assumes the cloud folder may be read, changed, reordered or replayed by someone else.

  • Contents, file names, folder structure, timestamps and logical sizes are encrypted.
  • Every object is bound to its vault, its file and its position, so swapping, truncating or repeating pieces is detected.
  • Rolling a vault back to an older state is detected on devices that have seen a newer one.
The vault health panel in Sigilkeep: verified just now, storage details and a warning about one conflicting file.
Vault health: a deep check decrypts and authenticates every chunk.

Limits

No encryption tool can do everything. Sigilkeep cannot:

  • Hide how many encrypted objects a vault has, roughly how big they are, or when they change. Your storage provider can see that.
  • Stop someone with write access to the folder from deleting it. Keep backups.
  • Protect files on a device that is infected with malware while the vault is unlocked.
  • Recover a vault if you lose your password, or your keyfile in keyfile mode.

What Sigilkeep sends over the network

Your files, file names, passwords, keyfiles and vault keys never leave your device unencrypted. Your sync service uploads the encrypted vault folder on its own; Sigilkeep never connects to it. The only connections Sigilkeep itself makes are for Sigilkeep Pro:

Every connection Sigilkeep itself makes
WhatWhere toWhen
The Pro purchase checkApple’s App Store, through the system on your deviceMac, iPhone and iPad: when you buy Pro or restore purchases

Report a vulnerability

Please email security@sigilkeep.app. You can expect an acknowledgement within 5 working days and an initial assessment within 14 days. Disclosure is coordinated, normally within 90 days of the report or when a fix is released, whichever is first. Credit is given if you want it. There is no paid bug bounty. See also security.txt.

Use synthetic data only. Never send real vault files, passwords, keyfiles or licence keys: I will never ask for them, and I couldn’t use them to unlock anything. Forgetting a password is not a vulnerability; Sigilkeep has no recovery by design.

This website has no cookies, no analytics, no JavaScript and no third-party requests, and sends a strict Content Security Policy.