Data & deletion

Getting everything out, and having it erased

Full export is a permanent feature, not a retention tactic. A product whose entry story is “files in, no bank login” has to be able to say files out too.

The product promise is no lock-in. That closes the loop the landing page opens: statements go in as files you control, and they come out the same way.

What is stored

Confirm this list against the schema before publishing, and keep it specific — a vague inventory reads as evasion.

  • Entities you create, and the accounts mapped to them.
  • Transactions imported from statements: date, description, counterparty, amount, category, and whether the line was recognised as an internal transfer.
  • Loans, leases and invoices, with the payments recorded against them.
  • Goal inputs: age, invested capital, target withdrawal rate, logged deposits.
  • Account details: email address, and a password hash where email sign-in is used.

OPEN-02Are the uploaded statement files themselves retained after import, or only the parsed rows?

This changes the answer materially. Retaining the original file is useful for re-parsing after a bug fix, and it is also a second copy of the raw data to account for.

Export

OPEN-02Which formats can a user export, and does export cover everything or only transactions?

CSV per entity plus a single JSON of the whole account is the natural answer. Say whether goal inputs and invoices are included.

OPEN-02Can a user export after cancelling, and for how long?

Being able to export during the deletion window is the difference between no lock-in and technically no lock-in.

Deletion

OPEN-02How is deletion requested — in the app, or by email?

In-app and immediate is the answer that matches the one-click cancellation the pricing section promises.

OPEN-02How long between the request and the data actually being gone, including backups?

Must agree with the backup retention answer on the security page. Two different numbers across two pages is worse than one honest number.