PII firewall

The PII firewall pseudonymizes personal data in a request before it reaches a model, then restores the original values in the response. Names, emails, phone numbers and similar identifiers are swapped for stable placeholder tokens on the way in, and swapped back on the way out, so the model never sees the raw data while your application still gets a normal answer.

You will find the PII firewall under Services > PII firewall.

Turning the firewall on

Use the Enabled switch in the top right of the page. It takes effect immediately, with no separate save step. The firewall is on by default for new organisations: routing personal data to a model is treated as something you opt out of, not into.

How pseudonymization works

When a request runs through the firewall, detected entities are replaced with tokens such as <PERSON_1> or <EMAIL_1>. The mapping from token to original value lives only for the duration of the request and is never sent to a provider. After the model responds, the tokens in the output are replaced with the original values before the response is returned to you.

Because the same value always maps to the same token within a request, the model can still reason about relationships — two mentions of the same person stay consistent.

Detection drivers

The firewall can detect entities with either a built-in pattern driver or an external analysis service, depending on how your organisation is configured. Both produce the same token format, so switching drivers does not change how your application consumes the response.

Routing to external models

Pseudonymized data is still personal data. Sending it to a non-EU or third-party model remains a data transfer with its own obligations. External routing is only allowed when the firewall is active for the request, or when an administrator has recorded an explicit acknowledgement that accepts responsibility for the transfer. Without one of those, the request is refused rather than sent.

What is recorded

Each firewalled request records that the firewall ran and how many entities were handled — never the entities themselves or the original values. You can review this activity in the audit log.