Exports and deletion#

Export your data#

My profile → Sessions and data → Export. The export downloads as a single JSON file, laver-export-<your-uuid>.json, built on demand. No request, no wait, no ticket.

It contains everything on your account and everything you authored:

What it does not contain:

• Attachment files. File contents are not bundled; download anything you need from the tickets themselves before you leave.
• Work authored by other people — tickets, comments and wiki pages written by colleagues, even on boards you can reach.
• Board structure — columns, positions and settings are not included.

This export is per person. For everything in a workspace — including work your colleagues wrote — see the whole-workspace export below.

It is built in one pass, so a very large history can take a while. And it works in every billing state, including a workspace that has gone read-only over an unpaid invoice — you should never have to pay to get your own data back.

Via the API: GET /profile/export with a session token. API keys are not accepted.

Export a whole workspace#

Owners and admins only. Admin → Export. Press Export workspace, leave the page if you like, and come back for the download. It is prepared in the background, because a workspace with a hundred thousand tickets is more work than a page load can wait for. Nobody has to open a ticket with us to get a copy of their own data — this is the button that does it.

• One at a time. Asking again while one is being prepared returns the export already in flight rather than building a second copy.
• Seven days. A finished export stays downloadable for a week, then the file is deleted. The record of it stays, so you can always see that an export was taken, when, and by whom.
• Every billing state, exactly like the personal export above — a workspace that has gone read-only over an unpaid invoice can still be exported. A workspace suspended by us cannot.
• Signed in, not automated. API keys are refused. Taking a complete copy of the company's data is something a person does deliberately.
• Requesting, building and downloading are all recorded in the audit log.

How long it takes, and what to expect#

A request is picked up within a minute and then takes as long as the workspace is big: seconds for a young workspace, minutes for one with a hundred thousand tickets. There is nothing to keep open while it runs — the request is recorded the moment you press the button, and the file appears against it afterwards.

• We do not email you when it is ready. Come back to Admin → Export; the list reloads every time you open the tab, and Check again refreshes a row that is still being prepared.
• The last twenty exports are listed, newest first, each with its state: Being prepared…, Ready to download, Failed, or Expired — ask for a new one.
• A build that fails is retried a few times, minutes apart, before the row gives up and shows Failed with the reason on it. Ask for a new one; a failed export never blocks the next request.
• Seven days start when the file exists, not when you asked, so a slow build does not eat into the week you have to download it.

What the file contains#

One JSON document, laver-workspace-export-<export-uuid>.json:

{
  "format": "laver.workspace-export",
  "format_version": 1,
  "exported_at": "2026-08-13T09:00:00.000Z",
  "attachments": "references",
  "workspace": { "uuid": "…", "name": "…", "slug": "…" },
  "data": {
    "members": [],
    "labels": [],
    "boards": []
  }
}

format_version is the contract. Fields may be added within a version; anything renamed, removed or restructured comes with a new number, so a file you archived two years ago still says how to read it.

data holds these sections, in this order:

Archived boards, tickets, comments and pages are included, each with its archived_at date. Deleting in Laver is archiving, and an export that silently dropped the bin would be missing work you can still restore.

What it deliberately leaves out#

• Attachment files. Each attachment is listed with its name, type, size and storage key — a reference, not the bytes. Otherwise a workspace with 40 GB of files produces a 40 GB download that no browser finishes. Download the files you need from the tickets themselves.
• Bodies of private wiki pages you cannot read. A private page still appears, with its title, author and position, and its content is replaced by "content_withheld": true. An export must not become a way around page-level access — it shows you exactly what the wiki shows you.
• Published board and page links. The share token is a live credential: it serves the board to anyone holding it. Manage those in Admin → Published.
• Billing and payment details. Your invoices are in Billing; they are our record of you rather than your data.

Via the API#

All four take a session token; API keys are refused.

Poll either of the middle two until download_state is ready, then fetch the download. The other values are building, failed (ask for a new one) and expired (the seven days have passed).

Delete a workspace#

Owners only. Admins cannot delete a workspace.

Deleting is a soft delete. The workspace is archived and every membership in it is deactivated, which is what actually revokes access. Immediately:

• The workspace disappears from everyone's switcher.
• Its boards, tickets and wiki become unreachable for everyone, including you.
• Every API key scoped to it stops working, because the memberships behind them are no longer active.
• The Stripe subscription is cancelled straight away, so a workspace you have closed does not keep billing. The unused part of the period is credited to your Stripe customer balance rather than refunded to the card — Stripe spends a balance on a future invoice, so it comes back only if you subscribe again.
• The deletion is recorded in the audit log.

What deleting a workspace does not do:

• It does not erase the data. Boards, tickets, comments and wiki pages are still stored; they are simply unreachable.
• It is not self-service to undo. Restoring a deleted workspace means reactivating its members by hand, which is a support action. Ask before you assume it is gone for good, and export first if you might want the contents.

In the rare case Stripe is unreachable at the moment you delete, the deletion still goes through and the cancellation is left for support to complete. If you see a charge for a workspace you deleted, contact us.

Delete your account#

My profile → Delete account. You have to enter your password and type DELETE to confirm.

Transfer your workspaces first#

If you are the owner of any workspace that still has other active members, the deletion is refused with 409 and the workspaces are listed. Nobody would be left who could administer or pay for them. Transfer ownership — or remove the other members — and try again.

Deleting your account does not delete the workspaces you own, and does not cancel their subscriptions. If you own a workspace nobody else is in and you want it closed, delete the workspace first, then delete your account.

What happens immediately#

• Every workspace membership is deleted, so you lose access to all of them.
• Every API key you hold stops working.
• Your board access and your ticket assignments are deleted everywhere.
• Every session is ended on every device.
• Your account becomes a tombstone: the email address is released, verification is cleared, and two-factor is switched off with its secret and backup codes erased. You cannot sign in, and the account cannot be reopened.
• A confirmation email is sent to your address.
• user.deleted is recorded in the audit log of each workspace you were in, so your colleagues can see what happened.

What stays, and why#

Tickets you created, comments you wrote and wiki page versions you authored stay put. Deleting them would tear holes in your colleagues' boards and wiki history — conversations would lose half their turns, and pages would lose their edit trail. They remain attributed to a deleted user.

After 30 days#

A scheduled job scrubs what is left of the account: your name becomes Deleted user, and your phone number, profile image, stored two-factor data and any outstanding verification or reset codes are erased. The password is replaced with a value nothing can sign in with. The record itself remains as an anonymous tombstone so the content above keeps its history.

Soft deletes in short#

Export before you delete anything you may want later. Both exports are self-service and both work right up to the moment you delete: your own data from My profile → Sessions and data, the workspace from Admin → Export. After the deletion the buttons are gone, so take the copy first.