Privacy Policy — BabyCheers

The short version. BabyCheers is run from Ontario, Canada, and stores your journey on servers in the United States. It has no accounts, so we never ask for your name, email, or password. What we hold is what you put in it: your due date, your baby's nickname, the moments you add, and the photos on them. Only the people you invite can see any of it. We don't sell data, we don't advertise, and there are no third-party trackers in the app.

1. What BabyCheers collects

Everything below is either something you typed into the app or something the app needs in order to work at all. There is no hidden collection.

Your identity — a random ID, not a person

BabyCheers has no sign-up screen. On first launch the app creates an anonymous identity: a random identifier issued to your installation of the app. That identifier is who you are for the rest of the product. We do not know your email address, your phone number, your real name (unless you type one as your display name), or your Apple ID.

Your journey

Your due date — or the date of your last period, which the app uses to calculate the due date and then keeps.
The nickname you give the pregnancy, and the display name and relationship you choose for yourself and for anyone you invite.
The moments you add: their title, story text, date, week, type, and whether you marked them private.
Photos and videos you attach to a moment.
Cheers and comments left by you and by the people you invited.
For a Reveal, the sealed answer and the time you set for it to open.

Your device, if you allow notifications

If you say yes to notifications, Apple issues a device token for your installation of the app and we store it, so a notification can reach that phone and no other. The row is the token, which of Apple's two push environments it belongs to, and the anonymous identity it currently belongs to — one row per installation, and it goes when your journey does. It is not an advertising identifier, it does not follow you to other apps, and it is never used to build a profile of you. Section 8 is the whole of what we do with it.

A note on the sealed answer. When you seal a Reveal, the answer is stored under a database rule that refuses to hand it back to anyone — including your own phone, and including us through the app — until the reveal resolves. That rule is the product feature, not a promise about our staff: as the operator of the database, we retain the technical ability to read the underlying row, and we don't.

Analytics — seventeen events, and nothing else

BabyCheers uses Amplitude to understand whether the app works. It sends seventeen events, and this is all of them: the app being opened; onboarding starting and finishing; an invite link, a partner link or a card link being taken; an invite being accepted; a moment being saved from one of our suggestions; a cheer; a comment; a reveal being sealed, guessed at, and played; a puzzle challenge being started; a weekly note being opened; a reveal reminder being tapped; and a journey being deleted.

Each one is a name and nothing else. They carry no properties at all — not the milestone's title, not the photo, not the comment's words, not the reveal's answer, not who was invited. The event says a comment was posted; it cannot say what it said.

Amplitude's automatic capture, session replay, and experimentation features are switched off in our build, and our remote configuration cannot turn them on. BabyCheers does not ask for App Tracking Transparency permission because it does not track you across other companies' apps or websites.

Technical data

Our providers process ordinary technical information needed to serve a request — IP address, device and OS version, timestamps — in their server and security logs. We use this to keep the service running and to investigate abuse. The website at babycheers.com sets no cookies and includes no analytics, no advertising pixels, and no embedded third-party content.

2. What we never collect

No health or medical data. BabyCheers is a celebration app, not a pregnancy tracker. There is nowhere in it to record symptoms, weight, blood pressure, kick counts, test results, or appointments as clinical information — and we don't want that data.
No contacts. The app never reads your address book. Invitations are links you send yourself, using whatever app you like.
No location. BabyCheers never asks for it.
No advertising identifiers, no cross-app tracking, no data brokers, and no sale or sharing of personal information for advertising. We do not "sell" or "share" personal information as those terms are defined under US state privacy laws.

3. Who can see your moments

Access is enforced in the database itself, by rules attached to every table, rather than by the app being careful. In practice:

A moment you have not shared is visible to you and your partner, if you added one.
People who opened your journey link can see the moments you've included them on, cheer, and comment.
Someone you sent a single card's link to sees that card and nothing else.
A card you mark private stays private, including from people who join later.
Anyone holding a link can pass it on. Treat a BabyCheers link like a photo you've texted: send it to the people you mean, and remove someone from your following list if you change your mind.

There is no public profile, no discovery, no feed, and no way for a stranger to find your journey.

4. Where your data lives

Your journey is stored on servers we rent, so it can reach the family you invited. We use a small number of providers, each doing one job:

Supabase — the database, file storage for your photos and videos, and the anonymous identity system. Hosted in the United States (US East). Photos and videos sit in a private storage bucket that is not publicly readable.
Amplitude — the seventeen product events described above.
Cloudflare — serves this website.
Apple — distributes the app and, if you allow notifications, delivers them through the Push Notification service. A notification's text passes through Apple on the way to your phone; section 8 says what is in it. Apple's own handling of your App Store activity is governed by Apple's privacy policy, not ours.

Your data is stored in the United States, not in Canada. We are based in Ontario, but the servers are not, and while your information is held there it is subject to US law — including lawful access requests by US courts and authorities. That is true of most Canadian apps, and PIPEDA permits it, but it is the kind of thing you should be told rather than left to discover. We remain accountable for your data under PIPEDA wherever it sits, and we require comparable protection from every provider that handles it.

If you are in the UK, the EEA, or Switzerland, this also means your data leaves that region. Those transfers rely on the European Commission's Standard Contractual Clauses, entered into with each provider, together with the technical measures described here.

5. Why we're allowed to hold it

