Leaving takes your data with you

A scheduled full teardown that cancels billing, removes the connected sub-account, unlinks the owner's login, and wipes every account-scoped table in dependency-safe order.

What it is

Deleting an account is a scheduled job rather than an instant button, with a delay before it runs. When it runs it cancels the subscription so billing stops, deletes the connected external sub-account, unlinks the owner's login without deleting the person, wipes every account-scoped data table in a foreign-key-safe order, and archives the original signup record so the billing history survives.

Also called: cancel my account · delete my data · close account · get my data out · off-boarding

See it
Leaving takes your data with you
Apr
May
Jun
Jul
Gideon Alt — 40×64 Shop
Framing
Delia Yoder — 30×40 Garage
Concrete
Delia Yoder — Barndominium
Trim
Ivy Brubaker — Equipment Storage
Framing
Marlin Hoover — Equipment Storage
Concrete
Framing crewConcrete crewTrim crew
A step diagram of the teardown order with per-step success/failure reporting — orgDeletion.ts ORG_SCOPED_TABLES sequence. Sample data — no customer information appears here.
How it works
  1. 1Cancel the platform subscription via the linked signup record so billing stops first
  2. 2Delete the connected external sub-account (idempotent if already gone)
  3. 3Unlink the owner from the account — never delete the person
  4. 4Wipe every account-scoped table in dependency-safe order, then settings singletons, then the account row
  5. 5Archive the linked signup with reason 'account_deleted' rather than hard-deleting the billing record
  6. 6Each step is independent and reported; a failed step never blocks the rest and the run is idempotent
Why we built it

The worst version of leaving is the half-finished one — the data is gone but the card is still being charged, or the subscription stopped months ago and the customer list is still sitting on a server. Closing an account now cancels billing, removes the connected sub-account, unlinks the owner's login and wipes every table of that company's data in an order that leaves nothing stranded. A step that fails does not block the rest and the whole thing is safe to run again, because deleting most of a company's data and retrying the remainder beats deleting none of it. One exception is deliberate: the signup and billing record is archived rather than destroyed, since a contract has to outlive the data it covered.

The problem
  • Cancellation leaves data behind or leaves billing running
  • A single failing step blocks an entire teardown
Sound familiar?
What you get
Billing stops first, before anything else
Every account-scoped table is wiped, in the right order
Retries are safe, and the billing record survives for both sides

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →