Data and retention

Messages, originals, attachments, saved drafts and generated context are kept while the workspace exists. Archiving changes where a message appears; it does not erase it.

Workspace deletion removes its application data after mail routes and custom domains have been removed. Until cleanup is confirmed, deletion stays pending and receiving is paused. Shared workspaces cannot be deleted through this page.

Exports include only data you can access. The current downloads are technical data files, not a ready-to-open mail archive. Message lists alone do not include the full email or attachment bytes. Save and check every list and linked content file before deleting the workspace.

Your sign-in profile is separate from workspace data. Workspace deletion does not delete that profile or data in other workspaces. The separate profile deletion flow verifies your current password, removes eligible workspaces and then removes your sign-in profile, sessions and recovery proofs. Shared workspace membership must be resolved first.

Before erasing local data, deletion saves an off-server record containing a workspace identifier or a hash of the sign-in profile identifier. It contains no message contents. If this record cannot be saved, deletion stays pending and local data is preserved. Confirmed deletion has no cancellation step: a restore may remove data for a recorded deletion even if local cleanup was still pending. Operators must apply these records before reopening a restored service.

The mail transport keeps separate message and delivery records. Workspace deletion does not erase those records or copies already delivered to another mailbox.

Backups can contain deleted data. The configured backup policy keeps seven daily, four weekly and twelve monthly snapshots; retained snapshots are removed by scheduled maintenance. This is a snapshot selection policy, not a guaranteed deadline for erasing a particular message. Restored data must be checked against deletion records before service resumes.