Deleting an account, or a whole workspace, runs on a clock. Access stops straight away, the permanent erasure happens later, and there is a window in between in which the deletion can still be called off. This article explains that clock, who can stop it, and what is left once it runs out.

There are two lengths, and which one applies depends on what is being deleted.

• Deleting a whole workspace: 30 days. The organization and every record in it are permanently erased 30 days after the deletion is accepted.
• Deleting a single account: 14 days. That person and the personal data held for them are permanently erased 14 days after the deletion is accepted.

A workspace can be given a longer window, up to 90 days, which we set on request. In abuse cases and in response to a legal takedown the window can be zero, which means the deletion is finalized immediately and there is no cancellation period at all. The date that matters is always the one stated in the email we send when the deletion is accepted, not the default named here.

Access ends when the deletion is accepted, not when the window closes. Everyone affected is signed out within seconds and cannot sign back in, even though the erasure itself is still days away. If you need an export, take it before the deletion is accepted.

When a deletion is accepted we email a notice. It names what is being deleted, the date the erasure runs, and it carries a link to a status page. Opening that link shows the current state of the deletion and its completion date without signing in, which is what makes it useful to someone who has just lost access.

Two people can cancel: the person who asked for the deletion, and an administrator of the workspace being deleted. Either of them signs in and cancels it from the status page or from Admin > Users. Cancelling restores the account and everything the deletion had not yet touched, and nothing is erased. It does not undo the sign-out, so anyone who was signed out has to sign in again.

A whole-workspace deletion is cancelled the same way, by the person who asked for it or by any administrator of that workspace, and the section below covers it in full. A member deletion that leaves no administrator behind is the one case that has to go through support instead, because that request removes every person who could otherwise have cancelled it. Do that quickly: the window is the only chance, and once it closes the erasure is permanent and cannot be reversed by anyone.

When the window closes and the erasure completes, we send one last email to the address that was deleted. It confirms what was deleted and the date it finished, states that the data is gone from our production systems and that backups holding it are purged within 90 days, and it names the one thing we keep: a one-way hash of the address plus its bare domain, retained for 13 months so the same address cannot open repeated trial accounts. The receipt carries no CRM records and no message content. Keep it if you need evidence of the deletion for your own compliance records.

The address is blocked for exactly the length of the window and released at the end of it, so the address can be used for a new account as soon as the deletion completes. A new account started that way is genuinely new: nothing from the deleted one is restored, re-linked, or visible in it.

Invitations sent to this address by other workspaces are not affected; only invitations from the workspace being deleted are cancelled.

A work address that later belongs to a different person can be used to open a new account, because the address is released when the deletion completes.

Deleting a whole workspace is its own deliberate action, not something that happens as a side effect of removing the last person. Only a super admin can start one, from Admin > Workspace. An administrator who is not a super admin can open that page and reads who to ask instead of a blank refusal. Once it is scheduled it follows the 30-day window described above.

It takes six steps, in order, and nothing is scheduled until the last one is confirmed. Leaving the page part-way through abandons the whole thing, and starting again begins at step one.

1. What gets deleted. A summary of the workspace as it stands right now: how many members it has, how many records of each kind, which integrations and mailboxes are connected, and its billing state. Everything named there goes, so read it before going on.
2. Export your data first, or continue without export. The first button starts an archive of the workspace and the second skips it. Nothing is deleted either way at this point, but this is the last convenient moment to take a copy, so skipping it is a choice rather than a default.
3. The subscription check. A workspace with a running subscription cannot be deleted, because the deletion would leave a live, recurring charge behind with nothing left to bill for. If a subscription is active the step says so and links straight to billing: cancel it there, then come back to this step. If none is active the step says that too, and you continue.
4. Type the workspace name. Type the name of the workspace exactly as it is written, which proves you mean this workspace and not another one you also administer. A near miss does not count, and the step will not advance until it matches.
5. Verify it is you. The same identity check this workspace already uses for its other sensitive admin actions. Nothing can be scheduled until it succeeds, so an open session on an unattended machine is not enough on its own.
6. Schedule the deletion. The last step states the exact instant the workspace closes, in your own time zone with the zone named, and the same instant in UTC underneath so there is no arithmetic to do. Confirming here is what starts the clock: every member is emailed, access ends within seconds, and the cancellation window begins.

What the archive contains, and how long it lasts. If you asked for one at step 2, the archive holds the workspace data as it stood at that moment: its records and their field values, notes and logged activity, the files attached to them, and the stored message history. It is prepared in the background, so it is not always ready the second you finish the steps. It is not a backup: it stays downloadable for exactly as long as the cancellation window lasts, from the status page and from the deletion emails, and it is deleted when the deletion finalizes, along with everything else. Download it before the window closes if you want to keep it.

Calling a workspace deletion off. Anyone who can sign in can stop it while the window is still open: the person who asked for the deletion, or any administrator of the workspace. Either of them signs in and cancels from the status page or from Admin > Users. It restores the workspace and everything the deletion had not yet touched, and it does not undo the sign-out, so everyone signs in again.

Deleting one member rather than the whole workspace is a different job, done from that person's own row. The step-by-step instructions live in User Management.

The quickest route is to reply to the deletion notice itself, which reaches us with the details of the deletion already attached. You can also write to support@laureo.io. If the window is close to closing, say so in the first line so it is handled in time.