Tagged “accounts”
-
The apps left on your devices
Desktop and mobile apps hold signed-in sessions and unsynced drafts. Uninstalling before the account closes can take the only copy of something.
-
Cancelling without losing the archive
Access to your history usually depends on an active account. That single fact decides the order of every step in closing one, and the order is unforgiving.
-
What a team member can take with them
In a workspace your employer pays for, the conversations are usually not yours to take. Find out what your export rights are before the seat disappears.
-
Switching a team workspace
A shared workspace turns a personal migration into a coordination problem. The export is an admin task and the deadline is everyone's.
-
What does not transfer
The export covers what was said. Everything that made the assistant feel tuned to you lives outside it, and has to be rebuilt by hand on the other side.
-
What happens to your data after the account closes
Cancelling, deactivating and deleting do different things to your data. Only one destroys it, and none are instant in the way people assume.
-
Revoking the integrations you forgot
Authorisations the assistant holds against your other accounts do not expire when you cancel. Revoking happens in those services, not in it.
-
Replacing shared links before they break
Shared conversation links live on the old account. When it closes they stop resolving, in documents belonging to people who will not know why.
-
Copying memory out before you clear it
What the assistant remembers about you accumulated over months and cannot be regenerated. Read it, copy it, sort it — then clear.
-
Rebuilding projects and folders on the other side
The organisational layer has no export format anywhere. Rebuild only the containers you used, from your own list rather than by copying.
-
Storing the archive so it survives
The archive has to outlive the account, the laptop, and your memory of what is in it. Three copies, plain formats, and one note explaining the folder.