01
Where data lives
In the EU. Separated per organisation.
Bloeiindex runs on Microsoft Azure in the EU. The database itself keeps organisations apart, not just the screen.
Privacy by default
Privacy is on by default. Across the whole platform.
Bloeiindex holds the stories of real people. So privacy is not a setting, but how the platform works: where data lives, who sees what, what the talent shares, and what AI gets to see.
✓Data in the EU✓Access per role✓The talent decides✓AI sees only tokens
Six layers
All on by default. None to switch on.
02
Who sees what
Everyone sees what fits their role.
Roles decide what someone may see and do. A guide only sees the talents they are linked to.
03
The talent decides
Sharing is a choice. Per answer.
In a check-in, the talent chooses per answer what the guide sees. A private note always stays with the talent.
04
Absence
Absence without medical details.
A sick report does not ask for a medical reason. Absence is a separate category, and medical details are refused.
05
History and retention
Nothing overwritten. Nothing kept forever.
Changes are added, never overwritten. After the retention period, Bloeiindex deletes data automatically. Removal on request is done in Admin.
06
AI
AI only sees tokens.
Before text goes to an AI model, names become tokens. After the action, the mapping table is deleted.
Everything about Bloeii AI →Progress note · Q3
Mila de Jong is doing a work placement at Bakkerij Smit in Utrecht. Next conversation via mila@voorbeeld.nl.
OpenAI APISees tokens only
Mila de Jong is doing a work placement at Bakkerij Smit in Utrecht. Next conversation via mila@voorbeeld.nl.The mapping table
Made for one action. Then gone.
For every AI action, Bloeiindex creates a mapping table: names become tokens, and then names again. Then the table is deleted. Not stored, not logged, never sent to the model.
Bloeiindex · EUDossier Mapping tableOnly during this action
Mila de Jong worked with Ahmed Yilmaz this week. Reachable on 06 12 34 56 78.
✓ Saved in the dossier, with real namesD1_PERSOON_1Mila de JongD1_PERSOON_2Ahmed YilmazD1_TELEFOON_106 12 34 56 78
AI model · OpenAI APIWaiting for text with tokens
What we recognise
Same person, same token. Every time.
PersonD1_PERSOON_1OrganisationD1_ORGANISATIE_1LocationD1_LOCATIE_1RoleD1_FUNCTIE_1EmailD1_EMAIL_1PhoneD1_TELEFOON_1BSND1_BSN_1IBAND1_IBAN_1PostcodeD1_POSTCODE_1
✓ Stays readable: dates, and the names of your own programme, phase, and location.
Honest about the limits
Much safer. Not risk-free.
Pseudonymised, not anonymised
As long as the mapping table exists, names can come back. So it only exists during one action.
Recognition can miss something
A nickname or “the only welder on the team” can still make someone recognisable.
So there are more layers
Only needed sources, no private notes, no medical details. And a person reviews the draft.