Skip to main content

Deleting your organization

Administration → Billing & Subscriptions → Danger zone. The owner only.

This is the erasure path. It deletes the organization, everything in it, every uploaded file, and every member account — and it cancels your subscription at the same time. There is no undo and no backup to restore from.

It exists because you are entitled to it. Under the GDPR's right to erasure (Article 17) you can ask for your data to be deleted, and you should not have to open a support ticket to do it.

What is deleted​

Everything the organization holds:

  • Every project, and the whole test library inside it — folders, test cases, steps and comments.
  • Every bug hunt and its results, issues and comments.
  • Every exploratory session, its notes, issues and comments.
  • Every automation run, its reports, its recorded tests and results, and the error rows built from them.
  • Every requirement, dashboard, shared step and custom field.
  • Every API token and AI connector.
  • The Jira integration and its stored credentials.
  • The activity log.
  • Every uploaded file — screenshots, videos, attachments and CI reports — removed from object storage, not just from the media library.
  • Every member account in the organization, including yours and including guests. There is no account left behind to sign in with.

The confirmation lists the actual counts before you type anything, so you can see what you are about to lose rather than take it on faith.

What is not deleted​

  • Emails that have already been sent. A notification delivered last week is in somebody's inbox and we cannot reach it.
  • Automation source and tag names. These are shared across every organization on the platform — "Playwright", "smoke", "regression" — so there is no row belonging to you to remove.

:::tip Take a copy first Export your organization's data before you start. The export keeps working throughout the waiting period, but once the deletion runs there is nothing left to export. :::

How it works​

  1. Open the Danger zone on the billing page. Only the owner sees a working button; admins cannot do this.
  2. Read the counts. The dialog says how many projects, tests, files and accounts will go.
  3. Confirm four things. Type the organization's name exactly, enter your account password, enter your authentication code if you have two-factor enabled, and tick the box confirming you understand the deletion is permanent and covers everybody's data, not only yours.
  4. Your subscription is cancelled immediately. You are not billed for the waiting period below. If your plan had a paid period still running, it is set to end at the close of that period; otherwise it stops at once.
  5. Seven days pass. The organization works exactly as normal, and a banner at the top of every screen tells everybody the date it will be erased.
  6. The deletion runs. A nightly job carries it out shortly after the date passes. Everyone is emailed as it starts.

Three emails go out across that sequence: one when it is scheduled (owners get a one-click cancel button, everyone else gets the same facts), one if it is cancelled, and a final one as the erasure begins.

Nobody can be invited during the window​

While a deletion is scheduled, invitations are frozen. The Invite buttons on the Members page are disabled and say why, a pending invite sent earlier stops working, and both are refused by the server rather than just hidden.

The window is there so you can change your mind, not so the organization can carry on recruiting into something about to be destroyed — an invite accepted on day six would create an account, spend a seat, send a welcome email and be deleted the next night. Cancel the deletion and inviting works again.

The seven days are the point​

The window is there so a mistake, or somebody else using your signed-in computer, does not end your company's test history in one click. Erasure "without undue delay" does not mean the same second, and a week is short enough to satisfy that and long enough to notice.

You can stop it at any time before it runs, in either of two ways:

  • The button in your email. The notice sent to the owner carries a Cancel the deletion link. One click stops it — no sign-in, no password, so it works from a phone at the weekend. The link is single-use and only goes to owners; everybody else gets the same notice without it.
  • The Danger zone on the billing page. This one asks for your password again, because anybody holding a live session can reach it — so that somebody who scheduled a deletion against your wishes cannot quietly cancel and reschedule it to hide what they did.

Cancelling the deletion does not bring your subscription back. It was cancelled deliberately when you asked for the deletion. Pick a plan on the same page to carry on.

Why the password​

A signed-in session proves somebody signed in as you in the last day. It does not prove it is you at the keyboard now. For the one action with no undo, we ask again at the moment you do it — the same reason deleting a single project asks for it.

Typing the organization's name is not security; anybody who can reach this page can read the name. It is there so the confirmation cannot be satisfied by a reflex.

If you only want to stop paying​

You do not need this. Cancel the plan instead, further up the same page. Your organization moves to the no-plan state: everything you have stays readable, and nothing is deleted. You can pick a plan up again whenever you like.

Use deletion when you want the data gone.