Privacy policy

This policy explains what Buma collects, why, who else touches it, and what you can do about it. It covers the Buma apps for iPhone and Android, the Buma service behind them, and this website.

1. Who we are

MB Marnar, company code 306991895, Kranto g. 12, Paežerių k., LT-70205 Vilkaviškio r., Republic of Lithuania, is the controller of the personal data described here.

Write to team@bumababy.app about anything in this policy. Please use the email address on your account, so we can tell it is you asking.

2. What we collect

Your account

Your email address and display name, passed to us by Apple or Google when you sign in, along with which of the two you used. Buma has no password of its own and never sees one. If you use Sign in with Apple and choose to hide your address, we only ever receive Apple’s relay address — we do not see your real one.

Your baby’s profile

Name, date of birth and optionally time of birth, sex, an optional photo, birth weight and length, time zone, and — if you tell us — how many weeks into pregnancy they were born, which is what lets Buma use corrected age.

What you log

Entries across the trackers Buma ships with and any you create yourself. That includes feeds, sleep and how hard settling was, nappies, tummy time and play, and also temperature, medicines and doses, symptoms, vaccines, doctor visits, weight, height, head size, teeth, mood, milestones and free-text notes. Every entry records who created it and who last edited it.

Photos

The image itself, its dimensions and file size, any caption you add, and the day it belongs to.

Ask Buma

The messages you send, the replies, and a snapshot of the log data used to answer — so an answer can be explained later rather than being a black box.

Your subscription

Which product you bought, which store it came from, whether it is active and whether it will renew, and the customer identifier our billing provider uses. We never receive or store your card details. Apple and Google take the payment.

Device and diagnostics

A push notification token if you enable notifications, plus platform, app version and a device identifier. Crash reports, which contain technical diagnostics rather than the contents of your log.

Sessions

Each sign-in creates a session record. That is what lets signing out — and deleting your account — take effect immediately on every device rather than whenever a token happens to expire.

3. Health data about a child

Your entries and photos are data concerning health, which the GDPR treats as a special category. We process them on the basis of your explicit consent under Article 9(2)(a), given by choosing to record them, and you can withdraw it at any time by deleting the data or your account.

As the parent or guardian, you are the one consenting on your child’s behalf, and you are responsible for having the right to record what you record.

4. Why we process it

• To provide the service — storing your log, syncing it between devices, sharing it with your family, working out sleep windows. Performance of our contract with you.
• To keep it working and secure — diagnostics, abuse prevention, backups. Our legitimate interests.
• To bill you — knowing whether your subscription is active. Performance of our contract.
• To answer you — support correspondence. Our legitimate interests.

We do not sell your data, we do not advertise to you, and we do not use your log or your photos to train AI models.

5. Sharing inside a family

This is the part to read twice, because it is how Buma works rather than an edge case.

A family is the unit of sharing. Anyone who joins yours with an invite code can see every baby in it and every entry and photo attached to them, and can create, edit and delete entries — including ones you made. Their changes are attributed to them, so you can always see who did what.

Removing someone ends their access immediately, but entries they created stay in the history, because they are part of your baby’s record rather than that person’s. Invite only people you are content to give all of it to.

6. Who else processes it

These providers process data on our instructions, under contract, and may not use it for their own purposes.

7. Where it is stored

Your data is held in the European Union, and Ask Buma requests are processed in Google’s europe-west1 region. Where a provider processes data outside the European Economic Area, the transfer relies on the European Commission’s Standard Contractual Clauses.

8. How long we keep it

For as long as your account exists. Deleting an entry removes it from the app straight away; a marker is kept for a limited period so that a device which was offline learns the entry is gone rather than resurrecting it, and the record itself is then purged.

Deleting your account ends every session immediately and removes your personal data, except where the law requires us to keep something — billing records, for example — for a statutory period.

9. Your rights

You can ask for access to your data, correction of it, erasure of it, restriction of how we use it, a portable copy of it, and you can object to processing based on legitimate interests. Where we rely on consent, you can withdraw it without affecting what was lawful beforehand.

Export is available in the app. For anything else, email team@bumababy.app and we will answer within one month.

10. Children

Buma is for parents and carers, not for children. The account holder must be an adult, and the data recorded about a child is provided and controlled by that adult.

11. Security

Data is encrypted in transit. Every read and every write is checked against whether your account belongs to the family that owns the record — asking for another family’s baby returns “not found” rather than “not allowed”, so identifiers cannot be probed. Photos are served through short-lived signed links, and every session can be revoked individually.

12. This website

This site sets no advertising cookies and sells nothing about you to anyone. The only personal data it collects directly is an email address you choose to type into the launch-notification form, which we use once, to tell you Buma is out, and then to nothing else.

It also uses PostHog for product analytics — how many people read a page, which language they read it in, and whether the launch-notification form worked. What that means for you depends on which of three states you are in, and we would rather spell them out than round them off:

• Before you answer the banner. We count the page you are reading, but store nothing on your device — no cookie, no browser storage. Close the tab and there is nothing left to recognise you by, so you are a visit rather than a person. We do this on the basis of our legitimate interest in knowing whether anyone reads the site at all.
• If you accept. PostHog additionally stores an identifier in your browser, so return visits are recognised as the same person and we can tell twenty readers from one reader who came back twenty times.
• If you decline. Measurement stops. Not “continues without a cookie” — stops. You said no, and that is the whole of it.

In every case PostHog receives the pages you visit and approximate location derived from your IP address. It does not receive your email, and there is no baby data on this website to receive — the app is a separate thing, covered by the rest of this policy. PostHog Inc. processes this on our instructions on EU servers. You can change your mind at any time by clearing this site’s data in your browser, which removes the stored decision and brings the banner back.

13. Changes

We will post any changes on this page and update the date at the top. If a change materially affects you, we will say so in the app before it takes effect.

14. Complaints

You can complain to the State Data Protection Inspectorate of Lithuania (vdai.lrv.lt) or to the supervisory authority where you live. We would rather you told us first, at team@bumababy.app — most things are quicker to fix than to escalate.