ThereflectionroomsalonBudgeting app transparency project
Pre-publicationDraft contact details require verification before launch or advertising.
Portability and exit

Can You Take Your Budgeting Records With You?

Wide view of folded garments strapped to concrete blocks on a sunlit surface
Editorial metaphor: portability depends on what remains bundled and transferable.
Portability audit

An export is not automatically a migration

Portability depends on which records leave, their format, and whether another system can interpret them.

01

Export availability

Question: Can plan and transaction information be exported?

Evidence: A current first-party document naming platform, scope, and file type.

02

Export format

Question: Is the result CSV, TSV, spreadsheet, PDF, or proprietary?

Why it matters: A widely opened file may still omit structure.

03

Included fields

Question: Are categories, history, notes, scheduled items, targets, and attachments included?

Evidence: Explicit documentation, not the word “export.”

04

Access after cancellation

Question: How long does normal access continue?

Evidence: Current subscription and cancellation terms.

05

Account deletion

Question: Is cancellation separate from deletion?

Evidence: Current deletion and privacy documentation.

06

Local readability

Question: Can files open without the original application?

Evidence: Formats, requirements, and proprietary dependencies.

07

Category migration

Question: Can another system recreate names, notes, history, and rules?

Why it matters: Moving rows is not always moving the workflow.

Exit record

What to document before a change

  • Date the documentation was checked.
  • Available export types and known exclusions.
  • End of normal access.
  • Stated retention behavior.
  • Difference between cancellation and deletion.
  • Information requiring manual reconstruction.