2026-09-01
FEMA says your emergency kit needs digital copies of your documents. Encrypt them first.
Today is September 1st, which makes this the first day of National Preparedness Month — the awareness month FEMA's Ready campaign has run every September since 2004, with a 2026 theme of "Americans Stand Ready". Preparedness advice is mostly physical: water, flashlights, a go-bag by the door. But every serious checklist also has a line about paperwork, because disasters destroy documents with special efficiency — the fire that takes your house takes the deed to it, the insurance policy covering it, and the birth certificates of everyone who lived in it, all in the same hour. FEMA's own guidance says to keep electronic copies of your critical documents, and it describes how with exactly one security phrase: "password-protected." This post is about taking that phrase seriously — why document copies are the part of your emergency kit most worth encrypting properly, and what encryption honestly does and doesn't fix when the worst week of your life actually arrives.
What burned in January 2025, besides the houses
On January 7, 2025, two fires started hours apart in Los Angeles County. By containment at the end of the month, according to LA County's own fact sheet, the Eaton Fire had destroyed 9,414 structures and killed 19 people, and the Palisades Fire had destroyed 6,837 structures and killed 12 — a combined 16,251 buildings and 31 lives. Inside thousands of those buildings were the filing cabinets, desk drawers, and fireproof-rated boxes where households keep the paper that proves who they are and what they own: deeds, titles, insurance policies, passports, Social Security cards, birth and marriage certificates, medical lists. The cruelty of document loss is its timing — the weeks after a disaster are precisely when you need documents most, to file insurance claims, apply for assistance, and prove you owned what's now gone. It's common enough that FEMA maintains a dedicated Replacing Vital Documents hub walking survivors through re-ordering everything from Social Security cards to green cards, agency by agency, one at a time. Replacement works, but it's slow — and it starts from zero if you can't remember a policy number or an account list that burned.
What FEMA actually tells you to keep, and where
The federal answer to this is genuinely good, and worth reading first-hand. FEMA's Emergency Financial First Aid Kit (EFFAK) is a checklist for gathering household identification, financial, insurance, and medical documents into one place before you need them. Its companion guidance, Safeguard Critical Documents and Valuables, covers where those copies should live: paper originals in a fireproof, waterproof box or safe, or a bank safe deposit box — and for the digital half, it says to "store electronic copies of important documents in a password-protected format on a removable flash or external hard drive," or to consider a secure cloud-based service. The same guidance family is also careful about the passwords themselves, warning against keeping written password lists together with the document copies they unlock. All of that is sound. But notice that "password-protected format" is the entire technical specification. The advice tells you the property you need and leaves the mechanism — the part that decides whether a found go-bag drive is an inconvenience or an identity theft — entirely up to you.
The tension inside "keep copies everywhere"
Here's the structural problem an emergency document kit has that almost no other sensitive file does. For the kit to do its one job — surviving a disaster that takes your house — it cannot live only in your house. It has to be spread out: a USB drive in the go-bag, a copy in a cloud account, maybe a copy with a relative in another city, exactly as the guidance suggests. But this particular folder is the densest identity-theft target a household can assemble — Social Security numbers, passport scans, account lists, insurance policies, signatures, all curated into one place by you, for completeness. Kept as plaintext, every copy you spread multiplies the exposure: the go-bag drive that's lost or stolen, the cloud account that gets phished next year, the relative's laptop you have no control over at all. Redundancy and exposure rise together, and you're pushed toward a bad choice between a kit too centralized to survive and a kit too scattered to be safe. Encryption is the tool that breaks exactly this trade-off. Encrypt the kit once, with a strong passphrase, and the copies stop being the secret — they're ciphertext, and you can spread them as widely as resilience demands. The only thing that stays precious is the passphrase, and the passphrase doesn't multiply: it lives in your head and your household's, not on any of the drives.
Take "password-protected format" seriously
That one phrase in the federal guidance is doing a lot of work, because "password-protected" describes a spectrum. At the weak end it means a viewer application that declines to open a file until a password is typed — a lid, not a lock, with the contents sitting underneath it unchanged. At the strong end it means the file itself is transformed: a key is derived from your passphrase through a deliberately slow key-derivation function, the contents are encrypted with a modern authenticated cipher, and the result is indistinguishable from random noise to anyone without the passphrase — including whoever finds the drive, breaches the cloud account, or borrows the relative's laptop. For a kit that may sit unattended in three places for a decade before the day it matters, only the strong end is worth anything, and it's worth knowing what to look for by name: a real key-derivation function (PBKDF2, scrypt, or Argon2) standing between a human passphrase and the key, and authenticated encryption (AES-GCM or ChaCha20-Poly1305) so that tampering or corruption fails loudly at decrypt time instead of silently handing you altered documents in the middle of an insurance claim.
Building the kit in an afternoon
The mechanics are less work than they sound, and September is the designated month for finally doing them. Work through the EFFAK's checklist and scan or collect what it names — identification, insurance policies, deeds and titles, medical and medication lists, account inventories — into one folder. Encrypt the files with a single strong passphrase; one passphrase for the whole kit is a deliberate choice here, because this is a kit your household needs to be able to open on a bad day, not a set of accounts needing unique credentials. Then place copies exactly where FEMA's guidance points: one on the go-bag drive, one in whatever cloud storage you already use, one with the out-of-area contact your family plan names. Two rules keep the scheme honest. First, the passphrase travels by memory, not beside the copies — every adult in the household should know it, the same way everyone knows the meeting point, and the guidance's warning about storing password lists with your documents applies squarely here. Second, the kit gets refreshed when the documents do — a new policy, a new house, a new family member — and the old encrypted copies get replaced, not accumulated.
What an encrypted kit honestly can't do
Four limits, stated plainly. First, an encrypted scan is not a certified document. Agencies and courts will still require certified copies, and you'll still order replacements through the channels FEMA's replacement hub lists — the kit's job is to make that process start from everything (numbers, issuers, proof of what existed) instead of from memory. Second, and this is the caveat that cuts hardest in a disaster context: there is no recovery. Not from NearSeal, not from the mathematics. A passphrase your household can't produce during the most stressful week of your lives means the kit might as well have burned. That's why it should be memorable, shared, and actually rehearsed — an unopenable kit is a failure you discover at the worst possible moment. Third, the same logic applies to absence: if the kit might need opening when you're not there, the passphrase must already be with the people who'd open it. And fourth, paper still matters. FEMA recommends physical copies in a fireproof box for good reason — a regional disaster can mean no power, no network, and a borrowed phone, and ciphertext is no help to anyone standing in a shelter without a computer. The encrypted kit is the copy that survives and travels; it complements the paper, it doesn't retire it.
Where NearSeal fits
A tool for encrypting your most sensitive documents shouldn't itself be a place those
documents travel to. NearSeal runs entirely in your browser: the files and passphrase never
leave your device, there's no account and no upload, and you can watch the network tab confirm
nothing is transmitted. The format is AES-256-GCM with the key derived from your passphrase via
PBKDF2-SHA256 at 220 iterations — the strong end of "password-protected," by name.
Two properties matter specifically for the emergency use case. Decryption needs nothing
installed: whoever holds a copy — your spouse on a hotel computer, the relative holding the
backup — opens the same website, drops the file in, and types the household passphrase; the file
is recognized by its bytes, not its name. And for a kit meant to outlast any single website,
there's the opt-in age-encryption.org format: an age
file opens in the official age CLI, in rage, and in any other
age-compatible tool, so the kit you seal this September is still openable in twenty years by
tools that have nothing to do with us. Two things NearSeal deliberately is not: it is not
storage — the go-bag drive, the cloud account, and the relative are yours to arrange — and it is
not a recovery service. The copies are yours to place, and the secret is yours to keep.