That is the part that matters. The rest of this page spells out the little that does leave, who receives it, and why.
Everything you log — feeds, sleep, diapers, pumping, growth measurements, temperatures, notes, your baby's name, date of birth and sex, milestone and immunisation ticks — is written to a database file inside Cubby's own storage on your iPhone.
Not your baby's log. Cubby has no user accounts, no sign-in, no cloud sync and no server of ours that receives your baby's information, so nothing you record about your child can reach us. What does leave the app is anonymous and technical, and the next three sections say exactly what it is. There is no advertising, no advertising identifier, and no tracker following you into other companies' apps or websites.
Cubby includes Firebase Crashlytics, which sends a technical report if the app crashes. Those reports contain the device model, the iOS and app version, the code path that failed, and a random identifier Firebase generates for your installation of the app — not your name, not your email, not your Apple ID, and it changes if you delete and reinstall Cubby. A crash report never contains your baby's name or any entry you logged. Crashlytics is provided by Google; their privacy policy is at firebase.google.com/support/privacy.
When Cubby shows its unlock screen, it counts a short list of events through Firebase Analytics, also from Google: that the screen was shown, which layout was shown, and that an unlock completed. These events carry no personal content — nothing about your baby, no name, no contact details — and Cubby never attaches your identity to them. They exist so we can tell whether the unlock screen works, and for nothing else.
Apple handles the transaction itself. Mark Utility Labs never sees or stores your card details, billing address, or Apple ID password.
Your unlock is kept on your device, in the iOS Keychain. If you unlock the whole collection of Mark Utility Labs apps at once, Cubby offers to safeguard that unlock so you can get it back on a new phone — the only feature in the app that involves signing in anywhere. Only if you choose it, Cubby asks you to Sign in with Apple and stores a short record in Google Firestore, keyed to the identifier Apple returns: which unlock you hold and when you got it. Nothing else goes into it, and Cubby never asks Apple for your name or email address. Because that record is keyed to your Apple sign-in it is a per-person record, and Apple's privacy labels for Cubby declare it as linked to you.
Feed and nap reminders are optional and are scheduled locally by iOS on your own device. Nothing is sent through a push server, so no third party learns your baby's routine.
Export builds the file on your device and hands it to the iOS share sheet. Where it goes after that is entirely your choice; Cubby is not involved and keeps no copy.
Because the data sits in the app's storage, it is included in your normal iPhone backup to iCloud or a computer, which Apple encrypts. Deleting the app deletes the data.
Cubby is a tool for parents and caregivers, not for use by children. Information you record about your child is stored only on your device as described above.
Your baby's log is already entirely yours: we never receive a copy, so there is nothing for us to hand over, correct or erase. Export it whenever you like, and delete it by removing the entry, the baby, or the app. For the anonymous crash reports, the unlock-screen counts and — if you created one — the unlock record, email mark@vibecode.review and we will delete what is held.
If this policy ever changes, the updated date at the top changes with it, and any change that affects what leaves your device will be called out in the app's release notes.
Questions about privacy: mark@vibecode.review.