My Baby

Privacy Policy

Updated: November 7, 2026

In short: your data lives on our own server, there are no third-party analytics or ad SDKs, and nothing is sold or handed to advertisers. There are three exceptions: the Nana assistant, which processes a diary without names and only you can switch on (photos you attach yourself go as they are), voice transcription on those Android phones where the phone's own speech recognition does not work, and the handling of support requests, where a language model helps the developer.

Who is responsible for your data

This policy covers the My Baby and White Noise apps (Baby White Noise: Sleep Sounds in the stores) and this website. The personal data controller is Ilia Popov (Попов Илья Вячеславович), a private individual. Email contact@apexs.tech: write there with any question about your data or to withdraw consent.

What we store

Your account. Name, language, units and preferences. Telegram is linked only if you choose to, and only to invite a second adult — that adds a Telegram id and avatar.

App details. Platform, app version and the store it was installed from, as of your latest visit. The phone app also sends the phone model, the versions of the operating system and the built-in browser, and the build number. We use them to handle support requests, to look into failures on particular models and to know which builds are still in use. No advertising identifier is among them.

Your baby's records — everything you enter yourself: feedings, sleep, diapers, pumping and the milk stash, weight, height and head circumference, teeth, milestones, temperature, medicines and symptoms, solids, vaccinations, doctor visits, notes and photos.

Photos are stored encrypted, and only our server has the key. They are visible only to members of your space.

Purchases and subscription. The status of Family+ and Nana+ and how long the subscription runs. We learn about a purchase from the receipt Apple sends or from a notification of the website's payment provider (Paddle or lava.top). When paying with a Russian card on the website you enter an email: lava.top receives it for the receipt and subscription emails, and we keep it to link the payment to your account. The free week, gifts from the developer, promotions and the free Family+ connection we record ourselves: Apple knows nothing about them.

Sign-in email. If you link an email in settings, we keep the address so we can send you a code to sign in on a new phone. Before linking we send a six-digit code to the address, so we know the email is yours. We send no emails to it other than codes. The address is deleted together with the account; you can change it in settings.

App survey. After a week of keeping the diary the app asks once whether you like it. If you answer, we keep the score from 1 to 5, your comment if you wrote one, the app version, store, language and the number of diary days together with your account, so the developer can see what works and what gets in the way. If the diary is kept only on the phone, answering creates a messaging account, the same as the first message to the developer. The answer is deleted together with the account.

Where the diary is stored

Entries are stored on our server and on the phone itself: this way the app works offline, and the diary is not lost if the phone is lost or the app is deleted. An account is created automatically on first launch, with no email or password. If there is no connection on first launch, entries are kept only on the phone at first and move to the server as soon as there is a connection. Diaries that earlier versions of the app kept only on the phone move to the server after you read about it in the app and tap “OK”. Until then such a diary lives only in the phone's storage and we know nothing about it.

Earlier versions could keep an encrypted copy of such a diary with us if you turned it on in settings on iPhone. The copy is identified by a pair of random keys held by your phone and is not linked to a name, an email or Telegram. The encryption key is ours, so technically we are able to read the copy; we do not do that and we pass it to no one. You can switch the upload off in settings, and the copy already uploaded is then deleted from the server. It is also deleted when the diary moves to the server or you erase it on the phone.

What we don't do

Our apps for iPhone and Android run no behavioural analytics. They have no third-party analytics or ad SDKs; the only third-party libraries deliver notifications, talk to the watch and show the stores' own rating dialogs. Usage counters are kept only as daily totals that are not tied to a person or a device: how many times a day the app was opened, a payment screen was shown, Buy was tapped, what was chosen on the "I can't afford this right now" screen and how many seconds it took (rounded, up to a minute), a baby was added, the feeding-reference screen was opened and the assistant was asked from it, the clothing guide and its Home part for the room and sleep were opened, how many installs came back a day, a week or a month later, which store they came from, how many times the server turned a request down, why and in which app version, and which errors happened in the app itself: the error text with numbers and email addresses removed, the place in the code and the version. They contain no identifier, no address and nothing from the diary, so a number cannot be linked to you. The date of the first launch, used to count "came back a week later", stays on the phone. We do not sell your data, hand it to advertisers or use it for profiling.

