Data policies protect the content moving through your agents — detecting secrets and personal data, and deciding what happens when they appear.
Policies — Data
Guardrails for secrets and personal data in agent traffic
Was this page helpful?
Documentation Index
Fetch the complete documentation index at: /llms.txt
Use this file to discover all available pages before exploring further.
Guardrails for secrets and personal data in agent traffic
| URL | /policies/data-policies |
| Sidebar | Policies → Data |
| Roles | Admin · Analytics Viewer, reading |
| Requires | Data policies enabled for your organization |
| Section | What you set |
|---|---|
| Guardrails Configuration | Which guardrails apply and whether each one Blocks or Audits. Two are offered and no more: Secrets, always; and PII, only where it is enabled for your organization — contact support |
| When | How many detections in one request before the guardrail acts, from 1 to 10. Offered on both guardrails, but only the PII threshold takes effect |
| Configure Entities | The specific entities to detect, such as categories of personal data |
| Enforcement Message | What the developer sees when the policy acts. Offered for Block, up to 500 characters. The editor’s own note names Claude Code, Codex and Cursor; it also reaches Copilot and Augment Code |
| Action | Result |
|---|---|
| Create or open a policy | Opens the editor with the sections above |
| Set an Enforcement Message | Defines what the developer reads at the moment the policy acts |
| Message | What it means |
|---|---|
Failed to save policy | The policy was not saved. Your entries remain on screen, so saving again is enough |
| Page | For |
|---|---|
| Analytics — Data | What these guardrails matched |
| Settings | What happens when agents cannot reach Unbound |
Was this page helpful?