The Account Audit is the inventory: one row per online service, where it came from, how recently it was used, and whether it matters. It is included in every plan.

​
Starting from empty

Before the first audit the page shows one panel, Find every account your executor will inherit, with three ways to begin: You can mix all three. Sample and scanned accounts sit in the same table, and the Dashboard line tells you which source ran last.

​
The table

Every account shows its name and domain, a Category badge (Email, Finance, Crypto, Government, Security, Subscription, Utility, Social, Storage, Shopping or Other), a Status badge and the date of the Last activity we saw. A gold shield beside the name marks a critical account. The Sort accounts control at the top of the panel orders the table by Last activity (the default), Name, Category or Critical first.

​
The row menu

The ellipsis at the end of each row opens three actions:
  • Mark critical / Unmark critical. Critical means losing this account locks the family out of others: the primary email, the password manager, the phone carrier, the bank, the tax account.
  • Mark closed / Reopen. Closed accounts drop out of the counts and the timeline but stay in the inventory.
  • Remove takes the row out entirely. Use it for a sender that is not really an account.

​
Adding an account by hand

Add account (top right) opens a dialog for anything the inbox scan cannot see: a bank that only sends paper statements, a device, a domain registrar, a safety-deposit box. Give it a name and a domain, pick a category, set the last activity date and flip Critical access if it matters. The entry appears in the table straight away.

​
The activity timeline

Under the table, the timeline draws the five most recent open accounts against the last two years, with a teal dot for active and a gold dot for inactive. It is the quickest way to see which services have gone quiet.

​
What leaves your inbox

Nothing but a sender’s domain, display name, message count and last-seen date. The scan never reads message bodies, never stores the access token, and never runs without you pressing the button. See What we store.