AI activity retention

Your team works in Claude.

If regulators ask for those business records, can you provide them?

Comma captures Claude Enterprise activity through Anthropic's own Compliance API — the official integration Anthropic built for regulated customers.

SEC Rule 17a-4, FINRA Rule 4511, and the Investment Advisers Act recordkeeping requirements are channel-agnostic. The content of the activity determines the obligation, not the interface — and whether a Claude session is a business record follows the same analysis regulators have already applied to off-channel messaging.

This is the same logic regulators applied during the 2021–2024 off-channel sweep. The activity was happening in WhatsApp, Signal, and iMessage, yet firms had not captured it. The penalties followed. AI assistants are the next front-office channel, and the recordkeeping framework that would reach them is already in place. If the firm cannot produce the record on request, the gap is the firm’s.

Comma captures the AI execution record: the prompts, the responses, the files, and the surrounding context — not just a screenshot of the chat.

What Comma captures from Claude Enterprise

  • The organization Activity Feed: admin events and resource events
  • Users, roles, and groups across linked organizations
  • For claude.ai organizations, the underlying chats, files, and projects
  • Audit-log exports cover a rolling 180-day window; chat inputs and outputs are exportable by a Primary Owner

All of it routed through Anthropic’s Compliance API and landed in the same tamper-proof archive as your other channels.

Anthropic’s Activity Feed Goes Beyond Chat Retention

The Activity Feed captures an organizational layer that chat logs alone don’t reach: admin events (API configuration changes, user provisioning), resource events (project creation, file uploads), and user and role data across all linked organizations.

For compliance, legal, and risk teams, this organizational record is valuable for investigations and regulatory review — it shows who had access, when that access changed, and what actions were taken across the enterprise, not just what was said in a given session.

Why the architecture matters

For your compliance team

  • More than conversations

    Anthropic's Compliance API surfaces the organization's Activity Feed alongside chat content: admin events, resource events, and user and role data. That's a broader governance record than most compliance tools expect from an AI integration.

  • One archive, one review queue

    Claude activity lands alongside your other 35+ channels. One supervision workflow covers everything, so compliance teams do not need a separate tool for AI.

For your IT team

  • Enabled by a Primary Owner

    One person enables the Compliance API through organization settings. No per-user deployment, no device management, no browser configuration. It runs at the organization level from that point forward.

  • No client modification

    Anthropic's Compliance API connects server-to-server. Nothing is installed on employee devices or browsers, and the Claude client is not modified in any way.

For your employees

  • Claude works exactly as it does today

    Capture happens through the API, not on the device or in the interface. Employees continue using Claude without any change to their experience.

  • No manual exports

    Users do not need to save conversations, export sessions, or follow any retention procedure. The record is created automatically through the API.

FAQ about Claude compliance archiving

Do we need Claude Enterprise for Comma to capture activity?
Yes. Claude Enterprise is where Anthropic exposes the Compliance API — the official, admin-enabled path Comma integrates with. The Team tier gets audit logs but not the full Compliance API. On consumer plans the API does not exist, so there is no provider-supported way to capture the activity.
What exactly does Comma capture from Claude?
The organization Activity Feed (admin and resource events), users, roles, and groups across linked organizations, and, for claude.ai organizations, the underlying chats, files, and projects. Audit-log exports cover a rolling 180-day window; chat inputs and outputs are exportable by a Primary Owner. All of it lands in the same archive as your other channels.
What's in the Activity Feed that isn't in the chat log?
The chat log captures conversation content — prompts, responses, files attached to sessions, and projects. The Activity Feed captures an organizational layer on top of that: admin events (API configuration changes, user provisioning), resource events (project creation, file uploads), and user and role data across all linked organizations. For an examiner or internal investigation, the Activity Feed is often more revealing than the chat log itself — it shows who had access, when that access changed, and what actions were taken across the enterprise, not just what was said in a given session.
What about employees using free or Team-tier Claude?
Activity below Enterprise cannot be captured through the Compliance API. The Team tier gets audit logs but not the full compliance surface. Treat unmonitored Claude usage the way you treat an unmonitored messaging app: it is an off-channel risk. The practical fix is a written policy that standardizes regulated AI use on Claude Enterprise.
Does Claude activity go into the same archive as our other channels?
Yes. Claude activity is captured and archived with appropriate WORM-storage as the rest of your 35+ channels. Comma Compliance provides your compliance team one archive with a single supervision queue. No need to learn an entirely new tool just for AI.
What happens if an examiner requests data?
Comma retains your team's Claude interactions using Anthropic's own Compliance API, captured in structured form with timestamps and metadata intact. When an examiner asks for a date range or an individual, the records are searchable and exportable on demand.

Claude is already writing your emails.

Capture it the same way you capture everything else — through Anthropic's official Compliance API, into one exam-ready archive.

Go deeper on AI activity retention

Other channels we support