Website visits. On lumobaby.com, mybabyfamily.com and mybaby.apexs.tech pages opened in a browser we count visits with our own analytics on our own server: which page is open, where you came from, the browser, system, screen size, language and an approximate location from the IP address (country, city). There are no cookies, the IP address is not stored, page addresses are recorded without parameters, visits on different days are not linked together, and nothing from the diary gets there. The iPhone and Android apps don't do this.

If you found the app through an Apple ad on the App Store, on first launch the iPhone issues a one-time token, and our server uses it to ask Apple which ad campaign and keyword the install came from. The server adds one to that campaign's daily counter, and on a purchase or a subscription renewal to the same campaign's purchase counter, together with the amount. So that renewals count toward the same campaign, its number is saved with the purchase record. The token is not stored, no tracking permission is needed, and the daily counters are not linked to you.

Request log

Separately from the counters, the server keeps a technical request log: time, IP address, request path, response code and duration, platform, app version and the store the app was installed from. A request path may contain internal ids of a baby or a record, or an invitation or transfer code. The log holds no email addresses, names, diary content, photos, sign-in tokens or phone model.

We need it to look into failures and support requests: it shows whether a request reached the server and what the server answered. We look at it only for that; it is not used for advertising or profiling. Log entries are erased within 30 days and are not included in backups.

Weather

We show the weather on the home screen only if you turn it on. The app then takes the phone's approximate location and, still on the phone, coarsens it to a cell of about 10 km. These coordinates go to our server, which asks WeatherAPI.com for current conditions and the Norwegian weather service MET Norway for forecasts and fallback data on its own behalf: your IP address is not passed to either service. We do not store the coordinates; rounded, they appear in the request log and are erased with it. You can turn the weather off in settings.

Shared access

A second adult joins by invitation code. They see the records in your space, each of you signs in separately, and you can see who recorded what. Access can be revoked at any time.

Nana assistant

Nana answers questions about your diary: how long the baby slept, when the last medicine was given, how weight changed, how much formula goes per day. On your request ("log 4 oz") it makes a diary entry — a feed, a sleep, a diaper — and an Undo button appears under the reply. It is a separate feature, off by default: until you switch it on yourself on the introduction screen, nothing described below happens.

What is sent. Your question, a few previous turns of the conversation and a snapshot of the diary without names. The snapshot holds the child's date of birth and sex, how many weeks before or after the due date the child was born, the phone's time zone and the enabled features. Sleep, feeds, diapers, pumping and mood go for the last 90 days. Weight, height and head circumference, temperature, medicines, symptoms and diagnoses, solids, vaccinations, doctor visits, milestones and teeth go for the whole time, lab tests with their values and the ranges printed on the form for the last six months. If that is not enough for an answer, Nana may ask the server for older diary entries too. What you typed in your own words (a symptom, a medicine name and dose, a reaction to a food or a vaccine, which doctor a visit was with) goes as written. If you added your own clothes in What to wear, their type and size go too, never their photos; if weather is on, so does today's clothing pick: temperature, precipitation and wind, without the place. Children's names are replaced with placeholders, also inside what you typed in your own words, and put back on your phone.

What is never sent to the model. Names from the diary, notes, diary photos, the parent's own mood, the members of your space. A photo you attach yourself (to a question, or a lab form) is sent with everything visible on it, including printed names.

Web search. For questions about baby food (what is in a formula, the age range, the price) Nana may look the answer up on the web. A search service then receives a short query the model writes from your question, without children's names and without the diary snapshot. Links to the pages found are shown under the answer. The search service follows its own retention rules; the processing terms below do not cover it.

A photo with your question. You may attach a photo to a question — a formula label, a page of the medical record, a rash on a cheek. It is sent together with the question to the same language model, and only by routes where the provider, under its own terms, does not keep the request. Such a photo does not go into the diary and is not kept by us — not on the server, not on the phone once the screen is closed. Attaching it is your choice each time; Nana still never takes photos from the diary.

A lab form from a photo. In the Labs section and in a conversation with Nana you can photograph your child's lab test form, and Nana fills in the record: the test, the date, the values, units and the ranges printed on the form. The form holds health information about your child, so this needs a separate consent: we ask for it before the first photo and record the time and the version of the text you saw. The full text of the consent names who processes the photo and where. Before sending you cover the top of the form, where the name, date of birth and record number usually are; check the bottom too, it may have signatures, stamps and a barcode. What stays visible is sent. The photo goes to a third-party language model outside our server, in the EU or the US, and only by routes where the provider, under its own terms, does not keep the request and does not learn from it. The model returns the numbers and does not return the name, record number, clinic or doctor. The record appears in the diary only after you check and save it. We keep the photo of the form only if you tick "Attach the photo of the form to the record", and then the cropped one.

