Your data
What is stored, exporting and re-importing the whole account, and deleting transactions.
What is stored
Per workspace: your transactions, the original statement files you uploaded, your categories, your rules, any CSV format mappings you have confirmed, and the results of your last duplicate scan.
There are no bank credentials, because you are never asked for any. Nothing is linked to your accounts, so there is no standing connection to your bank for anyone to misuse later — the app only ever sees the files you hand it.
Nothing about your spending is sold, and nothing is placed in front of you because someone paid for it to be there. There are no offers between your transactions and no partner cards to recommend.
The one thing that leaves your workspace
Nothing you upload is ever pooled with anyone else's. There is no shared merchant list assembled from what other people categorized — an earlier version of this app had one, and it was removed.
What does leave, and only during a categorizing pass, is a question about a merchant the built-in merchant list doesn't recognize. The language model is sent the normalized merchant name, one representative description line from your statement, and how many times it appeared, along with the names of your categories so it has somewhere to put the answer. It is not sent amounts, dates, balances, account numbers, or anything identifying you, and it is asked about merchants rather than about individual transactions.
Nothing comes back the other way either: the answer becomes a rule in your workspace and nowhere else.
The app sends nothing else on its own. Send feedback, in the ⋮ menu, is something you send yourself: it posts what you typed to the app's public feedback board on Convo, along with an anonymous browser id so your notes can be grouped together. It carries no email, no workspace, and no transactions, so don't paste anything into it you wouldn't post in public.
The built-in list itself never leaves, because it never has to. It is a few hundred well-known brands written into the app, the same for everyone, which is why an obvious merchant is categorized correctly on your first upload without a model being asked about it at all.
Export
⋮ → Export JSON downloads your whole account as one file: every category, every rule, and every transaction — including the raw statement text, balances, and any overrides you have set, so nothing is lost in the round trip.
It's always the complete account. The filters you have on screen are deliberately not applied, because a backup that quietly excluded whatever you happened to be looking at would be a bad backup.
Any member of a workspace can export it, viewers included.
Import
⋮ → Import JSON loads a bundle back. Every section is optional, so a file with only rules is a perfectly valid thing to import.
The order matters and is handled for you: categories and rules land first, then transactions are written with the merged rule set already applied. Both are idempotent — a category you already have is kept as it is, and a rule functionally identical to one you already have is skipped rather than duplicated. Any genuinely new rules kick off a background pass so they reach transactions that were already there.
When it finishes you get a count of what was created, imported, and skipped.
An import can take a while on a large bundle and the header shows an Importing… indicator for its duration. It's the one long operation in the app that can't report a percentage — the request writes everything and reports once, so a progress bar here could only be invented.
Import and export together are how you move an account between workspaces: export from one, switch, import into the other.
Deleted transactions
Deleting a transaction from the Transactions screen or the uncategorized queue is a soft delete. The row disappears from every view and every total, but it's still there.
⋮ → Deleted transactions lists them with the date each was deleted, and restores any of them.
The one exception is a duplicate commit. Rows removed by committing decisions in the Duplicates workbench are hard-deleted and cannot be recovered — the point is that they should never have existed. See Duplicates.
Re-uploading a statement does not resurrect a deleted transaction: the tombstone is recognized and the row stays deleted. Restore it from the Deleted view instead.
Deleting a workspace
An owner can delete a shared workspace from Workspace settings…, which removes its transactions, categories, rules, and uploads along with it.
Your personal workspace can't be deleted from inside the app — it is your account's data. Export first if you want a copy of anything.