Privacy policy

We do not have your entries.

The mama.how app has no account and no login. Your entries stay on your iPhone and, if you have iCloud Backup turned on, in that backup too, under your Apple ID. We cannot reach them. Apple handles purchases. The only moment the app sends anything to us is Premium pairing with a QR code; we describe it below field by field. The website has no analytics and no ads.

Last updated: 2026-11-22. Covers the mama.how website and the mama.how iOS app.

This is a translation of the Polish privacy policy. In case of any conflict, the Polish version at /prywatnosc prevails.

1. Who we are and how to reach us

The mama.how website and the mama.how app are run by Blazej Lewartowski, sole proprietorship (jednoosobowa dzialalnosc gospodarcza), ul. Swieradowska 47, 02-662 Warszawa, Poland, NIP 5242414096, REGON 382843314. This is the data controller under the GDPR: one person, not a company and not a team.

Contact for anything, privacy included: [email protected]. One person reads it and usually replies within a day. We have not appointed a data protection officer, because the scale of processing does not require one.

2. The mama.how app

What the app is

mama.how is an iPhone app for parents, from trying for a baby, through pregnancy and the baby months, to a toddler up to the 3rd birthday. It works as a journal and a calendar: you record what you want to remember (your cycle, pregnancy, measurements, test results, photos, your child's development, reminders), and the app shows information about each stage, with its sources. Estimates such as the due date, the expected period or the estimated fertile window are approximate. The app does not assess your health or your child's health, does not diagnose and does not replace a doctor or a midwife.

The app is designed to work without us. We run no accounts, we have no server with your entries and no dashboard where anything of yours could be looked at.

What the app does NOT collect

  • No account, login, password or user profile. The app starts straight away. We do not even use Sign in with Apple.
  • We do not ask for your name, address, phone number or e-mail address.
  • The app contains no analytics or advertising SDK: no Google Analytics, no Firebase, no Facebook Pixel, no Matomo, nothing similar. The app sends us no statistics, events or device identifiers.
  • No ads, no IDFA and no App Tracking Transparency prompt, because there is nothing to track.
  • We have no access to your entries: journal, cycle and observations, measurements, test results, ultrasound and bump photos, voice notes, letters to your child.
  • We never see payment data: card number, billing address or your Apple ID.
  • We do not sell data, share it with advertising partners, build profiles or train AI models on your entries.

If you agree in iOS settings to share analytics with app developers, Apple may pass us aggregated statistics and crash reports under Apple's rules. This is a system setting, not an app setting; you turn it off in iOS Settings (Privacy and Security, Analytics and Improvements).

App data at a glance

DataWhere it isWho can reach itHow long
Entries and profiles: cycle and fertility observations, intercourse, pregnancy, measurements, test results, child's journal, medicines and reminders, lists, settings On your iPhone, in the app's data; in your iCloud Backup if you turned it on You. Apple stores the iCloud Backup under its own rules. Not us Until you delete them or uninstall the app; the iCloud Backup as you set it
Photos (ultrasound, bump, test results) and voice notes As above As above As above
Turning a voice note into text The iOS speech recognition service, which may send the recording to Apple servers; the text is saved on the iPhone Apple, under Apple's rules. Not us On Apple's side under Apple's policy; the text like other entries
Blood pressure and pulse from Apple Health Apple Health and the journal in the app You and Apple Health. Not us Until you delete them in the Health app and in mama.how
Technical entries for the profile limit (random profile id, date of the last birth date change, profile swap flag) iPhone and iCloud (key-value storage of your Apple ID) You and Apple. Not us Stay in iCloud after uninstalling; "Delete all data" clears them
Calendar for two: day colours, name, sign of the day Your iPhone and your partner's iPhone, sent without our server You and your partner. Not us On the partner's phone until the end of the expected period range or until you end sharing
Subscription plan and signed proof of purchase Apple; on the iPhone the app remembers the plan Apple as the controller of payments. Us only during Premium pairing Under Apple's rules
Premium pairing: session id, challenge, proof of purchase, IP address Memory of the mama.how server; Cloudflare also sees the IP address Us Session at most 5 minutes; token in your browser at most 7 days
Reminders Local notifications scheduled on the iPhone You Until you turn the reminder off

Where your data lives

Everything you enter or add is stored locally on the device, in the app's data. The app does not sync entries between devices and does not use a cloud database (CloudKit).

If iCloud Backup is on for your iPhone, the app's data is part of it, like the data of any other app. The backup belongs to your Apple ID; we have neither technical nor legal access to it. You turn backups on and off in iOS settings. iCloud is governed by Apple, as described in Apple's privacy policy. How Apple encrypts the backup is described in the Encryption part.

So that the free plan's limit on child profiles cannot be bypassed by deleting a profile or reinstalling, the app stores a few technical entries on the phone and in your iCloud (key-value storage tied to your Apple ID): a random child profile id created by the app, the date of the last change of the birth date in that profile, and a flag saying whether you have used the profile swap. They contain no child's name and no journal content, and they never reach us. They stay in your iCloud after you uninstall the app.

Reading text from photos of test results (OCR) runs on the device, through Apple's Vision framework; photos are not sent anywhere for this. PDF exports (pregnancy card, birth plan, charts, entries) are created on the device and handed to the iOS share sheet. You decide whether to save the file, send it to your midwife or print it. We are not in the middle and keep no copy.

Apple Health

With your permission, given in the iOS system dialog, the app can read from Apple Health systolic and diastolic blood pressure and heart rate, to show them in the pregnancy journal, and write to Apple Health the blood pressure readings, and the pulse if you enter it, that you add in the app. Readings stay on the device. Apple Health data is never sent to us or anyone else, never used for advertising or marketing and never sold. You can revoke access any time in the Health app (Sharing, Apps).

Permissions the app asks for

Every permission is optional, we ask only when you first use the feature, and saying no blocks only that one feature.

  • Camera. Bump and ultrasound photos, photos of test results for OCR, scanning the Premium pairing QR code and the Calendar for two code.
  • Photo library. Adding existing photos and saving what you export from the app.
  • Microphone. Voice notes for the journal.
  • Speech recognition. Turning a voice note into text through the iOS system service (details below, under network connections).
  • Apple Health. Reading and writing blood pressure and pulse, as described above.
  • Face ID or device passcode. Confirming it is you before you open the Calendar for two settings. iOS performs the check; the app only receives yes or no, with no biometric data.
  • Notifications. Local notifications only, scheduled by the app on your device (reminders for tests, vaccinations, entries, medicines and memories). We have no push server and send no marketing notifications.

Whatever is created with these permissions stays on the device (and in your iCloud Backup, if you have one), exactly like the rest of your entries.

Purchases: Apple is the controller

You buy the Solo or Family subscription in the App Store. Payment, free trial, renewal, cancellation, refunds and the receipt are handled entirely by Apple. Apple is the controller of payment and purchase data; see Apple's privacy policy.

The app learns from iOS whether a subscription is active and which plan it is, and receives a proof of purchase signed by Apple. It remembers the plan on the device. The proof of purchase reaches us only when you pair Premium with a QR code yourself, as described below. We never receive your name, address, card number or Apple ID.

Premium pairing with a QR code

You unlock the Premium area on the mama.how website by scanning a QR code shown on the website with the app. This happens only when you scan the code yourself. The code holds a mama.how address with two random values generated by our server: a pairing session id and a single-use challenge.

What the app sends. After the scan, the app sends the mama.how server, over HTTPS, exactly three fields: the session id, the challenge and the proof of purchase signed by Apple for the active subscription (a StoreKit 2 transaction in JWS format). The proof is passed on exactly as iOS issued it; the app adds nothing to it. It sends no entries, photos, child data, name or Apple ID. If there is no active subscription on the phone, the app sends nothing.

What is in the proof of purchase. Apple prepares and signs the proof of purchase. It contains, among other things: the transaction id (transactionId), the original transaction id (originalTransactionId), the subscription order line id (webOrderLineItemId), the app id (bundleId), the product id, that is the plan and billing period (productId), the subscription group id, the dates of purchase, original purchase, expiry and signing, the purchase type and transaction reason (purchase or renewal), whether the purchase is yours or shared through Family Sharing, the App Store country (storefront) and its id, the price and currency, the environment (production or test), a device verification value that Apple lets developers use to check whether the transaction belongs to a given device, and, where it applies to your subscription, details of a promotional offer or a revocation. Apple certificates that confirm the signature are attached. The proof contains no name, e-mail address, Apple ID or card data. The originalTransactionId stays the same across renewals; on its own it does not point to a person, but it lets successive pairings be linked to the same subscription, so we treat it as personal data.

What the server does. It checks Apple's signature and certificate chain and reads only these items from the proof: the signing date, the environment, the app id, the product id, the expiry date, any revocation date and the originalTransactionId. From these it works out the plan (Solo or Family) and whether the subscription is valid. The server does not read the other fields. We do not store the proof of purchase on disk, in a database or in logs; after the check it is not kept.

How long. The pairing session lives only in the server's memory, for at most 5 minutes. After a successful check the session holds the plan, the originalTransactionId and the subscription expiry date, and once the browser picks up the result the session is deleted. Expired sessions are removed every minute, and a server restart wipes them all. The browser receives a premium cookie with a token signed by us that holds the plan, the originalTransactionId and its validity: until the subscription ends, but no longer than 7 days. The token lives only in your browser; the server does not store it and checks its signature when you enter the Premium area.

Logs. The server writes only the outcome of pairing to its technical log: the session id and the plan, or an error code. No IP address, no proof of purchase and no originalTransactionId. The log has a size limit and the oldest entries are overwritten. Web server access logs are switched off for the pairing addresses and the Premium area. The server keeps the IP address only in memory to limit attempts per minute and forgets it after a few minutes. As with every connection to the website, Cloudflare also sees the IP address (part 4).

Legal basis: Art. 6(1)(b) GDPR, providing the service you ask for: checking your plan and opening the Premium area on the website. Pairing is optional; the app works the same without it, you just cannot open the Premium area in the browser.

Calendar for two

On the Family plan, while trying for a baby, you can show your partner a calendar of coloured days on their iPhone. Your partner installs mama.how and chooses the partner role; they need no account and no subscription.

What leaves your phone. Your phone itself works out a short list from your entries: date ranges and the kind of day (period logged in the current cycle, expected period, and in the "Trying" mode the estimated fertile window and, if you turn it on, the waiting time). Plus the name you choose and, if you want, a sign of the day picked from a few ready ones. You choose what to show. Never sent: temperature, cervical mucus, ovulation and pregnancy tests, intercourse, symptoms and mood, notes, supplements, test results, the cycle day number, cycle lengths, the estimated ovulation day or any information about a late period.

How it travels. Without our server and without iCloud. The invitation is a QR code shown on your screen, which your partner scans in their app. Later updates and the code that ends sharing can be shown as a QR code or sent as a file through AirDrop or the iOS share sheet. If you send the file through a service of your choice, such as a messenger, it passes through that service, but it is encrypted and cannot be read without the key from the invitation. We have no access to this data at any point.

Encryption. Each invitation creates new keys. The content is encrypted with AES-256-GCM and signed with an Ed25519 digital signature. The signing key stays only on your phone; your partner's phone receives the decryption key and the public key in the invitation, so it can read and verify your updates but cannot forge them. The partner's app rejects files that were altered, forged or are older than the last one received.

Where and how long. Your phone holds the sharing settings and keys, your partner's phone holds the last calendar received and the keys; both in the app's data, so also in the iCloud Backup if it is on. The calendar disappears from your partner's phone after the end of the expected period range. You can pause or end sharing at any time; the ending code clears the view on your partner's phone. What your partner has already seen cannot be undone. You open the sharing settings after confirming with Face ID or the device passcode.

We decide in the app what kind of information can be shared and how much, but the transfer itself happens between your phone and your partner's phone, at your decision; we do not receive or store this data.

Network connections made by the app

The app connects to the network only in these cases:

  • Premium pairing with a QR code, described above. This is the only connection to our server.
  • Speech recognition. When you turn a voice note into text, the app uses the iOS speech recognition service. We do not force on-device-only mode, so iOS may send the recording to Apple servers to recognise it. This is governed by Apple's privacy policy; we never receive the recordings or transcripts. If you do not want this, do not grant the speech recognition permission; voice notes keep working, without transcription.
  • PDF fonts, only as a fallback. The Inter font is built into the app. If it could not be loaded from the app during a PDF export, the app would try to download it from Google Fonts servers (Google LLC, USA). Google then sees the device's IP address and which font file is requested; none of your entries go there.

Apart from that the app does not connect to the network, except for iOS system services such as the App Store, iCloud and AirDrop, and links you open yourself.

Deleting your data

  • In the app. You delete single entries, photos and recordings where you added them. You delete a child profile in Settings; it goes to the Bin, where you can restore it for 30 days, after which it is gone for good. Settings also has Delete all data, which wipes the app's content on the device, including the Calendar for two, and the technical profile limit entries in iCloud for the profiles that are in the app at the time of deletion.
  • Uninstalling. Deleting the app removes local data from the device.
  • iCloud. The iCloud Backup belongs to you and you clear it on your side: iOS Settings, Apple ID, iCloud, Manage Storage.
  • Apple Health. Readings previously saved to Apple Health are deleted in the Health app.
  • Partner. The calendar on your partner's phone is removed by the code that ends sharing or when the calendar expires; your partner can also delete the data in their app.

You do not need to ask us, and we could not undo it, because we have no copy.

3. Encryption and security

  • Connections to the website and the server. The mama.how website and the Premium pairing connection use HTTPS, an encrypted connection. Traffic passes through Cloudflare (part 4), which as an intermediary handles that connection on its servers.
  • Calendar for two. AES-256-GCM and Ed25519 signatures, new keys for every invitation, no server of ours, as described above.
  • Data on the iPhone. The app's data sits in its iOS sandbox, which other apps cannot reach, and is covered by iOS Data Protection, which works when you have a passcode set.
  • iCloud Backup. Apple encrypts the backup, and the level of protection depends on your Apple settings. With standard data protection, Apple holds the keys to the backup. If you turn on Advanced Data Protection, iCloud Backup is end-to-end encrypted and the keys are only on your trusted devices. Apple describes the details in its iCloud data security overview. We have no influence on these settings and no access to the backup.
  • Premium token. The premium cookie is signed by our server, so it cannot be forged, and is not readable by page scripts (HttpOnly). It is not encrypted; it holds only the plan, the originalTransactionId and its validity.
  • Newsletter. The confirmation and unsubscribe links carry the e-mail address in encrypted form.

4. The mama.how website

The site needs no account. Calculators, the week atlas, tests and quizzes run in your browser; results are never sent to us or stored on our side.

Resources loaded from third-party servers

We serve the site's fonts and scripts from our own server. The only exception is the Cloudflare mechanism below; Cloudflare then sees your IP address, browser headers (including the user agent) and the page address:

  • Cloudflare network error reports. Cloudflare adds Network Error Logging headers (NEL and Report-To) to the site's responses. Browsers that support them remember a reporting rule for 7 days and, if a connection to mama.how fails, send Cloudflare (a.nel.cloudflare.com) a short technical report: page address, error type and time. Successful visits are not reported.

We do this so outages can be detected; the legal basis is our legitimate interest, Art. 6(1)(f) GDPR. We pass no other data to Cloudflare and do not use them for tracking or advertising.

Hosting and server logs

The site is hosted on a server of Hetzner Online GmbH (Germany), located in a data centre in Helsinki, Finland, in the European Union. In front of the server sits Cloudflare, Inc. (USA) as reverse proxy, DNS and attack protection; Cloudflare is certified under the EU-US Data Privacy Framework. Cloudflare sees traffic to the site (IP address, browser headers, page address) and keeps its own aggregated edge counters (request counts, countries, status codes), which we read in its dashboard. There are no individual people in it, no tracking script on the site and no profiling. How long Cloudflare keeps traffic data is set out in its privacy policy.

The server keeps standard access logs (IP address, user agent, path, response code, timestamp), except for the Premium pairing addresses and the Premium area, where access logs are switched off. Application logs do not record IP addresses. Logs rotate daily and are deleted after 15 days at the latest; they are used only to keep the site running and spot abuse. The legal basis is our legitimate interest, Art. 6(1)(f) GDPR: keeping the site up and defending against abuse.

Cookies

We have no analytics and no ads, so there are no analytics or marketing cookies. There is also no consent banner, because there is no consent to collect.

The site sets no language cookies: the address decides the language version (Polish at mama.how, English at mama.how/en/). We set only two functional cookies, and only during Premium pairing:

  • qr_sess: a random key that binds the QR code to the browser that showed it. Valid for up to 5 minutes, sent only to the address that checks the pairing status, removed when pairing ends.
  • premium: the Premium area token described in part 2. Valid until the subscription ends, but no longer than 7 days.

If your browser still holds locale or region cookies from earlier visits, the site no longer uses them; you can delete them in your browser settings.

The site stores nothing permanent in your browser's localStorage or sessionStorage. The only exception is a dismissed translation banner in language versions that are not fully translated yet; that entry never leaves your browser and you can delete it in its settings.

The Premium area on the website

Premium on the website is opened by the QR pairing token described in part 2. The website area is unlocked by every paid plan (Solo and Family). The token holds the plan, the originalTransactionId and its validity, with no name, e-mail address or Apple ID; when it expires you pair again.

Newsletter and unsubscribing

The "Pregnancy weekly" newsletter is a free series of up to 40 educational e-mails about pregnancy, without advertising or commercial content. The first e-mail arrives within a day of confirming, the next ones every 7 days, in the same order for everyone; after the 40th e-mail the series ends. Signing up is optional and uses double opt-in: after you send the form you get an e-mail with a link valid for 2 days, and the link opens a page with a "Confirm sign-up" button. Only clicking that button puts the address on the list; without confirmation we send nothing more.

What data: your e-mail address, the name of the place on the site the sign-up came from (e.g. "atlas", without a pregnancy week number) and, as proof of consent, the version of the consent text, the sign-up time and the confirmation time. To run the series we also store the language of the e-mails (Polish or English), the start day of the series (the day of confirmation) and the number of the last e-mail sent, so we know which one comes next. We do not collect the pregnancy week or a due date. We do not store the IP address as proof of consent and we do not pass it to Brevo; the mama.how server uses it only in memory to limit sign-ups per address per minute and forgets it after a few minutes. The newsletter is for anyone interested in pregnancy: future parents, family, people planning a child. We do not ask whether you are pregnant and store no such information; the series runs in the same order from the day of sign-up for everyone. So the sign-up is not data about your health and the newsletter does not process special categories of data (Art. 9 GDPR).

Who processes it: delivery is handled by Brevo (Sendinblue SAS, Paris, France, European Economic Area), our processor: it sends the e-mails and keeps the list and the data described above. We do not store the address in any database of our own: once a day the mama.how server reads the list from Brevo, sends the next e-mail of the series through Brevo and keeps nothing from that list. The confirmation and unsubscribe links carry the address in encrypted form. See the Brevo privacy policy and the terms including the data processing agreement (DPA).

No tracking, no profiling: open and click tracking in Brevo is switched off and the e-mails contain no tracking pixels. We do not build recipient profiles and do not segment the list by behaviour.

Legal basis: your consent, Art. 6(1)(a) GDPR. You can withdraw it at any time, without affecting the lawfulness of earlier sends.

How long: the trace of an unconfirmed sign-up (the confirmation e-mail in Brevo's sending logs) is deleted within 30 days at the latest. A confirmed address is kept until you withdraw consent and at the latest 3 months after the last e-mail of the series; after that it is deleted automatically. The proof of consent and the series data are stored with your address in Brevo and kept exactly as long as the address: they are deleted together with it, never later. The newsletter is for people aged 16 or over.

To stop receiving emails:

  1. Easiest: click "Unsubscribe with one click" at the bottom of any e-mail and confirm with the button, or use the unsubscribe button your e-mail program shows (e.g. Gmail). Sending stops at once, and the address, the proof of consent and the series data are removed from the Brevo list at the same moment.
  2. Or write to [email protected] with the subject "Unsubscribe". We act within a day.

E-mail correspondence

The [email protected] and [email protected] mailboxes (replies to the newsletter land in the latter) are run for us by Migadu (Migadu-Mail GmbH, Switzerland; Switzerland is covered by a European Commission adequacy decision). When you write to us, we process your address and your message to reply and settle the matter, based on our legitimate interest (Art. 6(1)(f) GDPR). We keep the correspondence until the matter is settled.

5. Your rights

In plain words: we do not have your app data, so there is nothing to hand over or correct. Your entries sit on your device and in your iCloud Backup, only you can reach them, and you correct and delete them yourself without asking us. Premium pairing data disappears from our server together with the session, after a few minutes, so after that we do not have it either. If you e-mail us, we keep that correspondence until the matter is settled, and then we do hold your address and your message; the same goes for an address signed up to the newsletter.

For that data you have the right of access, rectification, erasure, restriction of processing, objection, data portability and withdrawal of consent. We reply without undue delay and within one month at the latest. If you think we are doing something wrong, you can lodge a complaint with the President of the Polish Personal Data Protection Office (uodo.gov.pl) or, outside Poland, with the data protection authority of your country. Write to [email protected] and we will sort it out without forms.

Providing data is voluntary. Without an e-mail address you cannot sign up to the newsletter, and without a proof of purchase you cannot open the Premium area on the website; you use the app without giving us anything.

6. Age and children

The website, the app and the newsletter are intended for people aged 16 or over. The app is a tool for parents, and the parent is our user. We do not collect data directly from children. A child's data is entered by the parent and stays on the parent's device (and in their iCloud Backup, if they turned it on); we never see or store it.

7. Changes to this policy

If the product changes, we update this page and the date below. Material changes are announced on the site, and by email to newsletter subscribers. The Polish version is binding; translations are auxiliary.

Blazej Lewartowski, sole proprietorship, ul. Swieradowska 47, 02-662 Warszawa, Poland, NIP 5242414096, REGON 382843314 · [email protected] · Terms · Last updated: 2026-11-22.