You can withdraw the consent in the Labs section, after which lab forms are no longer sent to the model. Saved lab tests stay in the diary: you can delete a record by opening it in the Labs section, and the whole diary together with the account as described on the account deletion page.

How it is processed. Our server builds the snapshot; the answer is produced by a language model that receives it only for the duration of the answer. Under the processing terms the data is not used to train models; the model provider may keep the request for a limited time to protect against abuse. Lab forms go only by routes without storage, as described above. The model may run on infrastructure outside our server, including outside your country.

What we keep. Nana itself stores neither the question nor the answer on the server. On the phone the conversation stays while it lasts — no longer than an hour after the last message, so it survives the app being sent to the background — and is then erased; signing out erases it at once. Nana's last answer, together with its question, stays on the phone for one more day so you can read it again. The Remove button, Start a new conversation and signing out erase it at once. An answer you put into Cheat sheets yourself becomes an ordinary card of your family diary: members of your space can see it, and it is kept until you delete it. The server keeps only the fact of a call: the time, the access level, the conversation id and the names of the tools used (a record, a chart, a search) — no content — to count the conversation limit and to see what gets used.

Voice. Your speech is recognised on the device itself, by system means, and the recording never leaves the phone. The exception is an Android phone whose system speech recognition does not work (this happens on firmware without Google services). Then the recorded phrase goes through our server to a language model (OpenRouter, by a route without storage), which returns the text of the phrase, and the audio is kept neither by us nor by it. Nana's answer is read aloud by a speech synthesis service through our server: it receives only the text of the answer, without the question or the diary snapshot. The answer may contain the child's name and the diary figures you asked about: the name is put in on the phone, otherwise the voice would read out a placeholder. If the service is unavailable, the device's own voice reads the answer.

Switching off. Settings, “How we record”, “Nana assistant” — a switched-off toggle blocks sending on the server, not just the button.

Voice assistants

You can keep the diary by voice through a smart speaker with Alice or Alexa. It is a separate feature, and it stays off until you connect a speaker yourself. If you never connect one, nothing described below happens.

What is sent. The assistant reads out what you asked for: the baby's name, the time and amount of the last feed, when the baby fell asleep and woke up. We pass those values to the assistant's service so that it can say them. What comes back is the text of what you said to the speaker, and an entry in the diary is made from it. Photos and notes are never sent. If Nana is on and you ask the speaker something it cannot do by itself, Nana answers, and her answer also goes to the assistant's service so that it can say it. Such an answer may contain anything from the diary you asked about, including weight, height and health.

Sleep sounds. While a speaker is connected, we remember which sleep sound you played last, in the app or on the speaker, so that the speaker can play it when you ask for the last sound. We keep one row, it changes with every play and is erased when you disconnect the speaker. Sounds you recorded in the app are uploaded to Yandex Dialogs for that time, because otherwise the speaker cannot play them. Delete the sound or disconnect the speaker, and within an hour we delete the file at Yandex too.

Who receives it. Alice is made by Yandex, Alexa by Amazon. We do not build these assistants and do not run their servers. Recording your voice and recognising speech happens entirely on their side: the audio never reaches us, only the text does. What they do with the voice and the text is covered by their own privacy policies, not by this one.

Consent and withdrawal. Before the linking code is issued, the app shows a separate screen with this same list and asks for your permission. You can withdraw it in the same place: settings, "Smart speakers", "Disconnect the speaker" — the link is deleted and the assistant stops receiving entries.

Handling support requests

When answering support requests and looking into how the service works (for example, how many families use a feature or what someone wrote about a failure), the developer asks a language model. To answer, the model reads the rows of our database it needs: the account, diary entries, the conversation with support. It does not see sign-in codes, tokens, webhook addresses or copies of diaries kept without an account. The model here is Claude by Anthropic (US) under the developer's subscription; the fallback one works through the same intermediary as Nana. Under Anthropic's terms the conversation with the model may be kept by it for a limited time. Processing takes place outside our server, including outside your country. None of this is used for advertising or profiling.

