Your application sends
Summarize the onboarding notes for Maria Alvarez, employee 4417-2208. Send the summary to maria@example.com.
Person nameCustom IDEmail address
Decide what
reaches the model.
Detect sensitive details in AI requests. Redact what needs protecting. Block what should stay inside your business.
Built into the gateway
Give AI the task.
Set boundaries for the data.
Customer details, internal identifiers and credentials can travel with everyday work. Choose which detectors run and how each match is handled before a supported request reaches a provider.
01 / In the request
The context stays.
The details change.
A redacted request keeps the surrounding instructions while configured sensitive details are replaced with placeholders.
The provider receives
Summarize the onboarding notes for [PERSON_NAME], employee [CUSTOM_ID]. Send the summary to [EMAIL_ADDRESS].
Redaction applied
Example only. Detection and handling depend on your configured rules and the supported request workflow.
02 / Your handling rules
Different data.
Different decisions.
Choose an action for each detector. Your policy defines which details can be replaced and which should stop a request.
Read the documentationRedact the detail.
Replace detected information with placeholders before sending a supported request to the provider.
Block the request.
Use blocking rules when a detected detail should prevent the request from reaching the provider.
Restore where supported.
Supported redaction workflows can restore details in the response, so the person doing the work gets useful context back.
03 / Detection coverage
Protect what matters
to your business.
Enable the detector groups you need, then configure actions for individual detectors.
Identity
Names, usernames, organisations and government identifiers.
Contact
Email addresses, phone numbers and street addresses.
Financial
Card numbers, account numbers and financial details.
Credentials
Keys, tokens and secrets included in a request.
Health / PHI
Health information in supported requests.
Custom identifiers
Patterns and identifiers specific to your business.
04 / Keep the evidence
A policy is only part of the picture.
See how it is applied.
Review detections over time, by entity type and across the providers and models your teams use. Keep captured request activity close to the work it describes.
Explore observability- Detector activity
- Entity types
- Providers and models
- Captured request context
One shared gateway
Your models.
Your data-handling rules.
Bring data protection to supported requests from your workspace, applications and connected tools.