Privacy Policy

Your data lives in your iCloud. Here’s the paperwork.

Effective July 28, 2026 · Applies to the Burp iPhone app and burpapp.io, operated by Mupiter LLC.

The short version: your feeding data stays on your iPhone and in your own iCloud. Burp has no servers, requires no accounts, shows no ads, uses no trackers, and sells nothing. The only data that ever reaches a third party is an anonymous crash report when the app breaks.

What Burp stores, and where

Burp stores the data you enter: your children’s names, feedings (times, sides, amounts), and any notes you attach. This data lives:

Burp does not have any servers. We cannot read, access, or recover your feeding data — it is technically inaccessible to us, which is exactly how we designed it.

Sharing, and names on feedings

Sharing is entirely under your control and runs on Apple’s iCloud sharing. When you share a child, people you invite can see (and, if you allow, edit) that child’s feeding history. So everyone can tell who logged what, Burp displays the name associated with each participant’s iCloud account next to the feedings they log. Stop sharing at any time from the sharing sheet; participants can likewise leave.

Crash reports — the one exception

If Burp crashes, a crash report is sent to Firebase Crashlytics, a Google service, so we can find and fix the bug. A crash report contains technical diagnostics: device model, iOS version, the app’s stack trace at the moment of the crash, and a random installation identifier. It contains none of your feeding data, is not linked to your identity, and is not used for advertising or tracking. Google processes this data on our behalf solely to provide crash reporting, under its own privacy commitments, and retains it for a limited period (currently around 90 days).

Full honesty: this is the complete list. One crash-reporting service, nothing else riding along.

What we never collect

Purchases

The one-time unlock is processed entirely by Apple through the App Store. We never see your payment details — Apple only tells the app that a purchase exists so it can unlock.

Notifications

Feeding notifications are composed on your device from data that synced through your iCloud. There is no push server and no message ever passes through us.

Website language preference

We use a functional cookie named burp_locale to remember the language you choose on this website. It contains only your language preference, expires after one year, and is not used for advertising or tracking.

Data retention & deletion

Your data is yours, kept as long as you keep it. Delete a feeding, or a child and their whole history, directly in the app — because there is no server copy, deleting it in the app removes it from your iCloud and from synced devices, including shared participants’. You can also remove Burp’s iCloud data entirely from your iPhone’s Settings (iCloud → Manage Account Storage). Crash reports expire automatically per Google’s retention above. For any deletion request or question, email hello@mupiter.com.

Your rights

Depending on where you live (for example the EU or UK), you may have rights to access, correct, delete, or receive a copy of personal data we hold, and to complain to your local data-protection authority. Because Burp’s design means we hold almost nothing — crash reports are the only data that ever reaches us — most of these rights are already in your hands. For anything else, email hello@mupiter.com and we’ll help.

Children’s privacy

Burp stores information about babies, entered by their parents and caregivers. The app is intended for adults; it is not directed at children, and we do not knowingly collect personal information from children.

Changes to this policy

If this policy changes, the new version will be posted here with an updated effective date. Given what Burp is, don’t expect drama.

Contact

Mupiter LLC · hello@mupiter.com