Where the app stores data
The app writes to two locations on each member’s computer: Configuration: config.toml in the app’s default data folder (~/.claude-science/config.toml on macOS and Linux, %USERPROFILE%\.claude-science\config.toml on Windows) holds all app settings. Every key is optional; the app starts with no file present. This is the file to deploy through device management.Data: the app’s data directory holds conversations, generated artifacts, delegation configurations, and workspace files in a per-organization subfolder (orgs/
<organization-id>/), stored as a local database plus files.
Authentication tokens and the shared package environment live under the default data folder (~/.claude-science/, or %USERPROFILE%\.claude-science\ on Windows) regardless of the data directory, so endpoint backup or wipe policies that target the data directory don’t affect sign-in state.
On Windows, the program itself installs per user to %LOCALAPPDATA%\Programs\ClaudeScience and registers under the signed-in user’s Settings > Apps > Installed apps rather than machine-wide. The app also writes launch logs and state to %LOCALAPPDATA%\ClaudeScience and keeps a sandbox state folder under %LOCALAPPDATA%, and it unpacks components it runs, such as the app window engine and the sandbox launcher, under the data folder, so allow-listing by path needs both the program folder and the data folder. Uninstalling removes the program and sandbox state; claude-science uninstall --purge also removes the data and state folders.
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 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
To set configuration keys organization-wide, deploy the per-member config.toml (at the path given under Where the app stores data) through your MDM or endpoint tool. Claude Science doesn’t read its settings from a system-level managed-preferences file or registry policy keys, so there’s no native MDM configuration channel on any operating system. Deploying the per-member config.toml is the supported approach. The sandbox network allowlist and the package mirror can instead be set once for every member under Organization settings > Claude Science (see Organization settings). The keys most relevant to admins are:
The configuration file reference documents the network-related keys and their defaults, and Use Claude Science on a corporate network covers the proxy, TLS-inspection, and mirror settings.
Telemetry
The app sends product-usage telemetry (event counts and timings, not conversation content) to Anthropic. There’s no in-app setting for this; consent is covered by your organization’s acceptance of Anthropic’s commercial terms. When the app runs into an error, it also sends an error report to the error-reporting service Anthropic uses that identifies the error type and where it occurred in Claude Science’s own code. The report includes the app version, its runtime version, the operating system version, and the app’s most recent telemetry events. The app redacts each report on the member’s computer before sending it: error messages are removed, and code locations outside Claude Science’s own code are blanked. Reports contain no conversation content, research data, file contents, or file paths, and no usernames, account identifiers, or organization identifiers. To turn telemetry and error reports off on managed devices, use either of: Set disable_telemetry = true in config.toml (deployable through MDM).Set the DO_NOT_TRACK environment variable (for example to 1) on the device. Both are device-level settings. There’s no per-member or per-organization telemetry toggle in Organization settings.