Privacy Policy

PreBaby is a pregnancy tracker and journal for iPhone and Android. What you write in it is the kind of thing you would tell one person, so this policy is written to be read, not to be survived. It explains exactly what is stored, where, who else handles it, and what you can do about it.

The data controller is Rıdvan Uyan. If anything here is unclear, write to [email protected] and ask.

The short version

• You can use PreBaby without an account. In that mode, what you write and the photos you add stay on your phone and are not sent to our servers. Usage events, crash reports and subscription checks (all described below) still run without an account; they do not contain what you write.
• If you create an account, what you write and the photos you upload are stored on our servers against that account, so they can be restored on a new phone and shared with people you invite.
• We show no advertising, the app contains no ad network, and we do not sell your data to anyone.
• Our analytics never carry the text you write or the values you measure. They do carry the kind of thing you did, which week you are in and your pregnancy status. There is no setting in the app to switch analytics or crash reporting off.
• No other user can see your health records and notes unless you explicitly choose it, and followers cannot see them under any circumstances.
• You can export your data and delete it immediately from inside the app. A few records are not reached by deletion; we list them plainly below.

Without an account

Your entries stay on your device only: the due date or last-period date you enter, your week, your mood and symptom entries, notes and journal entries, water, weight and sleep entries, kick counting sessions, contraction timings, medications and appointments, photos you add, your lists (hospital bag, shopping, birth plan, questions), baby-name favourites and letters you write to your baby.

None of that is sent to our servers. It is not backed up by us either, which also means that if you delete the app or lose the phone, it is gone — that is the trade-off of keeping it local.

What does leave your phone without an account is limited to the usage events, crash and performance reports and subscription checks described in the sections below. They are tied to an installation id rather than an account, and they do not contain what you write.

With an account

If you create an account, so that your pregnancy survives a lost phone or can be followed by your partner, we store the following against that account:

• Your account: an email address and a display name, plus how you sign in — email and password, Sign in with Google, or (on Apple devices only) Sign in with Apple. Passwords are kept only as an irreversible hash; the plain value is never stored anywhere, and we never see your Apple or Google password. If you use Sign in with Apple, you may use Apple’s private relay address.
• Your health and pregnancy records: last-period or due date, mood, symptoms, weight, sleep, water, kick sessions, contractions, medications, appointments, birth plan and questions. They are stored to show them back to you, sync them between your devices and build your weekly view.
• What you write and upload: notes, journal, letters to your baby and memory photos. Photos and export files are kept in a private storage bucket and are reachable only through short-lived signed links. We do not read this content, analyse it, or use it to train models.
• Connections: partner invitations, follow links, your follower list and blocks, so that we can decide who sees what and keep blocked people out.
• Purchase records: your subscription status and the gifts you sent, to make sure what you paid for is unlocked. We never see your card details; Apple (iPhone) or Google Play (Android) takes the payment.
• A push notification token, only if you allow notifications (see below).

Usage events

We use Mixpanel to understand which screens help and where a flow breaks. These events do not contain what you wrote or the values you measured: instead of note text we send yes/no flags such as “is there a note”, and your weight, mood choice, kick count and symptom codes are never sent. To be straight with you, though: when you save a record, the kind of record (for example “symptom”) and which week you are in do go.

Every event also carries your pregnancy status (active, paused, archived, postpartum or none) and your week band (1–12, 13–27, 28–36, 37+), together with your installation id (your account id once you sign in), device model, operating system, app version, language, a banded count of your entries, whether notifications and partner sharing are on, and your subscription status.

There is no setting in the app to switch this analysis off. If you want your data removed from Mixpanel, write to us (see “What deletion does not remove”).

Crash and performance reports

We use Sentry so that we can fix a crash or an error. The stack trace, device model, operating system and app version, a short trail of recent app activity such as screens opened, and your installation id (your account id once you sign in) are sent; your email and name are not. The app is configured not to attach default personal data to these reports, including your IP address. About 20% of app transactions (such as screen loads) are sampled for performance timing. Reports go to Sentry’s EU (Germany) region. There is no setting to switch this off.

Push notifications

Only if you create an account and allow notifications: your device’s Firebase Cloud Messaging token is stored against your account, so that notifications from your partner and your circle reach you. The notification text is generic and carries no health record or message content. Google receives the token and that generic text in order to deliver it. Firebase Analytics is not used. The appointment and medication reminders you set are scheduled on your device only.

IP address, logs and location

Our servers log the IP address and time of each request, so that we can notice abuse and attacks. Request bodies, session tokens, email addresses and your notes are not written to the logs; they are stripped before anything is recorded.

Mixpanel also derives an approximate location (country, region, city) from the IP address of the analytics requests, and the app does not switch that off. The app asks for no GPS or precise-location permission.

What the app does not contain

We do not collect your precise (GPS) location, contacts or calendar. The app contains no ad network, no Google Analytics, no Firebase Analytics and no Crashlytics, and we show you no ads. It does contain a crash reporter (Sentry) and Firebase Cloud Messaging, which is used only to deliver push notifications; both are described above.

One exception: if you installed the app from an Apple Search Ads advert, we pass Apple’s attribution token for that install to the service that verifies subscriptions — solely to measure which advert worked. That token does not identify you as a person, and the app never shows a tracking-permission prompt.

Who can see what

