What happens to your data after the account closes

Three different endings get called the same thing. Cancelling a subscription, letting an account go dormant, and deleting an account do different things to your data, and only the last one is a deletion.

Knowing which one you are performing matters, because two of them are recoverable and one is not.

The three endings, in order of severity

Cancelling the subscription ends the billing relationship. The account generally continues to exist, usually with reduced access. Your conversations are typically still there and typically still readable, though what remains accessible on a lapsed account varies by product and is the specific thing to check rather than assume.

Letting it go dormant is cancelling and then not logging in. The account exists, the data sits there, and whether anything eventually happens to it depends on the product’s own policy.

Deleting the account is the irreversible one. It removes the account and, on the product’s own schedule, the data with it. There is no version of this you can undo, and support cannot restore it.

Only the third destroys anything. If somebody tells you cancelling deleted their history, they either deleted the account or lost access to it, which is a different problem.

Access lapsing is not the same as data going

The distinction that catches people: a cancelled account may hide or limit your history without deleting it.

Reduced access looks identical to deletion from where you are standing. The practical consequence is that you cannot rely on a lapsed account as your archive — not because the data is gone, but because your ability to read it is now a product decision rather than a fact.

Which is the entire reason the export comes first, and why the copy on your own disk is the one that counts.

Do not assume any retention period

How long data survives after cancellation, after deletion, or in backups is stated in the product’s own terms and privacy documentation, varies between products, differs for team accounts, and changes over time.

Anyone quoting you a number for this is quoting a number that was true somewhere at some point. If the retention period matters to you — and for sensitive material it might — read the current terms of the specific account, and read them for the account type you actually have.

The two things worth checking specifically: whether deletion is immediate or scheduled, and whether the terms distinguish deletion from removal from backups. Those are commonly different, in ways that are reasonable and worth knowing about.

Deletion is usually the wrong default

Most people should cancel and leave the account alone, at least for a few months.

The reason is asymmetric risk. A dormant account costs nothing and occasionally turns out to be useful — when you discover the export was missing something, when a shared link needs checking, when a colleague asks about a conversation from last year. Deletion buys you nothing except the deletion itself.

Delete deliberately, for a reason: the material is genuinely sensitive, the account belonged to an employer, or you want the data gone as a matter of principle. Those are all good reasons. Tidiness is not, and tidiness is why most premature deletions happen.

If you do delete, in this order

Export and verify. Replace shared links. Revoke integrations — from the other services, since deletion does not do it for you. Confirm the archive is stored properly, in more than one place. Then delete.

Also check that deletion is not entangled with something else: an identity used to sign into other services, an API arrangement under the same account, a team seat somebody else depends on. Deleting an account that is also a login is the one version of this with consequences beyond the assistant.

What moves

WHAT MOVES — closing an account

  · Your exported archive
                    → unaffected by any of the three
                      endings. It is a local file.

  · History inside a cancelled account
                    → typically remains, access varies.
                      Not a copy you can rely on.

  · Access to generate a new export
                    → commonly STAYS BEHIND once the
                      account lapses or closes.

  · Shared links, integrations, saved
    structure
                    → STAYS BEHIND. Deletion does not
                      tidy these up for you.

  · Deleting the account
                    → IRREVERSIBLE. No restore, no
                      support recovery, no undo.

  · Deleting an account used as a login
                    → IRREVERSIBLE beyond the assistant.
                      Check what signs in with it first.

Your archive is not affected by any of this

Worth stating plainly because the anxiety in this subject usually attaches to the wrong object.

Once the export is on your disk it is yours. Cancellation cannot reach it, deletion cannot reach it, and a retention policy has nothing to say about it. Everything on this page is about the copy that lives on the other side.

That is the whole reason the order of operations is export, verify, then cancel: it converts a question about somebody else’s policy into a file you control.

What is lost regardless

Deletion takes the things that had no export format — the organisational structure, the accumulated memory, whatever the product inferred — and those were never coming with you anyway.

What deletion adds is the loss of the fallback. A dormant account is a second chance at anything you missed; a deleted one is not, and you will not know what you missed for several months. That is the actual argument for waiting, and it is not about the data being safe. It is about you not yet knowing what you forgot.