Tax Office OS

Backup

We will hold your backup. We cannot open it.

Local-first has one honest weakness, and it is not privacy. It is the laptop that gets stolen, dropped, or reimaged by IT on a Tuesday. So you can seal the workspace and hand it to us for safekeeping. What leaves your machine is ciphertext: scrambled bytes that mean nothing without your password. The key stays in your head.

What we store Illustration

Everything the server can see

Three fields, and this is their shape, not a sample from a real account. Hosted backup is built and not switched on, so there is no stored record to quote.

Sealed blob
AES-256-GCM ciphertext
Size
a byte count
Last written
a timestamp

What it cannot see

  • Your clients' names, or how many you have
  • Any Social Security number, ever
  • Any income, deduction, or tax figure
  • The return itself, in any form

The part nobody puts on a pricing page

Lose the vault password and the backup is gone. There is no reset link and there will never be one, because a reset link is a copy of your key sitting somewhere you do not control. That is not a missing feature we ran out of time for. It is the same property that makes the sentence above this one true: we cannot open your backup for an attacker, a subpoena, or a support ticket, and those are the same capability wearing different clothes.

  • Live today: the encrypted backup file. Your whole workspace, sealed on your device, saved wherever you already keep backups. No account, no service, no us.

  • Built, not switched on: hosted backup. When it ships it is off by default and opt-in per advisor.

Seal a workspace and look at the file yourself.