• You — everything.
• Your partner — only the parts you chose to share when you invited them. You can withdraw those permissions at any time.
• Your followers — only your name and which week you are in. They cannot see your health records, measurements, notes or photos. Followers send to you; they do not receive anything from you.
• The community — if you write a post or a comment, every user of the app can see it. By default you write under a pseudonym; if you turn that off, your display name is attached. None of your health records ever reach the community.
• Us — the minimum needed to run your account and fix a problem. We do not read your notes and photos; if a support request would require it, we ask your explicit permission first.

Services we work with

• Apple (App Store) — takes the payment on iPhone, and only Apple sees your card details. If you use Sign in with Apple, Apple verifies your identity.
• Google (Google Play, Sign in with Google, Firebase Cloud Messaging) — on Android, Google Play takes the payment and only Google sees your card details. If you use Sign in with Google, Google verifies your identity. Push notifications (iPhone and Android) are delivered through Firebase Cloud Messaging: Google receives the notification token and the generic notification text. Firebase Analytics is not used.
• RevenueCat — verifies whether your subscription is valid. It receives receipts, product information and an app user id (your installation id, or your account id once you sign in — not your email or name), your Mixpanel identifier as an attribute, plus technical request data such as IP address and device and OS details, and on iPhone the device’s vendor identifier (IDFV). It does not receive your notes or health records.
• Mixpanel — receives the usage events described above, including pregnancy status and week band. No free text and no photos are sent. It derives an approximate location from the IP address of the analytics requests.
• Sentry — receives the crash and performance reports described above, in its EU (Germany) region.
• Resend — processes your address and the message content in order to send you email (password reset, invitation, keepsake PDF link). Amazon SES is a supported alternative provider.
• Infrastructure — Supabase hosts the database (Frankfurt); Amazon Web Services S3 stores the photos you upload and your export files in a private bucket (eu-central-1, Frankfurt); DigitalOcean runs the API server; Cloudflare carries the traffic and sees requests and IP addresses; Upstash holds a short-lived cache.

These services process your data on our behalf. We sell data to none of them and none of them uses it for their own advertising.

Where your data is processed

Your notes, photos and health records — everything that actually matters — are held in Europe (Frankfurt). Email is sent from a provider in Europe (Ireland for Resend, Frankfurt for Amazon SES) and crash reports go to Sentry’s EU (Germany) region. By contrast, usage events (Mixpanel) and subscription verification (RevenueCat) are processed in the United States. What reaches those two is limited to what is described above: your notes and photos never go there.

How long we keep it

• Your account, records and photos stay until you delete them; nothing expires on its own. Archiving a pregnancy does not delete it, it only puts it away.
• Files you export and the keepsake PDF are deleted from storage automatically after 7 days; the download link in the email is time-limited too.
• Password reset links are valid for 1 hour, and the token itself is not stored — only its hash.

Your rights, and deleting your data

You have the right to access, correct, export and delete your data.

• Export: from inside the app. This feature requires at least two months of PreBaby Plus.
• Correct: your details, including the dates your week is calculated from, can be changed in the app.
• Delete: open Profile → Privacy and data → Delete my data. It starts immediately; there is no grace period and no waiting time. Your records, notes, photos (including the files in storage), appointments, lists, medications, birth plan, posts and comments, the follower messages you wrote in other people’s feeds and the gifts you sent, preferences and sign-in identities are deleted. Your email address and display name are removed. This is permanent and cannot be undone. You can also request deletion without installing the app: api.prebabyapp.com/account-deletion. Deleting your data does not cancel a subscription; cancel that in your Apple or Google Play subscription settings.
• Ask us: you can make any of these requests at [email protected], write from the address on the account, or complain to your local data protection authority if you think we have handled your data badly.

What deletion does not remove

Four things a deletion does not reach. We say so plainly, because we keep them for a reason or cannot reach them from the app:

• Payment records. The record of your subscription and purchases (which product, when, which store; RevenueCat events, gift payments and template purchases) remains. These are our accounting and tax obligation, and our evidence if a refund or dispute comes up. They contain no card details, because we never see those.
• An anonymous account record and notification tokens. A shell of your account without email or name (random id, role, created and deleted timestamps) and the record that you asked for deletion remain; the payment records hang off that id. Your device’s notification token is not removed by the deletion; it drops only when the device unregisters or the push service reports it as invalid.
• Logs, backups and provider records. Server logs (which contain IP addresses and request times), backups and the records held by Mixpanel, Sentry and RevenueCat are not deleted from the app. You can ask us by email to have them removed.
• Your history at Apple and Google. Purchase history is held by Apple (iPhone) or Google Play (Android); deleting your account with us does not reach it.

If you want these removed as well, write to us — we will remove anything we are not legally required to keep.

Children

PreBaby is intended for adults tracking their own pregnancy, or people they invite. It is not directed at children under 13 and we do not knowingly collect data from them. If we become aware of such an account, we delete it.

Security

Connections are encrypted with TLS, passwords are kept only as hashes, and access to photos is granted through short-lived signed links. The current app (iPhone and Android) connects to the API over HTTPS only; older Android releases used HTTP (details in the Android privacy notice). No system is perfect; if there is a breach we will notify you and the relevant authorities within the time the law requires.

Health data, and what this app is not

The entries you keep in PreBaby are personal health information, and they are treated as the most sensitive thing in the app. But PreBaby itself is not a medical device: it does not diagnose, treat, monitor or warn about any condition, and its week-by-week content is general information whose measurements are averages. It is not a substitute for your midwife or doctor.

Changes to this policy

If we update this policy we publish the new version on this page and change the date at the top, which always reflects the current version. If a change is material, the app will tell you before it applies to you.