Data lifecycle and deletion changedclaude-tag/concepts/data-lifecycle
Nearest release: v2.1.290, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 5 Oct 2026 18:54 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 18:07 UTC.
Upstream edited
Recorded here
Lines+19added
Lines−19removed
From line
15
where the diff opens
First seen
25 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 15, old and new numbered
/
from line 15
1515| What | What it contains |
1616| :- | :- |
1717| Session transcripts | The record of one thread's, channel's, or direct message's work. A transcript holds the messages Claude was shown in the conversation and who sent them, files attached there, earlier versions of messages that were later edited, what Claude retrieved while working (Slack search results, messages it read in channels it's in, and data from connected tools), and everything Claude said and did |
18| Memory | The notes Claude saves for each channel, the workspace notes it saves from public channels, and separate notes for each direct-message conversation. See [What Claude Tag remembers](/docs/claude-tag/users/memory) |
18| Memory | The notes Claude saves for each channel, the workspace notes it saves from public channels, and separate notes for each direct-message conversation. See [What Claude Tag remembers](/docs/claude-tag/users/memory.md) |
1919| Routines | The scheduled and run-once tasks set up in channels or in direct messages, with their instructions and run history |
20| Scopes and their settings | Each workspace and channel [scope](/docs/claude-tag/concepts/glossary#scope), with its custom instructions, version setting, and the bundles and access applied there |
21| Bundles and connectors | The [bundles](/docs/claude-tag/concepts/glossary#bundle), connectors, and credentials set up for Claude Tag. They belong to your organization, not to a workspace |
20| Scopes and their settings | Each workspace and channel [scope](/docs/claude-tag/concepts/glossary.md#scope), with its custom instructions, version setting, and the bundles and access applied there |
21| Bundles and connectors | The [bundles](/docs/claude-tag/concepts/glossary.md#bundle), connectors, and credentials set up for Claude Tag. They belong to your organization, not to a workspace |
2222| Account links | The link between each member's Slack account and their Claude account, and the tokens that link uses |
23| Published artifacts | Pages a session published to claude.ai. See [Artifact visibility](/docs/claude-tag/concepts/security-and-data#artifact-visibility) |
23| Published artifacts | Pages a session published to claude.ai. See [Artifact visibility](/docs/claude-tag/concepts/security-and-data.md#artifact-visibility) |
2424| The app's installation credential | The token the Claude app uses to read and post in your Slack workspace |
2525
2626Deleting or editing a message or file in Slack doesn't remove it from a transcript that already includes it. Messages from other people in the conversation, including guests, become part of the transcript the same way and are held as your organization's data.
from line 31
3131
3232Sessions Claude stops using are archived, not deleted. That includes a thread's session after someone sends [`@Claude !restart`](/docs/claude-tag/users/commands#restart-a-stuck-or-wrong-context-session), a session that closed because the thread's first message was deleted, and the channel-level sessions Claude replaces after about an hour of quiet or about a day of age. An archived session keeps its full transcript until the channel's or workspace's data is deleted.
3333
34Letting a plan lapse, turning Claude Tag off, or no longer using it doesn't delete anything on its own. To delete a workspace's data when you stop using Claude Tag, [disconnect the workspace](/docs/claude-tag/admins/workspaces#revoke-a-pairing) or uninstall the app.
34Letting a plan lapse, turning Claude Tag off, or no longer using it doesn't delete anything on its own. To delete a workspace's data when you stop using Claude Tag, [disconnect the workspace](/docs/claude-tag/admins/workspaces.md#revoke-a-pairing) or uninstall the app.
3535
3636When an action below deletes data, deletion starts right away and completes in the background. Copies can remain in routine backups for a limited period after that before they age out.
3737
from line 47
4747| On Enterprise Grid, a Grid admin removes an org-wide installation of the app, from the whole grid or from one of its workspaces | Nothing is deleted. To delete the data, an Owner disconnects the grid, or a workspace that has its own pairing, in your Claude admin settings | No |
4848| A channel is deleted in Slack | Deleted: that channel's sessions and transcripts, including earlier sessions Claude had archived there, its channel memory, and its scope with the routines and artifacts that belong to it. Workspace notes Claude saved from a public channel aren't tied to the channel and stay until you delete them or disconnect the workspace, as does anything created under the workspace scope rather than the channel's own | Not applicable |
4949| A channel is archived in Slack | Nothing is deleted. Unarchiving the channel picks its memory, routines, and sessions back up | Not while the channel is archived |
50| A public channel is made private | Nothing is deleted. Claude archives the channel's earlier sessions. The channel's notes stay with the channel, and workspace notes Claude saved from it while it was public stay shared; see [Channel and workspace memory](/docs/claude-tag/users/memory#channel-and-workspace-memory) | Yes |
50| A public channel is made private | Nothing is deleted. Claude archives the channel's earlier sessions. The channel's notes stay with the channel, and workspace notes Claude saved from it while it was public stay shared; see [Channel and workspace memory](/docs/claude-tag/users/memory.md#channel-and-workspace-memory) | Yes |
5151| Someone removes Claude from a channel with `/remove @Claude` | Nothing is deleted. The channel's memory, routines, and past sessions stay on record, and re-adding Claude picks them back up. The channel's routines keep firing while Claude is out of the channel but can't post there | No |
5252| Someone edits a message Claude read | Claude receives the edit as a note, and the transcript keeps both the earlier and the edited text | Yes |
5353| Someone deletes a reply in a thread | Nothing is removed from the transcript, and Claude isn't notified | Yes |
from line 59
5959
6060| Action | Claude-side data | Does Claude keep responding? |
6161| :- | :- | :- |
62| An Owner [disconnects a workspace](/docs/claude-tag/admins/workspaces#revoke-a-pairing) | Deleted: the workspace's sessions and transcripts, including members' direct-message conversations there; its channel, workspace, and direct-message memory; the routines set up in its channels and the artifacts published from them; its scopes with their instructions and bundle bindings; and members' account links. The Slack app and its installation credential stay so a workspace admin can pair again, and bundles, routines members set up in one-to-one direct messages, and what Claude posted in Slack stay too. Pairing the same workspace to the same organization again within a few minutes can cancel the deletion | Stops in channels immediately. One-to-one direct messages keep working on each member's own Claude account until the deletion removes that member's account link |
62| An Owner [disconnects a workspace](/docs/claude-tag/admins/workspaces.md#revoke-a-pairing) | Deleted: the workspace's sessions and transcripts, including members' direct-message conversations there; its channel, workspace, and direct-message memory; the routines set up in its channels and the artifacts published from them; its scopes with their instructions and bundle bindings; and members' account links. The Slack app and its installation credential stay so a workspace admin can pair again, and bundles, routines members set up in one-to-one direct messages, and what Claude posted in Slack stay too. Pairing the same workspace to the same organization again within a few minutes can cancel the deletion | Stops in channels immediately. One-to-one direct messages keep working on each member's own Claude account until the deletion removes that member's account link |
6363| An Owner disconnects an Enterprise Grid | The same as disconnecting a workspace, for every workspace in the grid that doesn't have its own workspace pairing, plus the app's installation credentials for those workspaces. Workspaces you paired individually stay connected and keep their data until you disconnect them | Stops in the affected workspaces |
6464| An Owner removes a channel's scope with **Remove this scope** in the **⋯** menu of the channel's page | Deleted: the channel's sessions and transcripts recorded up to that moment, including threads still in progress, its memory, its routines, and the artifacts published from it. The Slack channel itself is unchanged | Yes, where the channel's workspace has its own setting on, or has no setting of its own and the **Slack** page's setting is on. Claude stays in the channel and, when tagged again, starts fresh under the access it inherits from the workspace. To stop it as well, first run `/remove @Claude` |
65| An Owner or a Claude Tag admin turns off a workspace's **Enable Claude Tag in this workspace** switch, a channel's **Enable Claude Tag in this channel** switch, or **Respond in all channels** (or **Respond in channels**) on the **Slack** page, or an Owner turns off **Enable Claude Tag in Slack** for the organization or [direct messages](/docs/claude-tag/admins/restrict-access#allow-or-disable-direct-messages) | Nothing is deleted. Turning the setting back on resumes with the existing memory, routines, and sessions | No, where the setting is off |
66| An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access#delegate-claude-tag-administration) removes a place from a bundle's **Where it applies** list, or deletes a bundle | Removing a place removes the binding, and deleting a bundle deletes its credentials everywhere it applied. Memory, routines, and transcripts are unaffected | Yes, without that access |
65| An Owner or a Claude Tag admin turns off a workspace's **Enable Claude Tag in this workspace** switch, a channel's **Enable Claude Tag in this channel** switch, or **Respond in all channels** (or **Respond in channels**) on the **Slack** page, or an Owner turns off **Enable Claude Tag in Slack** for the organization or [direct messages](/docs/claude-tag/admins/restrict-access.md#allow-or-disable-direct-messages) | Nothing is deleted. Turning the setting back on resumes with the existing memory, routines, and sessions | No, where the setting is off |
66| An Owner or a [Claude Tag admin](/docs/claude-tag/admins/restrict-access.md#delegate-claude-tag-administration) removes a place from a bundle's **Where it applies** list, or deletes a bundle | Removing a place removes the binding, and deleting a bundle deletes its credentials everywhere it applied. Memory, routines, and transcripts are unaffected | Yes, without that access |
6767| An Owner deletes entries from a scope's memory files, or someone in the channel tells Claude to forget an entry | The entry is removed from what Claude reads and from the memory files view. Earlier versions of the scope's memory remain stored with the scope until the scope's data is deleted | Yes |
68| An Owner deletes a channel's routine from the [**Scheduled work** tab](/docs/claude-tag/admins/audit#what-the-activity-page-lists), or someone asks Claude to delete a routine in the channel or direct message where it was set up | The routine and the sessions it ran are deleted. Pausing a routine there, or disabling it from the channel, keeps it on record | Yes |
68| An Owner deletes a channel's routine from the [**Scheduled work** tab](/docs/claude-tag/admins/audit.md#what-the-activity-page-lists), or someone asks Claude to delete a routine in the channel or direct message where it was set up | The routine and the sessions it ran are deleted. Pausing a routine there, or disabling it from the channel, keeps it on record | Yes |
6969| A member selects **Disconnect** in the Claude app's **Home** tab in Slack | Removes the link between their Slack and Claude accounts and revokes the tokens Claude Tag held for them. Their earlier direct-message conversations and notes, and channel work they started, aren't deleted; those go with the workspace | In channels, yes. One-to-one direct messages and personal connectors stop working for that member until they reconnect |
7070| A member is removed from your Claude organization | Nothing is deleted. They lose access within minutes, and routines they set up in one-to-one direct messages are turned off. Their account link, direct-message conversations, and notes stay until the workspace is disconnected | Not to that member |
7171| A member deletes their own Claude account | On Team and Enterprise plans, deleting an individual account doesn't remove the Claude Tag data your organization holds about that member, including their direct-message conversations and notes and their account link. A member who wants the link and its tokens removed can select **Disconnect** in Slack before deleting their account | Not to that member |
7272| Your Claude organization is deleted | All Claude Tag data for every paired workspace is deleted as part of the organization deletion. The Slack app isn't uninstalled by this, and its installation credential remains until the app is uninstalled, so uninstall it from each workspace in Slack as well | No |
73| Your organization adopts Zero Data Retention or another restricted compliance configuration after pairing | Nothing already stored is deleted. Disconnect each workspace to delete its data | No. Claude stops responding in Slack and new pairings are refused; see [Restricted compliance settings block Claude Tag](/docs/claude-tag/admins/troubleshooting#restricted-compliance-settings-block-claude-tag) |
73| Your organization adopts Zero Data Retention or another restricted compliance configuration after pairing | Nothing already stored is deleted. Disconnect each workspace to delete its data | No. Claude stops responding in Slack and new pairings are refused; see [Restricted compliance settings block Claude Tag](/docs/claude-tag/admins/troubleshooting.md#restricted-compliance-settings-block-claude-tag) |
7474
7575## Direct messages
7676
from line 84
8484
8585The controls that delete Claude Tag data, from largest to smallest:
8686
87* **Disconnect a workspace or an Enterprise Grid** under **Connected workspaces** on the **Slack** page, which you open with the **Slack** row on the **Channels** tab under **Claude's access** at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), or uninstall the app from the workspace in Slack. Deletes all of that workspace's data. See [Revoke a pairing](/docs/claude-tag/admins/workspaces#revoke-a-pairing)
87* **Disconnect a workspace or an Enterprise Grid** under **Connected workspaces** on the **Slack** page, which you open with the **Slack** row on the **Channels** tab under **Claude's access** at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), or uninstall the app from the workspace in Slack. Deletes all of that workspace's data. See [Revoke a pairing](/docs/claude-tag/admins/workspaces.md#revoke-a-pairing)
8888* **Remove a channel's scope**: open the channel from the **Channels** tab under **Claude's access**, then select **Remove this scope** in the page's **⋯** menu, if the menu lists it. Deletes that channel's data recorded so far
89* **Delete memory files**: open the workspace's page from the **Channels** tab (or a channel's page, when that channel has memory of its own), choose **View memory files** from its **⋯** menu if the menu lists it, pick a file, then select **Delete**. Deleting requires the Owner role. You can also tell Claude in the channel to forget an entry. See [Check and correct what Claude Tag remembers](/docs/claude-tag/users/memory#check-and-correct-what-claude-tag-remembers)
90* **Delete a routine**: an Owner deletes a channel's routine from the **Scheduled work** tab. You can also ask Claude to delete a routine in the channel or direct message where it was set up. See [Audit Claude Tag activity](/docs/claude-tag/admins/audit)
89* **Delete memory files**: open the workspace's page from the **Channels** tab (or a channel's page, when that channel has memory of its own), choose **View memory files** from its **⋯** menu if the menu lists it, pick a file, then select **Delete**. Deleting requires the Owner role. You can also tell Claude in the channel to forget an entry. See [Check and correct what Claude Tag remembers](/docs/claude-tag/users/memory.md#check-and-correct-what-claude-tag-remembers)
90* **Delete a routine**: an Owner deletes a channel's routine from the **Scheduled work** tab. You can also ask Claude to delete a routine in the channel or direct message where it was set up. See [Audit Claude Tag activity](/docs/claude-tag/admins/audit.md)
9191
9292There is no control in Slack or in your Claude admin settings that deletes a single thread's transcript on its own. During the beta, Claude Tag session transcripts and memory aren't included in your organization's data exports, and the Compliance API doesn't list or delete Claude Tag sessions. For a deletion request these controls don't cover, contact your account team or [[email protected]](mailto:[email protected]).
9393
from line 97
9797
9898## Related resources
9999
100* [Security and data handling](/docs/claude-tag/concepts/security-and-data): sandbox isolation, credential storage, and artifact visibility
101* [Manage workspaces and versions](/docs/claude-tag/admins/workspaces#revoke-a-pairing): the Disconnect control and what it deletes
102* [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access#quiet-or-remove-claude-tag): the ways to quiet or remove Claude, and which keep data
103* [What Claude Tag remembers](/docs/claude-tag/users/memory): reading, correcting, and deleting memory
104* [Audit Claude Tag activity](/docs/claude-tag/admins/audit): scheduled work, memory files, and network events
100* [Security and data handling](/docs/claude-tag/concepts/security-and-data.md): sandbox isolation, credential storage, and artifact visibility
101* [Manage workspaces and versions](/docs/claude-tag/admins/workspaces.md#revoke-a-pairing): the Disconnect control and what it deletes
102* [Restrict where Claude Tag operates](/docs/claude-tag/admins/restrict-access.md#quiet-or-remove-claude-tag): the ways to quiet or remove Claude, and which keep data
103* [What Claude Tag remembers](/docs/claude-tag/users/memory.md): reading, correcting, and deleting memory
104* [Audit Claude Tag activity](/docs/claude-tag/admins/audit.md): scheduled work, memory files, and network events
105105
No line in this hunk matches that.