- Effort
- an evening
- What changes
- Account takeover
When to tickThe manager is in use and every active account has its own generated password.
Create a password →A list of things to do, with the ticks stored in this browser. Work through it in any order.
15 to go. Work in any order.
When to tickThe manager is in use and every active account has its own generated password.
Create a password →When to tickThe master phrase is long, unique, and not stored beside the vault.
Build a passphrase →When to tickSigning into primary mail requires a second factor that does not depend on SMS.
15 minWhen to tickCurrent backup codes are offline and reachable if the second factor is lost.
10 minWhen to tickOld passwords were checked and every breached one was replaced with a unique value.
Check →When to tickFull-device encryption is on for laptop and phone, with the recovery key stored separately.
20 minWhen to tickThree copies exist on two media types, one off-site, and a test restore succeeded.
an eveningWhen to tickDevices use the chosen trusted or self-run resolver and the setting has been verified.
Test →When to tickAutomatic updates are enabled for the operating system and primary browser.
5 minWhen to tickThe local report was reviewed and unusual settings were understood or simplified.
Open the report →When to tickActive secrets were removed from pinned threads and moved to an appropriate vault.
Keys →When to tickSensitive transfers use an encrypted artifact and the passphrase travels over another channel.
Seal →When to tickUnused accounts were listed, needed data was retrieved, and the accounts were deleted or anonymized.
an eveningWhen to tickA short current map identifies devices, storage, backups, and who can restore them.
an eveningWhen to tickA trusted person knows where to find usable instructions for access to the essentials.
an eveningThe list starts with what removes the most risk per hour spent.
Most losses start with a reused password. One evening with a manager removes that whole class of trouble.
These decide what happens when hardware is lost or breaks — the ordinary case, not the dramatic one.
Own resolver, own storage, own model. This is where privacy stops being a setting and becomes ownership.
Items that close with something on this site link straight to it: passwords, keys, sealing, the fingerprint report, the resolver test.
The company profile swaps the whole list: a team fails in different places than a person.

In localStorage for the current site, separately for both profiles. Another subdomain or device starts with its own state; clearing site data removes it.
Copy it as text with the ticks in place, print it, or export its state as JSON. Imports are fully validated before they replace the current ticks.
A list you finish beats a list you admire. These are the items that actually change the outcome; everything else is a project, and projects deserve their own plan.
Mail, files, knowledge and AI on hardware you control. We plan it, build it and hand over the keys.