Calm starts with clear choices.

This page covers two things: how the Kiemly app handles your data, and what this website does with its two forms. The app collects nothing. There is no account, no analytics and no crash reporting, and no server of ours — except the optional wake service for Baby Buddy below, which stays off until you turn it on.

What you record in the app

Everything you keep about your child — feeds, sleep, nappies, growth, medication, notes and memories — stays on your own iPhone. We don't see it and we can't reach it.

If you connect Baby Buddy

Your log goes to the Baby Buddy server you run yourself, at the address you enter. That's your server; we're not in between. Its key lives in your phone's Keychain and only leaves the device towards that server.

Kiemly Oppas (Android)

Kiemly Oppas is a separate, small app for a grandparent or sitter. It only works with an invitation from the parents. What you see and keep in it (the child’s first name, sleep, feeding, diapers, tummy time, temperature and notes, with their times and amounts, and when a medicine was last given) comes from and goes to the parents’ own Baby Buddy server, at the address in the invitation and encrypted in transit. We have no access to it and receive nothing. The invitation (server address and key) is stored encrypted in your phone’s storage and is left out of Android backups. Once the parents have made a rota, the app fetches nothing about the child outside your shifts. The app asks only for permission to use the internet and to show notifications: not your location, contacts, photos or microphone, and it has no ads and no analytics. The sitter’s key is a Baby Buddy Caregiver: it can add and change, not delete, and the parents can always withdraw it. “Disconnect” erases the invitation and everything the app remembered.

Notifications for the sitter, on Android and in sitter mode on an iPhone: that a shift begins or is about to end, that a nap or a feed is coming up, or that the parents sent a message. Your phone plans them itself, from what it just fetched from the parents, and only the ones the parents switched on for you. If the parents have Wake on changes on (below), push.kiemly.nl can wake your phone during a shift, so those notifications stay right while the app is closed. That server then keeps, per sitter: an unreadable code for your seat, the hash of a secret derived from your key (never the key itself), the start and end times of your shifts, and your phone’s push address. On Android the wake goes through Google’s Firebase Cloud Messaging, on an iPhone through Apple. The message only says “wake”: Google and Apple see that your phone is woken, not why or about whom. “Disconnect” makes the server forget your push address; when the parents remove you, your seat is gone.

If you turn on Wake on changes

A free extra for families who bought Kiemly Family and run their own Baby Buddy. It stays off until you turn it on. Then your phone signs up at push.kiemly.nl, a server of ours in the Netherlands. For each phone it keeps: a random enrolment, the push address Apple gave your phone, the number of your Family purchase as Apple signs it (to check that you bought it), the secret your Baby Buddy signs its notices with, and for one hour the ids of notices that arrived, to recognise repeats. Your Baby Buddy only tells that server that something changed and what kind of entry it was, for example a feed — never what it says. We then wake your phone, and it fetches the change from your own server itself. We never get your server's address, your key or your entries. We do learn when something is logged in your home; that is why it stays off until you turn it on, and why the server keeps no access log for this service. When you start or stop a nap or a feed, your phone says that too: which kind, when it began, and an unreadable code for the child — no name. The server uses it to put the Live Activity on the other parent's lock screen at once, and to take it away when it stops; only while it runs does the server keep that activity's push address. Which phones belong to one family the server tells from an unreadable code derived from your Baby Buddy's address, not from the address itself. Turn it off and we delete your enrolment. The extra may stop one day; Family itself stays as it is then.

If you use Family Sync

Traffic between your own devices runs through your own iCloud. Kiemly encrypts the contents on the device itself before anything is sent, with a key that only exists on the family's approved devices. What Apple stores is therefore ciphertext: visible is that something synced and when, not what it says.

Willow

The thinking-along is computed on your iPhone itself. No data goes to a model elsewhere, and nothing about your child is used to train anything that exists outside your phone.

If you send us a sync report

Settings → Sync has a button that mails us a report. Nothing about it is automatic: the report is made on your own phone, your Mail app opens, you can read every word, and it only goes when you press send. It holds nothing about your child — only times, which step of syncing it was, and the answer your own server gave. Close the message and nothing goes.

Purchases

Payments run through Apple. We never see payment details from Apple — only whether a purchase is valid.

Taking your data with you or throwing it away

Settings holds an export of everything, always, at no price. Delete the app and the data is gone from your phone; what sits on your own Baby Buddy stays there, because you manage that.

Children

Kiemly is meant for parents. The app is not directed at use by children themselves and collects no data from them beyond what a parent records on their own device.

Forms on this website

For a sign-up, we store your email address and, when provided, your name and platform. For a question, we store your email address, your question and, when provided, your name. We only use this data to process your sign-up or answer your question. A sign-up is kept until you unsubscribe; a question is kept for one year and then deleted automatically.

Spam and security

The forms use a honeypot, minimum completion time, origin check and a rate limit based on a one-way hash of the IP address. That hash is only used temporarily to limit abuse. We don't use a tracking captcha.

No website tracking

This website sets no analytics or advertising cookies. Only your language choice is stored locally in your browser. Automatic dark mode uses your browser preference and local time.

Deletion

Want a form submission removed? Send the request from the same email address, either through the question form on the homepage or by mail.

Questions

Email info@kiemly.nl.

Last updated: 18 October 2026 (Kiemly Oppas: shifts and notifications).