ZDR settings inherited from parent scopes.
Retention
ZDR
Scope
Org + team
Policy
Enforced
New capabilities
Restrict traffic to provider routes that support zero data retention, so prompts and responses aren't stored on the provider side for your selected workloads.
Org
ZDR on
Default for organization traffic.
Team
Enforced
Team keys inherit the setting.
Key
Locked
Key cannot relax parent policy.
Enforce ZDR at the organization or team level so a child key can't turn it off. The policy is inherited, not left to whoever creates the next key.
See whether a key's ZDR setting was inherited from the organization, team, or user, so an auditor can trace exactly why a workload is protected.
Who Concentrate is designed for
Zero data retention means Concentrate only routes to provider paths that don't store your prompts and responses. You enforce it at the organization or team level, child keys inherit it, and reviewers can see exactly where each key's setting came from.
Restrict sensitive workloads to no-retention routes and prevent child keys from relaxing parent policy.
Pair ZDR with data redaction so traffic is both filtered and routed to approved providers.
Set retention once at org or team scope instead of trusting every new key to copy the right default.
See whether a key's ZDR setting came from the organization, team, or user when someone asks why a workload is protected.
Feature basics