Teams evaluating AI privacy controls should not treat customer-owned storage and no conversation storage as interchangeable promises. The boundary is the route and its contract.
Anthropic’s Enterprise Frontier Safeguards (EFS) announcement describes a specific architecture: monitoring activity data can live in a customer’s own cloud account under customer-controlled keys, access policies, and audit logging. Anthropic says rollout is phased. This does not show that an intermediary inherits the arrangement.
CometAPI’s privacy policy says it does not collect, store, or record conversation content, while its Responses API contract documents store as defaulting to true and storing generated responses for later retrieval. That is a scope question, not a conclusion: does the policy cover this path, and what happens to prompts, outputs, metadata, and upstream copies?
For a governed CometAPI Responses integration, record the exact route, account, model, request settings, response-retention behavior, and upstream terms separately. Test this CometAPI route with non-sensitive fixtures and require route-specific clarification before asserting EFS or ZDR equivalence. A provider’s customer-owned storage design cannot be imported into another API path by assumption.
Sources: Anthropic EFS announcement, CometAPI privacy policy, and CometAPI Responses documentation.