Hosted in the EU
Bloeiindex runs on Microsoft Azure in the North Europe region. The platform and your dossiers stay within the European Union.
Security
Built to protect people.
Bloeiindex holds information about recognisable people. That is why security is part of the foundation, not a setting: where data lives, who can see it, and how it changes.
Where your data lives
In the EU, separated per organisation.
Separated per organisation
Every request runs with the identity of the signed-in user and their organisation. The database itself prevents organisations from seeing each other’s data (Row Level Security).
Secure sign-in
Signing in runs through Microsoft Entra External ID. Bloeiindex does not store passwords.
Who sees what
Access follows role and purpose.
Access per role
Roles determine what someone may see and do. Guides only see the talents they are linked to.
The talent decides
In a check-in, the talent chooses per answer what is shared. Private notes stay with the writer.
Absence protected separately
Absence is a separate, protected data category. Diagnoses and medical details are refused: they belong with the occupational physician.
History preserved
Changes to hours, moments, and absence are added, never overwritten. It stays clear who changed what, and when.
Removal on request
Requests to remove a talent’s data are handled in Admin, with a clear trail.
Automatic deletion
Each organisation sets how long data is kept. Once that period has passed, it is deleted automatically.
AI with identity protected
The model sees tokens, not names.
Before text goes to the AI model, names and other identifying details are replaced by tokens. The mapping table that reconnects them exists only during that one action and is deleted afterwards. The model runs through the OpenAI API and only receives the text with tokens.
See how privacy by default works ↗For your privacy officer
Questions about security?
We gladly walk through the setup with your privacy officer or data protection officer.
Plan a conversation ↗