Summarize the complaint from subscriber +90 543 417 88 21, account VF-C-88231, about the fiber outage in Kadıköy.
↓
tokenize
↓
restore
Summarize the complaint from subscriber [PHONE_8f3a1d], account [CID_4a2e97], about the fiber outage in [LOC_1d8c5e].
The problem Salus solves#
Employees, applications, and AI agents are already sending sensitive data to external AI services. The two conventional responses both fail: blocking breaks the workflow and pushes usage into unmanaged channels, and one-way redaction destroys the context the model needs, so answers come back degraded.
Salus takes a third path. Sensitive values are detected inside your environment and replaced with typed, deterministic tokens — [PHONE_8f3a1d] instead of a phone number. The tokenized request goes to the provider, the provider writes its answer around the tokens, and Salus restores the original values inside your perimeter before the answer reaches the user. The workflow is unchanged and the answer is complete.
Where the intelligence runs#
The detection intelligence is a self-hosted PII model — it runs on your infrastructure and is allowed to see real values precisely because it operates entirely inside your environment. The external model that writes the answer receives tokens only. This division of labor is the core of the architecture: local intelligence manages sensitive data; external intelligence does the reasoning.
The token-to-value mapping is restoration state that lives inside your environment — held per Context, behind a storage interface your deployment controls. Restore decisions happen on your side of the boundary, and no external party has a path to the mapping.
Two ways to run it, one engine#
Salus protects AI two ways, on the same engine, vault, policy plane, and audit trail:
- Integrated deployment — for the applications you build. Salus runs inside your environment, and your application, service, or existing AI gateway calls it locally — via the Salus SDK, a local API, or a gateway adapter — to tokenize before the provider call and restore after. This is the first delivery.
- Endpoint deployment — for the applications you don't control: Salus on managed devices protects browser AI, desktop AI apps, and specialist tools your teams already use, without modifying the applications.
Where Salus Sits covers how to choose the path per surface.
You own the platform#
The entire platform — detection models, restoration state, and protection logic — deploys inside your environment and runs on your servers. Nothing phones home. Salus, the vendor, has no access path to your restoration state or your data.