Why we may process your data

The account and the diary are needed for the app to work for you: this is performance of our agreement with you. Your child's health information in the diary (temperature, medicines, symptoms, illnesses, vaccinations, doctor visits, lab tests): your consent as a parent. Nana and reading lab forms: your separate consent. Smart speakers and weather: consent, you switch them on yourself. Purchases: the agreement and the legal duty to keep payment records. The request log and fault analysis: our legitimate interest in a reliable and secure service.

For readers in the EU these are Articles 6(1)(a), (b), (c), (f) and 9(2)(a) GDPR. For Russia: Article 6 part 1 items 1, 5, 7 and Article 10 part 2 item 1 of Federal Law No. 152-FZ.

Consents and how to withdraw them

We ask for each consent on its own screen and record when you accepted it and which version of the text. Tapping the consent button in the app while signed in to your account counts as your simple electronic signature; the full text of each consent says so too. Withdrawal applies from then on.

Who else processes data and where

On our behalf and under data processing agreements:

Under their own rules, as independent recipients, data goes to Apple for App Store purchases, to the website payment operators Paddle and lava.top, to Yandex and Amazon if you connect a voice assistant, and to Telegram if you use it to invite the second adult or to write to us. WeatherAPI.com and MET Norway receive from our server only coarse coordinates, without the IP address or the account. We name the companies that process data on our behalf on request by email.

Deleting your data

You can delete your account inside the app: settings, "Delete account". Records and photos go with it. If a second parent shares the family, the space and its history pass to them.

How long we keep your data

For as long as the space is in use — indefinitely. If no member of a space has signed in for 24 months, we send a warning through the channels we have (a notification, a linked Telegram) and remind you to export your records from the app. If another 3 months pass with no sign-in after the warning, the space's accounts and data, including photos, are deleted. Any sign-in resets the clock.

Your rights

You can find out what data about you and your child we have, why we need it and who it was shared with; correct it; delete it as a whole or record by record; export it with "Data export" in settings; withdraw consent; object to processing based on legitimate interest. Write by email, in Telegram or through the form in the app's settings. We answer within 10 working days; if we need more, we extend by no more than 5 working days and tell you. We may ask you to confirm the account is yours.

If a data breach happens

We notify Roskomnadzor within 24 hours, the EU supervisory authority within 72 hours, and you right away if the risk to you is high.

Where to complain

Write to us first. You may also contact a supervisory authority: in Russia Roskomnadzor (rkn.gov.ru), in the EU the data protection authority of your country, in Kyrgyzstan the State Agency for Personal Data Protection under the Cabinet of Ministers.

The White Noise app

White Noise (Baby White Noise: Sleep Sounds in the stores) is a separate app by the same developer: sleep sounds, a timer, a night light and widgets. It has no diary and asks nothing about your baby.

Without an account. You can listen without signing in or signing up. The app then only sends our server requests for the sound shelf and crash reports that are not tied to anyone. The requests go into the request log as described above.

Device account. When you heart a sound, suggest your own sound for the shared shelf, request a sound or report a parent's sound, the app quietly creates an anonymous account with no name, email or password. It keeps the app language, your hearts, your sounds and your messages to the developer, plus the app information described above.

Your own sounds. The microphone is on only while you record your own sound. A recording or file you add before there is an account stays on the phone until you suggest it for the shelf. With an account your sounds are stored on our server, and only you can hear them. We listen to every suggested sound before anyone else can. An accepted sound goes into the shared library as a separate copy that is not linked to your account; a rejected one stays yours only.

Requests and reports reach the developer as support requests and are handled as described under "Handling support requests".

Deletion. Settings, "Delete account": the option appears once the account exists. Your sounds on the server, hearts, suggestions and messages to the developer are deleted with it. An accepted copy on the shelf stays; write to us and we will take it down. If the app is not used for 27 months, the account is deleted on its own, as described under "How long we keep your data".

White Noise has no ads, no tracking and no purchases.

Children

The app is used by parents. The records are about a child, but the child is not a user, and we do not collect data directly from children.

Medical note

This is a diary of observations, not a medical app. Vaccination timing, exemptions and any health question are the doctor's call.

Contact

Questions and data deletion — contact@apexs.tech, Telegram https://t.me/MyBabyApexsBot, or the feedback form in the app's settings.