Localign

Work safely with personal data

Every message is scanned before it's answered. Names, addresses, ID numbers, anything personal gets caught and tagged. Your conversation never leaves our secured models to get an answer. The moment it needs to, you're asked first.

Detects personal data such as names, addresses and ID numbersOnly asks permission when a sensitive detail is genuinely needed externallyEvery step logged in an audit trail
Localign
Personal details rewritten before sending
Your message

Tom de Groot called in sick this morning with flu symptoms and a fever of 39°C. What are we required to do as his employer?

Rewritten
Localign asks externally

What is an employer required to do when an employee calls in sick?

Only the essential question left your organisation
Names and health details are never shared.
Three ways in

Three ways to keep your data yours

When personal information shows up in a request, Localign protects it three ways before anything leaves - always picking the least revealing option that still answers your question.

Secured assistant

This question can be answered entirely by Localign's local AI model - your data never leaves the server.

Option 1

Stays inside

Most requests never need to leave at all.

You asked
Tom called in sick today with flu symptoms and a fever, what should we do?
What the model sees
What is an employer required to do when an employee calls in sick?
Option 2

Rewrite your request

The identifying detail wasn't needed, so it never leaves your environment.

Permission required
Provider
OpenAI
Address: 14 Church Street, Arnhem
CancelAgree
Option 3

Ask for permission

Nothing leaves the EU until you say yes, one item at a time.

Audit trail

Insight into which data was shared where

Every conversation records a full audit trail: what was detected, what was rewritten before it travelled, and which detail was shared with which provider - each with a timestamp.

Personal data
3
DataTypeShared externally
Tom de GrootFull nameNot shared
Flu symptoms, fever 39°CHealth detailsNot shared
14 Church Street, ArnhemAddressOpenAI
+ 2 more
Activity
4
12:03Detection
Personal data detected, request rewritten
Name and health details detected; the question was rewritten before anything left Localign.
12:04External
OpenAI · GPT-5
Schedule an occupational health home visit for this employee's reintegration.
12:04Consent requested
Requesting permission to share with OpenAI
Address: 14 Church Street, Arnhem.
12:05Consent given
Shared with OpenAI
Only the address was released. The employee's name stayed inside Localign.
It is this simple

You ask. We check before anything leaves.

The moment you hit send, your message stops at Localign first - not at the external model. A specialist pass reads it and flags every piece of personal data it can find.

Your message
Tom de Groot called in sick this morning with flu symptoms and a fever of 39°C. What are we required to do as his employer?
Then, per flagged detail
Local processing
Stays entirely inside Localign.
Rewrite
The detail drops out of the question.
Ask permission
Only leaves if you say yes.
Ask for permission

Nothing leaves until you approve it, detail by detail

When an external model genuinely needs a detail, Localign stops and shows exactly which detail it is and which provider is asking. Approve it and only that one detail is released, once. Refuse and the request stays fully inside. Your organisation can also set types such as a BSN or passport number as never shareable: Localign refuses those outright, without even asking you for consent.

Localign
Permission required

Your request: Schedule an occupational health home visit for this employee's reintegration.

OpenAI
Address:14 Church Street, ArnhemAsking to share
Employee's nameNever shared · policy
Waiting for your decision
Nothing extra has been shared yet.
Audit log
Detected
Name and address found in the request
Kept fully inside
The employee's name never left Localign
Permission requested
Asking to share the address with OpenAI
Why it matters

The same message, side by side

Paste it into an ordinary assistant and the real details go straight out. Send it through Localign and only the real question ever leaves.

Any other tool

"...Tom de Groot called in sick with flu symptoms and a fever..."

Sent raw to the external provider
Personal data now outside your walls.
With Localign

"...what is an employer required to do when an employee calls in sick?..."

Only the essential question leaves - names and health details stay with you
Tom's name and symptoms never left your organisation.
For admins

Set the policy once, for everyone

Organisation admins choose which external providers are even reachable. A separate option goes further than per-item consent: it asks the user for permission before every outgoing request, to any provider, even when nothing sensitive is being shared.

Localign
Privacy · External providers
OpenAI
ChatGPT
Anthropic
Claude
xAI
Grok
Google
Gemini
Consent required for all external providers
When enabled, Localign asks the user for permission before every outgoing request to an external provider, even when no sensitive information needs to be shared.

Privacy and security aren't optional settings.
They should be right by default.

Detection, consent, and audit are built into every Localign workspace. Talk to us and we'll walk you through it.