Privacy policy
Applies to the Babytakt app (Android and iOS) and to this website. Last updated: 29.10.2026. The German version is authoritative.
This is a courtesy translation. The legally binding version is the German Datenschutzerklärung.
1. Controller
bork.media
Thomas Borkowski
c/o IP-Management #12555
Ludwig-Erhard-Str. 18
20459 Hamburg
Germany
E-mail: hello@babytakt.app
We are not legally required to appoint a data protection officer.
2. The app on your phone
2.1 What Babytakt stores
Babytakt keeps a database in the app's private folder. Only the app itself can access it; other apps cannot read it. It contains what you enter yourself:
- entries for meals (nursing, bottle, solids), diapers and sleep — each with a time
- health details: weight and height, temperature, medication and vaccinations
- your own notes and moments, to which you can attach a picture
- about the child: name, date of birth and, if you choose one, a photo
- your settings (color, font, visible buttons)
This is the same on both platforms: on Android the database sits in the app's private folder, on iOS in the app's protected container. In both cases only Babytakt itself can access it.
This data is not transferred to us. We have no access to it and do not even learn that you use the app. Delete the app and the database is gone; only the daily backups in “Download/Babytakt” (Android only) stay behind (section 4).
2.2 Where the entries come from: from you
Every line in the app was typed in by you. Babytakt measures nothing, reads no sensors, pairs with no scale and no thermometer, imports nothing from other apps or health records, and buys no data anywhere. There is no second source. What the app holds is there because a parent or an invited person wrote it down.
So there is nothing we could know about you that you do not. No derived values, no assessment, no prediction. The app computes averages and intervals from your own entries, nothing more, and the result stays on the device.
Health details — weight, height, temperature, medication, vaccinations — are specially protected under Art. 9 GDPR. The same applies to them as to everything else, only with extra care: without family sync they never leave the phone. With sync they travel encrypted, and the health area carries its own key: whoever was not given it when invited cannot read those entries — nobody in the family and nobody at our end. If you would rather not keep them at all, simply leave the fields empty; the app does not ask.
2.3 Permissions
On Android, Babytakt asks for these permissions — each only when you use the feature, none at startup:
| Permission | What for |
|---|---|
| Notifications | For reminders and updates from your family. Asked when you turn on a feature that uses notifications. |
| Alarms & reminders | So a reminder arrives on the minute. Without this permission it arrives a little less precisely. |
| Camera | Only to scan an invitation QR code. The image is discarded immediately; no photo is taken and nothing leaves the phone. |
| Vibration | A short confirmation when an entry is saved. At night, without looking. |
| Internet | For family sync (section 3) and, only when you send one, for a message through “Write to us” (section 2.6). Otherwise the app opens no connection. |
On top of that come technical permissions that Android grants without asking, mostly from the components for background work, Firebase and Google Play Billing: seeing the network status, staying awake briefly, setting reminders again after a restart and finishing a task in the foreground. iOS adds none.
Babytakt demands no access to contacts, location, microphone or your photos — you pick a picture through the system chooser, which hands the app only that one image.
2.4 What is not in the app
No ads. No advertising ID. No analytics or statistics services. No crash reports to third parties. No fonts or images loaded from anywhere at startup.
Two components from Google are included, each for exactly one purpose: Firebase Cloud Messaging for the wake-up call in family sync (section 3.7) and Google Play Billing for the optional donation (section 6.1). Firebase stays completely silent without a family: it only registers with Google once you are in a family and the switch From the family under Reminders is on.
2.5 Deleting — any time, without asking us
Because the data sits with you, the right to erasure (Art. 17 GDPR) is built into the app and needs no request to us:
- Single entries: tap, delete — gone at once.
- A child: the profile sits in “Recently removed” for three days and can be restored. After that the profile, all its entries, moments and pictures are deleted for good, on every device in the family.
- Everything: under Settings → Data → “Delete all data” you delete the whole history in one go — children, entries, photos, moments, reminders and the app's daily backups in “Download/Babytakt” (Android only). If you are in a family, the phone leaves it; whoever founded it can dissolve it for everyone at the same time (section 3.5). If you want to keep the history, write a backup file first (section 4).
- The app: uninstalling takes the database with it. What you backed up into a folder yourself, and the daily backups in “Download/Babytakt” (Android only), stay there — delete them where they lie, or beforehand with “Delete all data”.
2.6 “Write to us” in the app
If you send a message through “Write to us”, the app transfers your text (with the topic, if you pick one), your email address if you enter one, and the app version (for example “Babytakt 1.0”) to the same mail service as the contact form on babytakt.app (section 5.2), including spam protection (section 5.3). No entries, no child's name, no identifiers and no device data go with it. Nothing is sent until you tap “Send”. Legal basis is Art. 6(1)(b) or (f) GDPR (answering your request).
3. Family sync (optional)
When several people track the same child — the other parent, grandparents, daycare —
you can create a family and invite the others. Only then does the app talk to a server,
and only to our own at sync.babytakt.app. If you never enable sync, this
entire section does not apply to you.
3.1 End-to-end encrypted
The app encrypts your entries on the phone before transferring them (AES-256-GCM). The key is created on the device, kept in the protected key store (Android Keystore or iOS Keychain) and handed directly to the other phone when you invite it — it never reaches the server. What sits there is a package nobody can open: not us, not the data center operator, nobody with access to the disk.
3.2 What sits on the server
| Stored | Why |
|---|---|
| The encrypted package per device | So the other devices can fetch the latest state. It usually holds only what is new since the day before; a new one replaces the old one, and it is deleted as soon as every other device has fetched it — after 14 days at the latest. Only when a device joins or has not fetched for more than a day do the others store their full state once. |
| Random family and device identifiers | To match packages to the right family. They are random and contain no names. |
| A hash of the device token | Device authentication. The token itself is not stored, only its checksum. |
| Timestamps per device | Created, last seen and up to when it has fetched, plus a note when it currently needs the full state — for cleanup, the device list and to know when a package may be deleted. |
| The wake-up address per Android device (a Firebase Cloud Messaging token) | So the service can nudge the other phones in the family (section 3.7). Only while the switch From the family is on; switched off, it is deleted. |
| Open invitations | A check value of the code, the sealed key package for the invited person (only someone with the full code can open it), which device sent the invitation and when it expires: automatically after 10 minutes (QR code) or 24 hours (link), or as soon as it is redeemed. At most five can be open at once. |
Not stored: names, e-mail addresses, phone numbers, device models, advertising IDs. The server does not know who you are and cannot derive it from the data.
3.3 Abuse prevention
So that nobody can guess join codes, five attempts per minute and IP address are allowed. For this, the IP address sits briefly in memory and is not stored permanently. A family holds at most ten devices. The legal basis is our legitimate interest in secure operation (Art. 6(1)(f) GDPR).
3.4 Logs
The service writes neither packages nor tokens nor join codes into its logs. Access logs exist only to the technically necessary extent, with truncated IP addresses, and are deleted after a few days.
3.5 Deletion
- Remove a device: In the settings under Family you take any device out with Remove from the family — its package and its access are deleted with it.
- Dissolve the family: Whoever founded the family dissolves it for everyone under “Delete all data” with “Dissolve the family for everyone”. This deletes packages, pictures, invitations and access of the whole family immediately and completely.
- By itself: Packages disappear as soon as everyone has fetched them, after 14 days at the latest. A device that has not checked in for 90 days is removed from the family; a family with 90 days of no activity is deleted entirely.
Your entries on the phone remain untouched in every case. The legal basis for sync is Art. 6(1)(b) GDPR — without this processing, the feature you requested cannot exist.
3.6 Pictures in sync
Pictures attached to moments travel encrypted like everything else. They sit separately from the entries at the service and are deleted there once every device in the family has fetched them, after 14 days at the latest. The original stays on the phone it came from.
If you do not want photos in the family, switch Sharing photos off in the settings: the texts are then synced and the pictures are not. On the other devices the moment appears without its picture.
3.7 The wake-up call (Google Firebase Cloud Messaging)
So that an entry reaches the other phones quickly, the service nudges them after a change. On Android this happens via Firebase Cloud Messaging (FCM) from Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. The nudge is empty: it carries only the word abgleich and the phone's wake-up address — no text, no name, no kind and no value of an entry. The phone then fetches the encrypted package from our service and writes the notification itself.
Google thereby learns that and when something was logged in a family and can link the wake-up address to a device — never what was logged. This may involve a transfer to Google LLC in the USA, based on the European Commission's adequacy decision for the EU-US Data Privacy Framework, under which Google LLC is certified.
The wake-up call only runs in a family and only while the switch From the family under Reminders is on. Switch it off or leave the family, and the wake-up address is deleted on our side and unregistered with Firebase; sync then runs more slowly, but without Google. Legal basis is Art. 6(1)(b) GDPR — fast sync is part of the feature you switch on.
4. Backup files
Babytakt can write your history into a file that you store yourself — on the phone, in your cloud, wherever you like. This file is not encrypted, so that it is still readable in ten years. Where you put it is your decision; if it lands in a third-party cloud, that provider's privacy policy applies there. We never see the file.
On Android, on top of that comes the daily backup: once a day, when you open the app, it writes a file into the “Download/Babytakt” folder on your phone by itself and keeps the last seven. These files are not encrypted either and do not go through our service. You can see the folder in your phone's Files app; apps you have given full access to your files can read it too. On phones older than Android 10 the file goes into the app's own folder instead. “Delete all data” removes these backups as well (section 2.5).
Independently of this, your phone backs up apps itself if you have turned that on: Android includes Babytakt's database in its backup to Google, iOS in the iCloud backup. That happens between you and Google or Apple; we are not involved and see none of it. You can turn it on or off in your phone's settings.
5. This website
The site runs on our own server at dogado GmbH, Antonio-Segni-Straße 11, 44263 Dortmund, Germany; a data processing agreement is in place. When you visit, technically necessary access data arises (requested page, time, browser identifier, IP address). It serves secure operation (Art. 6(1)(f) GDPR) and is deleted shortly.
No cookies. No cross-site tracking. No embedded third-party content. We count page visits ourselves (section 5.4). Fonts are served by this server itself — in particular, there is no connection to Google Fonts. If you write us an e-mail, we process your details only to reply.
5.1 Your choice between day and night
If you set the light or dark appearance at the top right, the browser remembers this
choice in local storage (key babytakt-schema, value hell or
dunkel). This is not a cookie: the entry stays on your
device, is never sent along, and can be removed any time with your browser data. If you
never touch the switch, nothing is stored — your system setting applies.
5.2 The contact form
When you submit the form, we transfer your name, e-mail address and message
to our own delivery service at api.bork.media — the same server, the same
controller, no form provider and no third-party service. From there the content lands in
our inbox as an e-mail. There is no database: what you write exists afterwards only as an
e-mail and is deleted once your request is settled and no retention duty stands in the
way. The legal basis is Art. 6(1)(b) or (f) GDPR (answering your request). You can always
write to us directly instead — the address is in the legal notice.
5.3 Spam protection (ALTCHA)
So that the form is not flooded by machines, we use ALTCHA. Unlike common captchas it runs on our own server: no picture puzzles, no Google reCAPTCHA or hCaptcha, no cookies, no data flowing to third parties. Your browser receives a random task, computes it in the background and sends the result along — only these random values are processed, nothing about you. In addition, an invisible extra field catches automated submissions.
So that nobody can fire the form every second, the service briefly counts requests per IP address (five in ten minutes) and the random values used. Both sit only in memory, are discarded after a few minutes and are never stored permanently. The legal basis is our legitimate interest in an abuse-free form (Art. 6(1)(f) GDPR).
5.4 Counting visits
We count how often the pages of this website are visited using the software Umami. It runs on our own server at dogado GmbH (see above); no data is passed to third parties, and the app is not affected. When you open a page, a small script transmits the address of the page, the page you came from, browser, operating system, device type, screen size and language setting. Country, region and city are roughly derived from the IP address; the IP address itself is not stored. Umami sets no cookies and stores nothing on your device. To count visits, a check value is formed from the IP address and browser identifier; it is created anew every month, and the IP address cannot be calculated back from it. The legal basis is our legitimate interest in designing the website according to need (Art. 6(1)(f) GDPR). You can object (Art. 21 GDPR); if "Do Not Track" is switched on in your browser, nothing is recorded.
6. Installation through the app stores
Babytakt is distributed through the Google Play Store and the App Store. When you download and update, Google Ireland Limited and Apple Distribution International Ltd. process data of your store account under their own responsibility — we have no influence on this and learn nothing beyond anonymous totals in the respective developer console (for example: how many installations exist in total). Google's and Apple's privacy policies apply.
6.1 The optional donation
Babytakt is free. At the very bottom of Settings you can support the app with a one-time in-app purchase; it unlocks nothing. Google Play (Google Ireland Limited) handles the payment as the seller, through the Google Play Billing library. So that the amounts appear in your currency, the app asks the Play Store on your phone for the prices when it opens.
We receive no payment data: no name, no card, no account. In the developer console we see that a purchase took place (amount, date, country, order number). The app itself stores nothing about it and sends nothing to our service. Legal basis is Art. 6(1)(b) GDPR; otherwise Google's privacy policy applies.
7. Data about your child
Babytakt is made for parents, not for children. What is recorded about the child is entered by the parents and stays in their hands: on their devices, in sync only encrypted. There is no profiling, no comparison with other children, no automated decision-making and no sharing with third parties — not even in anonymized form for research or advertising.
So we collect nothing about your child. We provide a notebook and a sealed envelope; what goes into it and who may read it is your decision — for the health details even per invited person (section 3). If the child later grows old enough to decide for themselves, the whole history is with you and can be handed over or deleted without us ever knowing.
8. Recipients
Our service and this website run at the hoster dogado GmbH, Dortmund; all our servers are located in Germany. Beyond that there is one recipient, only in the cases described: Google Ireland Limited, for the wake-up call in family sync (section 3.7, with a possible transfer to Google LLC in the USA based on the EU-US Data Privacy Framework) and for an optional donation (section 6.1).
9. Your rights
You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21 GDPR). Because we keep no accounts, we cannot match you to any record — the data sits with you, and the answer sits in the app: you can view, back up and delete it yourself at any time.
You can complain to any supervisory authority; the one responsible for us is the Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen, Kavalleriestraße 2–4, 40213 Düsseldorf, Germany.
10. Changes
If a feature arrives that touches new data, we change this text beforehand and update the date at the top. Older versions are available on request.
11. Reporting abuse
The service only carries encrypted packages; we do not see their content and cannot check it. If a family is used for something unlawful, write to us at hello@babytakt.app. Anything that narrows down the device or the family helps — for instance the invitation link that brought you in.
We look at every report and may suspend the device concerned or the whole family; the basis for that is in the terms of use. Whoever reports gets an answer. Whoever is suspended learns the reason as soon as we can name it, and may object.