How your encryption works

You load the round. We just make the press.

A cartridge only performs if every component is right — the case, the primer, the powder charge, the projectile. Miss one and the rest does not matter. Your records work the same way, and the component you control is the one that decides everything.

The Encryption Lab

Try to break it. See what it would take.

Loading the lab…

Time to break in

Everything depends on one thing, and it isn't the algorithm.

Assume the worst case: someone has stolen the encrypted file, they are grinding away offline where nothing can rate-limit them, and they know exactly how we derive keys. Here is how long each kind of password holds.

A password you reused somewhere else
the one from that forum in 2017 · — bits
Instantly

It is already in a cracking list. Nobody brute-forces it; they look it up.

A password that looks strong
Mustang!7 · ~28 bits
About 2 minutes

Capital, symbol, digit — it passes every strength meter and follows three patterns a cracker tries first.

Answers only you would know
birth city, first car, mother's maiden name · ~10 bits
Under a second

Against someone who knows you — an ex, a sibling, a roommate. The people most likely to want your serial numbers already have most of the answers.

Four random words
hammer · lilac · copper · flint · ~44 bits
About 3.3 months

Random beats clever — four words already beats Mustang!7 by a factor of sixty thousand. It is still not enough, which is why our own generator will not hand you four.

Five random words
hammer · lilac · copper · flint · meadow · ~55 bits
About 570 years

One more word moved it from months to centuries. This is the floor the generator starts you above, not the target.

Seven random words
hammer · lilac · copper · flint · meadow · anvil · marble · ~77 bits
About 2.4 billion years

What the generator gives you by default, and still seven things you can picture in a row.

Your recovery code
generated on your device · 160 bits
10²⁴ × the age of the universe

This is why the recovery kit is the one thing we tell you to print and put somewhere physical.

The record key itself
AES-256 · 256 bits
Out of reach of physics

Not a big number — a different category. Counting to 2²⁵⁶ would take more energy than the sun will ever emit. This is never the part anyone attacks.

Priced at one million guesses per second — a rented cluster several hundred times faster than a high-end graphics card actually manages against our key derivation, which is memory-hard by design and lands around 2,000–3,000 guesses per second in practice. Times are expected-case, meaning the attacker finds it halfway through on average. We use the unfavorable number on purpose; a table like this is only worth reading if it errs against the people who published it. The recovery-code and key rows are not slowed by the key derivation at all; they need no help, because 160 and 256 random bits are out of reach at any speed.

Where the jump happens

Two more words is worth more than every clever trick combined.

Look again at the table and find where it stops being measured in months. It is not at a stronger algorithm. It is between word four and word six — the part nobody else can do for you.

Our key derivation buys you about twenty bits. Roughly two free words. It turns four words from minutes into months. It cannot rescue a bad password.

The lab above is the real thing, not a mock-up: the same 2,048-word list and the same arithmetic the generator inside your account uses, which is where the 11 bits per word above comes from. Nothing you type or roll is sent anywhere — the words are drawn by your own browser, and this page has no database to send them to. And a passphrase you did not choose yourself is the entire point: a word you picked because it means something to you is a word that someone who knows you can guess.

The components

Four parts, and you own the one that matters.

Handloaders already understand this page. You do not trust a round because the box says so — you trust it because you know what went into it and you measured the charge yourself.

The primer

Your passphrase

The component we never see, never store, and cannot reproduce. Everything downstream is ignited by it, and nothing downstream can compensate for a weak one.

The powder charge

Argon2id, 64 MiB

Measured deliberately heavy. Each guess an attacker makes has to allocate 64 MiB of memory and work through it — which is what drags a graphics card from ten billion guesses a second down to a few thousand.

The projectile

AES-256-GCM

The cipher that actually does the work, on your device, before a single byte leaves it. Nobody attacks this part. It is not the weak component in any real break-in, which is exactly why we spent this page on the primer instead.

The headstamp

Your recovery code

160 random bits your own device generates once and shows you once. It unlocks an independent wrapped copy of your vault key. Supported passkeys can also unlock the vault, but availability varies by device. Keep it on paper in a safe, not in your email.

The honest part

What this protects, and what it plainly does not.

Encryption is a specific tool for a specific job. Any page that tells you it solves everything is selling something. Here is the actual boundary.

What it stops cold

  • Someone stealing our database. They get ciphertext and nothing to open it with.
  • An employee going looking. There is no internal tool that can read your records, because the key was never on our side.
  • A stolen or lost backup file. Same math as the table above.
  • Reading your stored encrypted collection for AI training. Optional AI valuation separately sends the description you submit in readable form, as explained below.

What it does nothing about

  • Malware on your own device, reading your screen after you have unlocked.
  • A password you reused somewhere that has already been breached.
  • Someone watching you type it, or finding your recovery code in a drawer.
  • A court ordering you to unlock it. That fight is between you and your attorney, and courts genuinely disagree about it.

If you take one operational thing from this page: the passphrase protecting your collection should be used for this and nothing else, and your recovery kit should live somewhere physical. Those two habits matter more than every technical decision listed above.

What we can actually see

We will not claim we know nothing about you.

Plenty of products say "zero knowledge" and mean it loosely. Here is the specific, checkable version, including the parts that are not encrypted.

Encrypted vault contents

  • Makes, models, serial numbers, values and notes.
  • Photos and documents, including everything in the document safe.
  • Safe combinations, storage locations, and your estate instructions.
  • Permit details, trusts, and the contents of every record type in the app.

Visible on our side

  • Your email address, optional account name and home/residence state, and billing identifiers and history through Stripe.
  • How many records you hold, of which kinds, and when they last changed. The app cannot list your collection without that much.
  • Record and media identifiers, relationships and stored file sizes; sign-in times, IP addresses, browser/device details, city, region, country, approximate coordinates and network operator.
  • Support messages, attachments and staff notes, and the descriptive fields you submit for optional AI valuation. Do not paste serial numbers or other private information into those fields.

A legal request can reach readable account, billing, sign-in and support information as well as encrypted vault contents. Stored vault ciphertext is not readable through our normal server tools, but metadata and information you voluntarily disclose have different boundaries. The Privacy Policy lists these records and their retention, including recovery backups.

AI valuation is optional. Make, model, caliber, category, condition, year/era and up to 500 characters of additional details are sent in readable form to CaliberBase and to Anthropic, with Cloudflare Workers AI as a fallback. A fallback can follow an Anthropic attempt, so both providers may receive the description. We do not add your email, account ID or a dedicated serial-number field to the model prompt. Text you enter is not automatically redacted: do not include names, serial numbers or other private information. We retain account-linked usage counts and operational error metadata; we do not save the description or estimate from the request in our database. If you choose to save an estimate, it becomes part of your encrypted vault. Provider processing and retention follow the applicable service terms and configuration; we do not promise zero retention by providers.

Your collection, your ledger

A tracking tool that answers to you.

This is a record of what you own, kept the way records of what you own ought to be kept: by you, readable by you, on terms you set. Not a registry. Not a database someone else queries. Not a product that studies your collection to sell you something. You hold the key, and the arithmetic on this page is what that sentence is worth.