Under PIPEDA, which is the Canadian law we answer to, the answer is your consent — given when you create a journey, add a moment, or invite somebody, and meaningful because this page tells you what each of those does before you do it. You can withdraw it by deleting the journey (section 7), subject to the limitation described there.

For anyone covered by the UK or EU GDPR, the same processing rests on:

Performance of a contract — your journey, moments, media, invitations, cheers, and comments. Without them there is no app to provide.
Legitimate interests — the seventeen analytics events and our providers' security logs, so we can keep the service working and stop abuse. We've weighed this against your privacy and kept the data minimal and non-descriptive for that reason.
Consent — push notifications, which iOS asks you for separately and you can withdraw at any time in Settings.

Photographs of a pregnancy can reveal information about health. We treat your media as sensitive, and we process it only to show it to the people you chose. Where special-category rules apply, that processing rests on your explicit consent, given by choosing to add the moment and share it.

6. How long we keep it

Your journey and its moments: until you delete them, or until you delete the journey.
Deleted content: removed from the live database when you delete it, and cleared from encrypted backups within 30 days.
Analytics events: retained by Amplitude for up to 24 months, then deleted.
Device tokens: kept while the installation exists, and deleted with your journey. Apple invalidates a token by itself when you delete the app, and we drop the ones it tells us are dead.
Server and security logs: kept by our providers for short periods, typically under 30 days.
Dormant journeys: if a journey has not been opened for 24 months, we may delete it after warning any device that can still reach it.

7. Deleting your data

You can delete an individual moment, or your entire journey, from inside the app — Profile, then the delete option. Deleting the journey removes its moments, media, cheers, comments, and invitations. It is immediate, it is not a hidden flag, and it cannot be undone.

The honest limitation. Because BabyCheers has no accounts, your journey is tied to your installation of the app. If you delete the app without deleting the journey, or you lose the phone, that identity is gone — and so is your access. We would have no way to prove the journey was yours, which means we cannot restore it for you and cannot reliably delete it on request either.

What follows from that: if you are about to stop using BabyCheers, or to give up the phone, delete the journey first, while you still have the phone that holds it. There is no way for us to do it for you afterwards, and no way to move a journey between phones — if that changes, this page changes with it.

8. Notifications

BabyCheers sends notifications. It did not when this page was first written, and an earlier version of this section said so; they began on 19 August 2026, and the device token described in section 1 is what makes one reach your phone rather than somebody else's.

They are only ever about your own journey:

A new moment on a journey you follow.
A cheer or a comment on one of your cards — at most one of each per card per hour, so a lively afternoon is not fifty notifications.
Somebody joining your journey, or opening a card link you sent them.
A Reveal opening, and your family playing it.

Two more are worked out by your own phone and never reach a server at all: the reminder that a Reveal opens tomorrow, and the one five minutes before it opens.

A comment notification quotes the comment. That is deliberate — a notification saying only somebody commented makes opening the app the only way to learn anything. It does mean that the words of a comment, the display name of the person who wrote it, and the title of the card travel through Apple's Push Notification service on the way to a phone. Apple holds an undelivered notification only until it can deliver it or it expires.

Nothing else is sent this way. A notification never carries a photograph, a story, or a sealed Reveal's answer.

We do not use notifications for marketing, and we never will. To stop them, turn BabyCheers off in iOS Settings → Notifications — that is the switch iOS itself honours, and it takes effect immediately. Deleting your journey deletes the token with it.

9. Children

BabyCheers is made for adults. You must be at least 13 to use it, and at least 16 in countries where 16 is the minimum age for consenting to online services. We do not knowingly collect data from anyone below that age. If you believe a child has used BabyCheers, write to support@babycheers.com and we'll delete what we hold.

Photos you add may show your baby. Those images are yours; we don't use them to train anything, we don't publish them, and we never show them to anyone you didn't invite.

10. Your rights

Depending on where you live, you have the right to access your data, correct it, delete it, export it, object to or restrict how we use it, and to withdraw consent. Most of these are things you can do directly in the app, which is faster than asking us. For anything else, email support@babycheers.com.

We answer within 30 days. We never charge for a request, and we never treat you differently for making one. Note the limitation in section 7: if you no longer have the phone holding the journey, we cannot verify that it is yours, and we will not act on a request we cannot verify — that protection cuts both ways.

If you think we've got this wrong, you can complain to a regulator. In Canada that is the Office of the Privacy Commissioner of Canada (priv.gc.ca). In the UK and the EEA it is your own data protection authority — in the UK, the Information Commissioner's Office (ico.org.uk). We'd rather you told us first.

11. Changes to this policy

If we change how BabyCheers handles data, we'll update this page and change the date at the top. For anything significant, we'll tell you in the app before it takes effect rather than quietly editing this page.

12. Who we are, and how to reach us

BabyCheers is operated from Ontario, Canada by Lusine Hovhannisyan, trading as BabyCheers ("BabyCheers", "we", "us"), who is the controller of the personal data described in this policy and the person accountable for it.

Write to us at support@babycheers.com about anything on this page, and we aim to answer within seven days. By post:

BabyCheers
2727 Steeles Ave West, Unit 103-188
Toronto, Ontario M3J 3G9
Canada

Still have a question?

Ask us anything about this policy, or about what we hold. A person answers.

support@babycheers.com