Where does your AI safety layer process personal data?
If your agent sends user messages to a guard model or a personal-data filter, that service handles the same personal data your agent does. So ask the same questions you ask of your model provider: where it runs, whether it saves the text, and whether a data processing agreement is ready.
Three questions for any safety layer
| Question | Why it matters |
|---|---|
| Where are messages checked? | Your customers' reviews ask where personal data goes, and the safety layer is on that path |
| Is the text saved, and where? | Logs of checked messages are copies of personal data |
| Is a data processing agreement ready to sign? | Your privacy team will ask before real customer data flows |
Our answers, as our site states them
- "The HaloGuard EU API and console run on Google Cloud in the Netherlands and Belgium. This is today's setup, not a promise to keep that region." (astroware.ai/trust)
- "Every request and reply you send is checked in the EU." (astroware.ai/eu-mode)
- "We do not save the text you send or the answer in any log, file or database." (astroware.ai/eu-mode)
- "The model server may keep a processed form of it in memory until the server restarts." (astroware.ai/trust)
- "Our data processing agreement is ready to sign: write to core@astroware.ai." (astroware.ai/trust)
Where Astroware fits: Our privacy filter looks for personal data in text and masks what it finds. You can try it on your own text with the free PII checker: astroware.ai/pii-checker. Your text is checked in the EU.
Sources: astroware.ai/trust and astroware.ai/eu-mode.
As of 28 October 2026.