Data lifecycle and deletion
Cloud Tag keeps data in two places: its own database and file store, and your organization's Anthropic account.
What Cloud Tag stores
| Data | Where | Kept until |
|---|---|---|
| Every message the agent's mailbox receives from its groups, and every email it sends | Cloud Tag's database | The group or organization is deleted |
| Imported past mail | Cloud Tag's database | The group or organization is deleted |
| Group files: attachments, uploads, and files the agent made | Cloud Tag's private file store | An admin deletes the file on the Files page, or the group or organization is deleted |
| Settings, roles, routines, approvals (including each request's arguments, up to 64 KB, with secret-looking values hidden), turn history and each group's activity log | Cloud Tag's database | The group or organization is deleted |
| The organization's API key and each mailbox's Google sign-in | Cloud Tag's database, encrypted | Replaced, removed, unlinked, or the organization is deleted |
| Each agent's GitHub sign-in | Cloud Tag's database, encrypted | Replaced, disconnected, or the organization is deleted. Unlinking a mailbox keeps its GitHub sign-in; disconnect that separately |
| GitHub repository tokens | Cloud Tag's database, encrypted | The repository is removed, its group is deleted (for group repositories), or the organization is deleted |
| Members' personal connectors and their sign-ins | Cloud Tag's database, encrypted | The member removes them on Your connectors. They belong to the person, not the organization |
| A record of each personal connector call: who it acted for, the connector and tool, a keyed digest of its arguments, and how it ended. Its result is kept encrypted only until the agent's session has it, and a call waiting for its owner's approval keeps its arguments encrypted until they answer | Cloud Tag's database | The result as soon as the session has it, or the turn ends; the record with its group or organization |
Confirmed DMs use the same storage and deletion rules as groups, with access restricted to their sender. Unverified Workspace DMs waiting for confirmation are stored as encrypted raw mail outside the agent's history. Confirming or declining clears that quarantined copy; the cron clears copies after their 24-hour confirmation expires and deletes confirmation metadata after a week. Deleting the organization also deletes its quarantined DMs.
Other data is not deleted on a timer.
What lives in your Anthropic account
| Data | Kept until |
|---|---|
| Each group's agent | Replaced when the group's settings change (the old one is archived), or archived when the group or organization is deleted |
| Each thread's session, with its events | You delete it in your Anthropic account. Cloud Tag never deletes sessions |
| Each group's memory store | Notes are deleted when an admin deletes them; the store is archived when the group or organization is deleted |
| Each agent's shared notes | Notes are deleted when an Owner or Admin deletes them. Not archived when the organization is deleted |
| Copies of group files the agent opened, and uploaded custom skills | Stay in your Anthropic account. Cloud Tag doesn't delete them |
| Vaults holding connector credentials and secrets (per group, per bundle, and the organization's) | A credential is deleted when you remove its connector or secret; group vaults are archived when the group is deleted; all vaults are archived when the organization is deleted |
| Environments (one per network policy) | Reused across groups, and never deleted |
Anthropic's own retention policies apply to everything in your Anthropic account.
What each action does
| Action | Effect |
|---|---|
| Delete a file (Files page) | Removes it from Cloud Tag, so the agent can't find it again. A copy it already opened stays in your Anthropic account's files |
| Remove a custom skill | Removes it from Cloud Tag and from the group's agent. The uploaded skill stays in your Anthropic account |
| Delete a memory note (Memory page, or the agent's shared notes) | Removes the note from the memory store |
| Remove a connector or secret | Deletes its credential from the vault, and re-makes the group's agent without it |
!restart a thread |
Drops the thread's session from Cloud Tag. The old session stays in your Anthropic account. The thread's messages stay in Cloud Tag |
| Remove the agent from a Google Group | It stops receiving the group's mail. Everything already stored stays |
| Unlink a mailbox | Discards its Gmail sign-in and stops reading it. Its groups keep their history. Linking it again picks up mail from while it was unlinked |
| Release an unlinked mailbox (Owners) | Lets another organization link the address. The old agent's groups, history and GitHub sign-in stay with your organization; the address is kept only in the activity log. It can't be undone: linking the mailbox here again makes a new agent |
| Delete a group (Overview, by a group admin or organization Owner/Admin, after typing its email) | Deletes its history, settings, roles, routines, approvals, queued replies and group activity from Cloud Tag. Attempts to remove its stored files and archive its Anthropic agent, vault and memory store; cleanup failures are reported. Shared resources, Anthropic sessions, uploaded copies, mailbox mail and the Google Group stay. Work already running and mail already being sent may finish. Submitted feedback and a deletion record, including incurred spend for the current month, stay in Cloud Tag; deleting a group does not reset the organization's monthly spend. Remove the agent in Google Groups first, or later mail can create a fresh pending group requiring approval |
| Delete the organization (by the platform operator, after typing its name) | Deletes its groups, conversations, messages, files and settings from Cloud Tag, and archives its groups' agents, vaults and memory stores in its Anthropic account. Sessions, shared notes, file copies, skills and environments stay in the Anthropic account. People's sign-in records and organization-level activity entries stay in Cloud Tag |
Google Drive
Cloud Tag doesn't copy Drive files. The agent reads the current version when it opens one, and a copy of what it opened goes into your Anthropic account's files for that session, like any other file it opens.
Mail outside Cloud Tag
Cloud Tag reads the agent's mailbox; it doesn't delete mail from it. Copies stay in the mailbox and in the Google Group's own archive under your Google Workspace or Google Groups settings.