Personal Data Protection
Flag, redact or block email addresses, phone numbers, IBANs, card numbers and IP addresses in requests before any provider sees them, and where to set it.
What it does
EUrouter can look for personal data in your requests before they are routed to a provider. For each type of personal data you choose what happens:
| Action | What happens |
|---|---|
| Off | The default. EUrouter does not look for this type. |
| Flag | The request is served unchanged, and EUrouter records the finding. |
| Redact | The value is replaced with a placeholder, such as [EMAIL], before any provider sees it. |
| Block | The request is refused before any provider is called. Nothing is charged for the model. |
The types EUrouter detects are email addresses, phone numbers, IBANs, card numbers and IP addresses. EUrouter keeps none of the data it finds, only how many items of each type it found.
Where to set it
For your organization
An organization owner or admin sets the actions every key follows in the dashboard under Guardrails → Personal data. Members can see them but not change them.
With an organization-wide management key, send the actions as pii in the organization policy, for example "pii": { "EMAIL": "redact", "IBAN": "block" }. The update replaces the whole organization policy, so read the current policy first and send it back with the new field, as the prompt-injection example shows. A type you leave out is off. An update without pii keeps the rules you set before; send "pii": {} to switch every type off.
For a workspace or a member
An owner or admin can also set a rule for one workspace or one member, on the Workspace and Member tabs. A workspace rule applies to every request made in that workspace, with any key. A member rule applies to every key the member owns and to their own requests from the dashboard. Both can only be stricter than your organization's rule: weaker choices are locked, and the API refuses them with a 400 that names the field. With an organization-wide management key, use the workspace and member guardrails endpoints, PUT /api/v1/settings/policy/workspaces/{workspaceId} and PUT /api/v1/settings/policy/members/{userId}. Members can see these rules but not change them.
A request gets the strictest rule of every level that applies to it: the organization, its workspace, its member, its key and the request itself.
For one key
A key can be stricter than every level above it, never weaker. On the API keys page, open the key's menu, choose Edit key, and set its actions under Personal data. Actions weaker than your organization's are locked. For each type, a request gets the strongest action of every level: block, then redact, then flag. You can also set a key's actions on the Key tab under Guardrails → Personal data.
Where to see findings
The request log shows how many items of each type a request contained and the reason, such as pii.redacted or pii.blocked. It never shows the data itself.
Prompt-Injection Protection
Flag or block requests that contain known prompt-injection phrasings, before any provider sees them. What it checks, what it misses, and how to switch it on.
Authentication
Authenticate with the EUrouter API using API keys: create a key, send it in the Authorization header and keep it secret in production.