Capture
One read of Claude Documentation
6 pages moved out of 218 read.
claude-science/admin-controls Changed · +16 / -16 lines
from line 2
> Members sign in to Claude Science with their Claude account, so your identity and billing controls apply automatically. -Members sign in to Claude Science with their Claude account, so your identity and billing controls apply automatically. Because the app stores conversations on each member's computer rather than on Anthropic's servers, most of the data-handling controls Anthropic provides don't reach that data today. The tables show, for each admin setting, whether it governs Claude Science in beta. Status values describe Claude Science specifically; other Claude products may differ. +Members sign in to Claude Science with their Claude account, so your identity and billing controls apply automatically. Because the app stores conversations on each member's computer, most of the data-handling controls Anthropic provides don't reach that data today. The tables show, for each admin setting, whether it governs Claude Science in beta. Status values describe Claude Science specifically; other Claude products may differ. Legend: Supported / Partial / Not available / Not applicable
from line 48
## Data and privacy -| Admin setting | Status in Claude Science beta | Note | -| ------------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| CMEK | Supported | Applies to the product's model traffic the same as Chat. | -| Data processing geography | Partial | Covers Anthropic-hosted processing, not remote compute you configure (code the member runs on their own SSH hosts or cloud accounts) or the member's computer (same as Claude Code). | -| HIPAA | Partial | HIPAA-ready organizations can enable the Claude Science beta, but usage isn't covered under the BAA. | -| Custom Data Retention | Not available | The auto-delete window doesn't cover local data or the usage logs Anthropic keeps for this product. | +| Admin setting | Status in Claude Science beta | Note | +| ------------------------- | ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| CMEK | Supported | Applies to the product's model traffic the same as Chat. Compliance API session transcripts are also encrypted under your key. | +| Data processing geography | Partial | Covers Anthropic-hosted processing, not remote compute you configure (code the member runs on their own SSH hosts or cloud accounts) or the member's computer (same as Claude Code). | +| HIPAA | Partial | Organizations with HIPAA compliance enabled can turn on the Claude Science beta, but usage isn't covered under the BAA. | +| Custom Data Retention | Partial | The auto-delete window doesn't cover data on members' computers or the model-call logs Anthropic keeps for this product. For Enterprise organizations with the Compliance API enabled, the window does apply to the session transcripts it returns. | ## Audit and compliance -| Admin setting | Status in Claude Science beta | Note | -| --------------- | ----------------------------- | ----------------------------------------------------------------------------------- | -| Audit log | Not available | No events recorded yet; on the roadmap. | -| Compliance API | Not available | Admins can't export or delete this product's data through the API. | -| Org data export | Not available | The export doesn't include data stored on members' computers (same as Claude Code). | +| Admin setting | Status in Claude Science beta | Note | +| --------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| Audit log | Not available | Claude Science doesn't write events to the audit log. For Enterprise organizations with the Compliance API enabled, changes to your Claude Science organization settings are recorded in its Activity Feed instead. | +| Compliance API | Partial | Enterprise plans only. The [Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api) returns read-only transcripts of members' Claude Science sessions (this coverage is in beta) and records changes to your Claude Science organization settings in its Activity Feed. Sessions in organizations with HIPAA compliance enabled aren't captured. See [Compliance API coverage](/docs/claude-science/how-claude-science-works-with-your-data#compliance-api-coverage). | +| Org data export | Not available | The export doesn't include data stored on members' computers (same as Claude Code). | ## Usage, models, and billing
from line 74
## Offboarding and local data -| Admin setting | Status in Claude Science beta | Note | -| ------------------------ | ----------------------------- | ------------------------------------------------------------------------------------------------------------------- | -| Offboarding (local data) | Not available | Removing a member doesn't wipe data already on their computer. | -| Local deletion signal | Not available | Deleting local data doesn't notify Anthropic to drop the matching server-side record early. This is on the roadmap. | +| Admin setting | Status in Claude Science beta | Note | +| ------------------------ | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Offboarding (local data) | Not available | Removing a member doesn't wipe data already on their computer. | +| Local deletion signal | Not available | Deleting local data doesn't notify Anthropic to drop the matching server-side model-call logs early; this is on the roadmap. Compliance API session transcripts, where captured, remain until their retention period ends. |
claude-science/how-claude-science-works-with-your-data Changed · +16 / -4 lines
## Compliance API coverage
from line 1
# How Claude Science works with your data -> Claude Science is a local-first application. +> What Anthropic receives from Claude Science, what stays on members' computers, and what Enterprise organizations can retrieve through the Compliance API. -Claude Science is a local-first application. Conversation history and artifacts are stored only on the member's device. Anthropic doesn't host a session store for the app and has nothing to browse, sync, or export. Prompts and completions sent to the model are processed by Anthropic and handled under Anthropic's standard retention and Trust & Safety policies. The following sections cover what Anthropic does receive. +Claude Science is a local-first application. Conversation history and artifacts are stored on the member's computer, and Anthropic doesn't sync them to the member's Claude account or to other devices. Anthropic does receive the prompts and responses the app exchanges with Claude, and handles them under its standard retention and Trust & Safety policies. For Enterprise organizations with the Compliance API enabled, Anthropic also retains those exchanges as session transcripts that the organization can retrieve; [Compliance API coverage](#compliance-api-coverage) explains what they contain. The following sections cover each of these, plus remote compute and connectors. ## What Anthropic receives -Each time the app calls Claude, the prompt and Claude's response travel to Anthropic's servers and are logged under Anthropic's standard retention policy for model traffic (see How long do you store my organization's data in the Privacy Center), the same policy that applies to other Claude products. If your organization has CMEK enabled, model-call logging follows the same CMEK handling as your other Claude products. Your organization's Custom Data Retention setting doesn't change that retention period; that setting governs conversation, project, and artifact data stored on Anthropic's servers, which this product doesn't create. The app also sends product-usage telemetry (event counts and timings, not conversation content), which can be turned off through device configuration. +Each time the app calls Claude, the prompt and Claude's response travel to Anthropic's servers and are logged under Anthropic's standard retention policy for model traffic (see How long do you store my organization's data in the Privacy Center), the same policy that applies to other Claude products. If your organization has CMEK enabled, model-call logging follows the same CMEK handling as your other Claude products. Your organization's Custom Data Retention setting doesn't change how long these model-call logs are kept. It does apply to the session transcripts that Anthropic keeps for Enterprise organizations with the Compliance API enabled, described in [Compliance API coverage](#compliance-api-coverage). The app also sends product-usage telemetry (event counts and timings, not conversation content), which can be turned off through device configuration. +## Compliance API coverage + +If your organization is on an Enterprise plan and has the [Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api) enabled, your compliance team can retrieve transcripts of members' Claude Science sessions through it. Coverage of Claude Science sessions is in beta. + +Anthropic captures a session only while the Compliance API is enabled for your organization and the member is signed in with their Claude Enterprise account. Transcripts aren't available for sessions that ran before capture began for your organization, although such sessions can still appear in the session list with their content marked unavailable. Anthropic records each session on its servers as the app's requests reach the Claude API, without installing anything extra on the member's computer or capturing anything beyond the requests the app already sends to Claude. Sessions in organizations with [HIPAA compliance enabled](/docs/claude-science/enable-claude-science#hipaa-organizations) aren't captured, and [Retrieve session transcripts](https://platform.claude.com/docs/en/manage-claude/compliance-sessions) lists the other cases the Compliance API doesn't return. + +A transcript is reconstructed from what the app exchanged with Claude during the session: the member's prompts, Claude's responses, tool calls (including code and file content Claude wrote through them), and the text portions of tool results, including text from files that Claude read, subject to the size limits the Compliance API applies. Claude's extended thinking and the app's system prompt aren't included (a placeholder marks where the system prompt was), tool definitions and connector (MCP server) configuration are omitted, and images, PDFs, and other non-text content appear as placeholders. Content that never reached the Claude API, such as a local file the session never sent, isn't in the transcript. + +Anthropic keeps these transcripts for six years from capture by default. If your organization has set a Custom Data Retention period (in claude.ai under Organization settings > Data and privacy), that period applies to the transcripts instead, and when more than one retention period is set, the shortest applies. If your organization uses CMEK, the transcripts are encrypted under your key. The session endpoints are read-only, so transcripts can't be deleted through the API before they expire; see [Retention and deletion](https://platform.claude.com/docs/en/manage-claude/compliance-sessions#retention-and-deletion) for the current terms. + +The Compliance API's [Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed) also records changes to your Claude Science organization settings, such as turning the product on or off. The [Compliance API reference](https://platform.claude.com/docs/en/api/compliance/activities/list) describes these events. + ## Remote compute When a member chooses to connect the app to remote compute (an owned server or cloud account they control), the app sends code and data directly to that destination. That traffic doesn't pass through Anthropic. Admins can't yet restrict whether members can connect to remote compute. For setup details, see [Remote compute clusters](/docs/claude-science/remote-compute-clusters) and [Compute providers](/docs/claude-science/compute-providers) in the user documentation.
from line 30
## What this means for you as an admin -Because conversations and artifacts live on members' computers, the Anthropic-side data controls (Custom Data Retention, Org Data Export, and the Compliance API) don't reach them. Device management is the control you have for that data: your device management software (such as your MDM or EDR) governs the app's local folder the same way it governs any other local application data. Identity controls (SSO, SCIM, roles) apply because sign-in goes through claude.ai; see [Admin controls](/docs/claude-science/admin-controls) for what IP allowlisting and session duration cover. +Because conversations and artifacts live on members' computers, Custom Data Retention and Org Data Export don't reach that local data. For Enterprise organizations with the Compliance API enabled, Anthropic also keeps session transcripts captured from the app's model calls, which include file text the app sent to Claude, and a record of settings changes (see [Compliance API coverage](#compliance-api-coverage)). Device management is the control you have for local data: your device management software (such as your MDM or EDR) governs the app's local folder the same way it governs any other local application data. Identity controls (SSO, SCIM, roles) apply because sign-in goes through claude.ai. See [Admin controls](/docs/claude-science/admin-controls) for what IP allowlisting and session duration cover.
claude-science/manage-on-devices Changed · +3 / -3 lines
from line 1
# Manage Claude Science on devices -> Claude Science is a desktop application that stores all member content locally. +> Claude Science is a desktop application that stores member content locally. -Claude Science is a desktop application that stores all member content locally. This page covers what IT and endpoint teams need to know: where the app writes data, how to deploy configuration with device management, what telemetry is sent, and what members see when Anthropic requires an update. +Claude Science is a desktop application that stores member content locally. This page covers what IT and endpoint teams need to know: where the app writes data, how to deploy configuration with device management, what telemetry is sent, and what members see when Anthropic requires an update. ## Where the app stores data
from line 13
Authentication tokens and the shared package environment live under \~/.claude-science/ regardless of the data directory, so endpoint backup or wipe policies that target the data directory don't affect sign-in state. -Your endpoint tooling governs these folders the same way it governs any other local application data. There's no Anthropic-hosted copy, so Custom Data Retention, Org Data Export, and the Compliance API don't reach them. +Your endpoint tooling governs these folders the same way it governs any other local application data. Anthropic doesn't host a copy of these folders, so Custom Data Retention and Org Data Export don't reach them. [How Claude Science works with your data](/docs/claude-science/how-claude-science-works-with-your-data) covers what Anthropic does receive from the app, including the session transcripts available to Enterprise organizations with the Compliance API enabled. ## Deploy configuration with device management
claude-science/whats-not-available-yet Changed · +3 / -4 lines
from line 6
## Audit and compliance -Audit log: no Claude Science events are written to the organization audit log yet. This is on the roadmap.\ -Compliance API: admins can't export or delete Claude Science data through the Compliance API. Because conversations live on members' computers, there's no Anthropic-side data for the API to reach; see [Manage on devices](/docs/claude-science/manage-on-devices) for endpoint-level options.\ +Audit log: Claude Science doesn't write events to the organization audit log. For Enterprise organizations with the Compliance API enabled, settings changes and read-only session transcripts are available through the [Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api) instead (Claude Science session coverage is in beta); see [Compliance API coverage](/docs/claude-science/how-claude-science-works-with-your-data#compliance-api-coverage).\ Org data export: the organization export doesn't include data stored on members' computers. ## Data retention -Custom Data Retention: your auto-delete window applies to conversations, projects, and artifacts stored on Anthropic's servers. Claude Science doesn't store that data on Anthropic's servers, so the setting has nothing to act on.\ -Local deletion signal: when a member deletes local Claude Science data, Anthropic isn't notified to drop the matching server-side model-traffic log early. The log still expires under Anthropic's standard retention. +Custom Data Retention: your auto-delete window applies to conversations, projects, and artifacts stored on Anthropic's servers. Claude Science keeps conversations and artifacts on members' computers, where the window doesn't reach. For Enterprise organizations with the Compliance API enabled, the window does apply to the session transcripts it returns.\ +Local deletion signal: when a member deletes local Claude Science data, Anthropic isn't notified, so the matching server-side records (the model-call log and, for Enterprise organizations with the Compliance API enabled, the session transcript) aren't dropped early. Each expires under its own retention period. ## Connector and domain allowlists
claude-science/multiple-computers Changed · +2 / -2 lines
from line 2
> What to expect when you sign in on another computer. -Claude Science runs on your own computer by design, and your projects, artifacts, and conversation history live there with it, under your control rather than in your Claude account or on Anthropic's servers. Each computer you install it on keeps its own projects, so a new or different computer starts fresh when you sign in, and your earlier work stays on the first computer. +Claude Science runs on your own computer by design, and your projects, artifacts, and conversation history live there with it, under your control rather than in your Claude account. Each computer you install it on keeps its own projects, so a new or different computer starts fresh when you sign in, and your earlier work stays on the first computer. ## Your work stays on your computer -Anthropic doesn't host your projects, artifacts, or conversation history, so there's no cloud copy of them to browse or sync. Claude reads and writes your files in place, in the folders you grant, and your work sits alongside them on your computer, where your own backup tools can cover it like any other application data. Your prompts, Claude's responses, and the file content Claude reads to answer them still go to Anthropic as part of each conversation and are handled under Anthropic's standard retention policy, as [Core concepts](/docs/claude-science/core-concepts#files-stay-on-your-computer) explains. +Anthropic doesn't sync your projects, artifacts, or conversation history to your Claude account, so there's no cloud copy for you to browse or sync from another computer. Claude reads and writes your files in place, in the folders you grant, and your work sits alongside them on your computer, where your own backup tools can cover it like any other application data. Your prompts, Claude's responses, and the file content Claude reads to answer them still go to Anthropic as part of each conversation, and Anthropic retains them as [How Claude Science works with your data](/docs/claude-science/how-claude-science-works-with-your-data) describes. You can install Claude Science on more than one computer and sign in to each with the same Claude account. Your account carries your plan and usage limits to every computer. Skills from your organization, along with any you published from the app, also reappear when you sign in on another computer (to the same organization, if your account belongs to more than one). Memory, settings, and the connectors you added in the app stay with each computer.
claude-science/core-concepts Changed · +1 / -1 lines
from line 10
## Files stay on your computer -Claude reads and writes files in place, in the folders you grant. Anthropic doesn't host or store your files; file content that Claude reads to answer a prompt is sent to Anthropic's API as part of that conversation and handled under Anthropic's standard retention policy. If you sign in to Claude Science on a different computer, your files, artifacts, and conversation history don't follow you there. See [Use Claude Science on more than one computer](/docs/claude-science/multiple-computers) for what your account does carry between computers. +Claude reads and writes files in place, in the folders you grant. Anthropic doesn't host or store your files; file content that Claude reads to answer a prompt is sent to Anthropic as part of the conversation, and Anthropic retains it as [How Claude Science works with your data](/docs/claude-science/how-claude-science-works-with-your-data) describes. If you sign in to Claude Science on a different computer, your files, artifacts, and conversation history don't follow you there. See [Use Claude Science on more than one computer](/docs/claude-science/multiple-computers) for what your account does carry between computers. The one exception to working in place is **Attach files** in the composer: attached files are copied into the application's local data folder so they stay with the conversation.