Data Security
Keep sensitive data out of model traffic
Redact PII, PCI, and PHI in prompts and responses, route workloads to zero-retention providers where required, and keep evidence that the rules ran.
Which rule ran, which entity type was removed, and whether it applied to the prompt or response.
PII
Redacted
Retention
ZDR options
Evidence
Logs
Input
Card number
Redacted before provider request.
Rule
Support traffic
Applies to support app Universal API key.
Review
Passed
Security can see what changed and when.
New capabilities
What your team gains with Concentrate
Redact before data reaches a provider
Remove selected entity types from prompts, responses, or both on the path through Concentrate.
Route to no-retention providers
Restrict workloads to provider paths that support zero data retention where your policy requires it.
Leave evidence for reviewers
Use request logs and audit logs to show which rules applied without logging the sensitive values themselves.
Who Concentrate is designed for
Teams handling regulated or customer data in AI features
Data rules belong where every model request passes through — not in scattered app code that each team maintains differently. Concentrate applies redaction and retention policy per key or team, then leaves a record security can review.
Security and compliance
Redact PII, PCI, and PHI from prompts, responses, or both, with events that prove filtering ran without storing raw values.
Support and customer apps
Tie rules to Universal API keys so support traffic redacts phone numbers while an internal eval key keeps a different policy.
Healthcare and finance workloads
Combine redaction with zero data retention on provider paths that support no retention for the models you use.
Engineering without reimplementing filters
Ship new AI features on keys that inherit org or team policy instead of copying redaction logic into every service.
Data Security basics