What SendSafe replaces
EU direct identifiers: name, BSN, IBAN, email address, phone number, city. Detection lowers the risk but is never complete.

- Name
- PERSON_1
- EMAIL_1
- Phone
- PHONE_1
- IBAN
- ACCOUNT_1
- City
- CITY_1
Security
For IT, security and privacy leads. SendSafe runs on the device and swaps personal data for neutral labels before a request leaves for an AI tool. This page sets out what stays on the device, what it sends, and where its responsibility ends.
ChatGPTPrompt sent
The mapping stays on this device
Originals stay on the device. Only neutral labels go to the AI tool.
The details an IT team asks about first.
EU direct identifiers: name, BSN, IBAN, email address, phone number, city. Detection lowers the risk but is never complete.

IT chooses which categories stay local for each team, once. Reporting follows the same line: counts by team, category and tool, never by person and never with content.

The same local protection sits in front of each of the major providers. Adding or changing a model does not mean rewriting policy.
The admin dashboard shows coverage, categories, AI tools and policy per team. Prompt content never reaches it, and usage is never tied to a person.


What we can confirm today. Anything else, ask us in the walkthrough.
Found a vulnerability? Email security@sendsafe.ai.
The product's subprocessors are listed in the data processing agreement.
SendSafe can reduce what reaches an AI provider. It does not replace the decisions your organisation still has to make.
Certification status. SendSafe does not currently claim any security certification or attestation. If that changes, it will be stated here with the scope and date. Questions for a security review are welcome at security@sendsafe.ai.
We walk IT and security teams through the architecture, and scope a pilot around your requirements.