Privacy policy
Effective from 5 September 2026 · Bayiku v1
The eight sections below are copied word for word from the Privacy page inside the app. Every sentence can be checked against Bayiku’s code today — if the app changes, this page changes in the same change.
No account, no server
Bayiku runs entirely on this device. There is no sign-up, no sign-in, and no entry is sent to a server — the server has not been built yet. If syncing between caregivers over the internet is added later, this page is updated along with it.
Entries stay on the device
Diapers, nursing, bottles, pumping, sleep, growth, the baby profile, and the caregiver list are stored in a single SQLite database file in this app’s own storage on this device. The app does not copy it anywhere. One thing is outside its control: the system backup — if Google or iCloud backup is on, this app’s data goes into it just like any other app’s.
No analytics, no ads
There is no analytics, advertising, or third-party tracking inside the app. Opening a screen and logging something sends nothing off the device.
Crash reports
If the app stops unexpectedly, the technical details of what happened are sent to an error tracking service (Sentry) so it can be fixed: the kind of error, the line of code where it happened, the app version, and the device model. The contents of your baby entries are not included — no names, no dates of birth, no numbers, and no trail of which screens were opened. This only runs in the release build of the app.
Notification permission
The only permission asked for is the notification permission, and it is used only for reminders and for timers that are running. On Android the app is also registered to wake up after the device restarts, so reminders that are already scheduled are not lost. There is no location, contacts, camera, or microphone permission.
Deleting the app deletes its data
The database lives in the app’s own storage, so deleting the app deletes the entries with it. The only thing that can be left behind is a copy inside the system backup, if that backup is switched on for the device.
Exchanging files between devices
Entries can be shared with another caregiver through a file that you pick and send yourself — over chat, email, or anything else in the device’s share sheet. There is no server in between. The file is not locked in any way: anyone who receives it can read every baby entry inside it, including anyone who later gets that file from them, and any copy left behind in a chat backup. Treat it like any other health document. Once the file has left through the share sheet, where it goes is outside this app’s control.
Doctor reports
Reports in text, CSV, and PDF form are meant to be readable by anyone who opens them — that is the point. Only one thing separates them from an exchange file now: deleted rows are left out of a report, while an exchange file must carry them so that deletions spread too.