Security and data.
Where your nursery’s data lives, who can see it, and how we prove it.
Hosting
Kinderlee runs on OVHcloud in the European Economic Area. OVHcloud is a European company, listed on the French register of approved health-data hosts. We considered Cloudflare and chose not to use it, because of its ownership and where it processes data.
Sign-in
Sign-in is handled by Zitadel Cloud, a managed identity provider, in its Frankfurt region. We do not run our own password store.
One nursery, one set of records
Every table in the database carries a rule that hides other nurseries’ rows. A test for every table proves that one nursery can see none of another’s records, and removing any rule makes a named test fail before the change can ship.
Consent
Each consent decision is added to a record that cannot be edited. A photo is shown only after our own system has checked consent for that child and that purpose, and a parent’s withdrawal takes effect on the next request.
A history that shows changes
Events are linked with SHA-256 hashes, which work like digital fingerprints. Changing any past record breaks the chain.
Personal data, labelled
Every database column that holds personal data carries a label saying what it holds. The labels decide what goes into an export, what is erased and how long anything is kept.
Photos
Photos are compressed, stripped of location, checked for viruses and encrypted with a key for each child.
The assistant
The assistant is Claude, running through Amazon Bedrock in an EU region. National identity numbers never reach it, and it does no emotion or mood detection.
Sub-processors
Every provider that processes data for Kinderlee does so in the EU. Where a provider is US-owned and runs in an EU region, it is named on our sub-processor list with the reason we accept it.
Reporting a problem
If you find a security problem, tell us through the contact in security.txt.
