What's Actually Inside Your Account Data Export

Requesting an export of your account data produces a single JSON file containing everything tied to your login across every workspace you're a member of — not just the workspace you happen to be viewing when you click the button. It's generated on demand, not on a schedule, and it's worth knowing exactly what's inside it before you rely on it as a backup, hand it to an accountant, or use it as a reference for what the platform actually stores about you.

It Covers Every Workspace You Belong To, Not Just One

The export starts by looking up every workspace membership tied to your account, then builds a complete data block for each one — regardless of whether you're the owner or just a member, and regardless of which workspace was active in your browser at the time. If you belong to three workspaces, the export contains three full workspace sections, each with its own clients, invoices, expenses, payments, and business profile. Each section also notes your role in that workspace and whether you're the owner, so if you're a member of a workspace you don't administer, the export still tells you exactly what your standing in it is.

What's Included Per Workspace

For each workspace, five categories of data are pulled in full. Every invoice record is included, stored as it's grouped internally — invoices are reconstructed from their raw line-item and metadata rows into a single coherent document per invoice, so the export reads as a list of invoices rather than a confusing flat list of database rows. Every saved client record is included, with name, billing details, contact email, and creation date. Every expense record is included in full, covering vendor, category, amount, currency, and rebilling status. Every recorded payment against any invoice in the workspace is included, showing the payment history independently of whatever the invoice's current summarized status says. And the workspace's business profile — the company details, address, and settings used to populate invoices — is included as a single object, or explicitly set to null if the workspace never had one configured.

What's Included at the Account Level

Outside the per-workspace sections, the export includes a small block of account-level information: your user ID, your email address, whether your account is verified, whether two-factor authentication is currently enabled, and your account creation date. Notice what's deliberately absent from that list — there's no password hash, no two-factor secret, and no backup codes. The export tells you *that* 2FA is turned on, which is a fact about your account's current configuration, but it never includes anything that could be used to reconstruct or bypass your authentication. That's consistent with how credentials are handled everywhere else in the product: they're written to be checked against, never to be read back out, even by an export mechanism the account owner explicitly requested.

On-Demand, Not Automatic

There's no scheduled export, no background job periodically snapshotting your data, and no email digest with an export attached. The export is generated fresh, synchronously, the moment you request it — the file you download is a real-time snapshot as of that exact request, not a cached copy from some earlier point. This means two exports taken minutes apart, before and after you edit an invoice, will genuinely differ. It also means there's no export history to browse — if you want a record of what your data looked like at a specific past point in time, you need to have actually run and saved an export at that time, since none are being generated or retained on your behalf automatically.

The File Itself

The export is delivered as a downloadable JSON file, with a filename that includes the export date, and served with headers that tell the browser to download it as an attachment rather than try to display it inline. JSON was chosen over something like a PDF or CSV bundle because the underlying data isn't naturally tabular — invoices contain nested line items, workspaces contain nested clients and expenses — and a single structured JSON document preserves those relationships in a form that's both human-readable if you open it in a text editor and directly parseable if you want to script something against it, like importing your data into another tool or running your own custom analysis over it.

Why This Exists Separately From Individual CSV Exports

The platform's financial reports — the aging report, the tax summary, the accountant report — each support their own CSV export scoped to that specific report's data. The account data export is a different tool solving a different problem: those report exports give you a curated, summarized view suited to a specific accounting task, while the account data export gives you the raw underlying records with nothing summarized or filtered out. If you need a tax summary for your bookkeeper, the tax summary CSV is the faster and more directly useful choice. If you need a complete, portable copy of everything the platform holds about you and your workspaces — for your own backup purposes, for migrating elsewhere, or simply to see the full picture — the account data export is the one built for that.

A Practical Note on Using It as a Backup

Because the export is comprehensive and self-contained, it functions reasonably well as an ad hoc backup — but it's a manual one, triggered by you, at whatever cadence you choose to run it. If having a genuinely current backup matters to your workflow, that means periodically running the export yourself rather than assuming one exists in the background. Nothing about deleting an invoice, closing a workspace, or any other in-app action automatically triggers a fresh export beforehand, so the safest habit is running one before any change you're not fully certain about, rather than treating the export feature as a safety net that's always quietly up to date.

How This Relates to Deleting Your Account

The account data export and account deletion are two entirely separate actions with no automatic link between them — requesting deletion doesn't trigger an export first, and running an export doesn't start any kind of deletion countdown. If you're planning to delete your account and want a copy of your data first, that means explicitly running the export yourself before you go through the deletion flow, not assuming one happens for you as a safety step along the way. Once an account is deleted, there's no path back to generating an export of what used to be there, since deletion removes the underlying records the export function reads from — the export has to happen first, as its own deliberate action, if you want a copy preserved.

If You're a Member, Not an Owner

Because the export pulls every workspace you belong to regardless of role, being a plain member rather than the owner of a given workspace doesn't exclude that workspace's data from your personal export. You'll still get that workspace's clients, invoices, expenses, payments, and business profile included in full, with your role and non-owner status clearly labeled on that section. This is worth being mindful of if you're a contractor or team member on someone else's workspace and you export your own account data — the resulting file contains real client and financial data belonging to a workspace you don't own, which is appropriate for your own personal record-keeping of work you were genuinely part of, but isn't something that should be forwarded on or treated as casually shareable the way, say, a copy of your own personal profile information would be.

Invoices Are Reassembled, Not Dumped as Raw Rows

Internally, an invoice isn't stored as one single database row — it's stored as a group of related rows sharing a common invoice group identifier, which is how line items, metadata, and the invoice's core fields stay organized together. Rather than exporting that raw, fragmented structure and leaving you to reassemble it yourself, the export groups those rows back together into one coherent object per invoice before it ever reaches the output file. The result reads the way you'd actually expect an invoice list to read — one entry per invoice, with its details nested inside it — rather than exposing the underlying storage structure the product happens to use internally. This same grouping logic is shared with the financial reports described elsewhere, which is part of why an exported invoice list and a report built from the same underlying data always agree with each other on the numbers.