🔐
PII and content controls
Detect, redact, warn, or block sensitive data before it reaches an LLM provider.
Talon helps EU teams answer the questions that come up in customer, security, DPO, and auditor reviews: what data left, where it went, which policy allowed it, what it cost, and whether the record can be verified.
Review questions
- What data left?
- Which provider received it?
- Was PII handled?
- Was spend controlled?
- Which policy allowed it?
- Can the record be verified?Controls
Talon sits at the provider boundary. It checks policy before requests are forwarded and records signed evidence after each decision.
Detect, redact, warn, or block sensitive data before it reaches an LLM provider.
Apply EU strict, EU preferred, or global routing rules based on your data posture.
Record policy decisions, PII findings, model, cost, hashes, and signature for later review.
Evidence map
| Question | Talon control | Evidence |
|---|---|---|
| What AI traffic processed personal or confidential data? | PII scan and data-tier classification. | PII findings, hashes, and signed record. |
| Was data sent to an approved provider or region? | Provider metadata and routing policy. | Provider, region, routing decision, and reason. |
| Was spend controlled? | Pre-spend cost caps. | Estimated cost, actual cost, and caller context. |
| Can the record be trusted later? | HMAC-signed evidence. | talon audit verify <id>. |
Evaluate Talon
Route one workflow through Talon, inspect the policy decision, and verify the signed evidence record.