access-transparency changedmanage-claude/access-transparency
Nearest release: v2.1.307, published an hour after this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+12added
Lines−12removed
From line
19
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits7to this page, all time
The whole hunk
from line 19, old and new numbered
/
from line 19
1919
2020Anthropic personnel access customer content only under defined conditions. Access Transparency is designed to make such access visible to you. The design rests on the following principles:
2121
22* **Human access happens only under a published reason code.**
22* **Human access occurs only under a published reason code.**
2323* **Human views of your covered content are recorded.** Anthropic's internal tooling that can reach your covered content is instrumented to emit an event on each view.
2424* **Events represent human access, not automated processing.** Anthropic's automated safety systems process your content in a secured pipeline with no interactive human access; that processing does not generate `anthropic_access` events. The one event automated processing can initiate is a `cmek_preserve` preservation record (see [CMEK content preservation](https://platform.claude.com/docs/en/manage-claude/access-transparency#cmek-content-preservation)).
2525* **Events arrive on your existing feed.** Activities are accessible through your [Compliance API Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed). Existing credentials, audit, export, and SIEM integrations for the Compliance API still apply.
from line 27
2727
2828## What Access Transparency covers
2929
30* **Covered content:** Access Transparency covers prompt and response content sent through the Claude Messages API or Claude Code sessions. Anthropic's [general ZDR documentation](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention) explains which APIs and features are covered by ZDR. The same APIs and features are covered by Access Transparency.
30* **Covered content:** Access Transparency covers prompt and response content sent through the Claude Messages API or Claude Code sessions. The [API and data retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention) page explains which APIs and features are covered by ZDR. The same APIs and features are covered by Access Transparency.
3131* **Manual views by Anthropic personnel:** Manual views of your covered content by Anthropic reviewers generate events.
3232
3333## What Access Transparency does not cover
from line 68
6868 "https://api.anthropic.com/v1/compliance/activities" \
6969 --data-urlencode "activity_types[]=anthropic_access" \
7070 --data-urlencode "limit=50" \
71 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
72 --header "anthropic-version: 2023-06-01"
71 -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
72 -H "anthropic-version: 2023-06-01"
7373```
7474
7575Pagination, date-range filtering (`created_at.gte` / `.lt`), and the response envelope (`has_more`, `first_id`, `last_id`) are shared with the rest of the Activity Feed. See [Query the Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed).
from line 126
126126 "https://api.anthropic.com/v1/compliance/activities" \
127127 --data-urlencode "activity_types[]=cmek_preserve" \
128128 --data-urlencode "limit=50" \
129 --header "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
130 --header "anthropic-version: 2023-06-01"
129 -H "x-api-key: $ANTHROPIC_COMPLIANCE_ACCESS_KEY" \
130 -H "anthropic-version: 2023-06-01"
131131```
132132
133133Example JSON message:
from line 182
182182
183183### Coverage timing
184184
185Access Transparency applies from the time it is enabled for your organization. Content already in your retention window at enablement might also generate events when accessed, but Anthropic does not guarantee coverage for content written before enablement. Treat your enablement date as the start of reliable coverage. There might be a delay of up to two hours between enabling Access Transparency and your content being covered.
185Access Transparency applies from the time it is enabled for your organization. Content already in your retention window at enablement might also generate events when accessed, but Anthropic does not guarantee coverage for content written before enablement. Treat your enablement date as the start of reliable coverage. There might be a delay of up to 2 hours between enabling Access Transparency and your content being covered.
186186
187187### Notification timing
188188
189`anthropic_access` and `cmek_preserve` events are delivered to your Compliance API feed within two business days of the access or preservation they record. This feed should not be treated as a real-time alerting channel, and the `accessed_at` timestamp reflects when the access occurred, which might be up to two business days before the activity becomes visible in your feed. The `created_at` field reflects the time Anthropic recorded the event, and the event usually becomes visible in your feed shortly after that time. These events do not follow the Activity Feed's usual 1-minute [indexing lag](https://platform.claude.com/docs/en/manage-claude/compliance-integration-patterns#window-polling): an event can become visible up to two business days after its `created_at`. If you poll the feed by `created_at` window, overlap consecutive windows by at least two business days for `anthropic_access` and `cmek_preserve` events so that a late-indexed event is not dropped.
189`anthropic_access` and `cmek_preserve` events are delivered to your Compliance API feed within 2 business days of the access or preservation they record. This feed should not be treated as a real-time alerting channel, and the `accessed_at` timestamp reflects when the access occurred, which might be up to 2 business days before the activity becomes visible in your feed. The `created_at` field reflects the time Anthropic recorded the event, and the event usually becomes visible in your feed shortly after that time. These events do not follow the Activity Feed's usual 1-minute [indexing lag](https://platform.claude.com/docs/en/manage-claude/compliance-integration-patterns#window-polling): an event can become visible up to 2 business days after its `created_at`. If you poll the feed by `created_at` window, overlap consecutive windows by at least 2 business days for `anthropic_access` and `cmek_preserve` events so that a late-indexed event is not dropped.
190190
191191### Automated processing does not generate access events
192192
from line 215
215215 Access Transparency is not available for platform deployments. Contact your Anthropic account representative to discuss your use case.
216216 </Accordion>
217217
218 <Accordion title="Will I see events for access that happened before we enrolled, or for our older data?">
218 <Accordion title="Will I see events for access that occurred before we enrolled, or for our older data?">
219219 Access Transparency is not guaranteed to be retroactive. It covers human access to content written to the Claude API on or after your enrollment date. You might see events for access to content that was written before enrollment.
220220 </Accordion>
221221
222222 <Accordion title="How soon after an access will I see the event?">
223 Within two business days of the access. Configure any SIEM alerting or scheduled exports with a matching lookback window rather than assuming real-time arrival.
223 Within 2 business days of the access. Configure any SIEM alerting or scheduled exports with a matching lookback window rather than assuming real-time arrival.
224224 </Accordion>
225225
226226 <Accordion title="How do I know which request an anthropic_access event refers to?">
from line 232
232232 </Accordion>
233233
234234 <Accordion title="How does Access Transparency relate to CMEK?">
235 They are independent. With CMEK, safety preservation outside your key emits a separate `cmek_preserve` event on the same feed. See [CMEK content preservation](https://platform.claude.com/docs/en/manage-claude/access-transparency#cmek-content-preservation) and [CMEK](https://platform.claude.com/docs/en/manage-claude/cmek).
235 They are independent. With CMEK, safety preservation outside your key emits a separate `cmek_preserve` event on the same feed. See [CMEK content preservation](https://platform.claude.com/docs/en/manage-claude/access-transparency#cmek-content-preservation) and [Customer-managed encryption keys](https://platform.claude.com/docs/en/manage-claude/cmek).
236236 </Accordion>
237237
238238 <Accordion title="How can I tell that my Access Transparency record has not been altered?">
from line 250
250250* [Compliance API overview](https://platform.claude.com/docs/en/manage-claude/compliance-api)
251251* [Activity Feed](https://platform.claude.com/docs/en/manage-claude/compliance-activity-feed)
252252* [API and data retention](https://platform.claude.com/docs/en/manage-claude/api-and-data-retention)
253* [Customer-Managed Encryption Keys (CMEK)](https://platform.claude.com/docs/en/manage-claude/cmek)
253* [Customer-managed encryption keys (CMEK)](https://platform.claude.com/docs/en/manage-claude/cmek)
254254* [Claude Code data usage](https://code.claude.com/docs/en/data-usage)
255255* [Trust Center](https://trust.anthropic.com/resources)
256256
No line in this hunk matches that.