SweetWonder
Articles & tips

Privacy Policy

SweetWonder ·

The short version: your records are kept so they can reach your other devices and the people you share a baby with. Nothing is sold, nothing is advertised against, and there is no analytics or tracking of any kind in the app. Milestone photos never leave your device.

Who is responsible

SweetWonder is made by Martin Donchev, in Bulgaria, who is the data controller for the purposes of the UK and EU GDPR. For anything in this policy, write to [email protected].

What is stored

Your account

When you create an account we store your email address, an account identifier, and your display name if your sign-in provider supplies one. You can sign in with an email and password, with Google, or with Apple. Sign-in itself is handled by Firebase Authentication; we never see or store your password.

What you record in the app

  • Your baby’s name, sex and date of birth
  • Sleep, feeds, nappies, awake time and temperature entries
  • Growth measurements, milestones, medicines, vaccinations and supply counts
  • Your sleep plan, appointments and reminder settings
  • Pregnancy details you enter: due date, antenatal visits, contractions, your own weight and blood pressure, hospital bag and birth plan lists
  • Pumping sessions and your milk stash
  • Your own mood check-ins

Some of this is health information about you and about your child. It is stored because storing it is the entire purpose of the app, and it is treated as data you have explicitly asked us to keep on your behalf.

What stays on your device

Milestone photos stay on the device where you add them. They are not included in diary synchronisation. Reminders use local scheduling and, where enabled, server push delivery as described below.

What is not collected

We do not use advertising identifiers, advertising profiles, location tracking or your contacts. Technical request and delivery records are processed to operate synchronisation, security, subscriptions and notifications; these are not advertising analytics.

Health data from Health Connect on Android

What we access

If you choose to connect Health Connect, SweetWonder requests read access to your step counts, sleep sessions and sleep stages, and heart-rate readings. We also read the associated dates, times and source app identifiers to show when the readings were recorded and where they came from. These are the adult user's health and fitness data, not the baby's records. They are separate from the health information you enter manually.

Why we access it and your permission

We use these readings to show your own daily steps and sleep totals for the recent seven-day overview, and your latest available heart rate with its time and source, in the personal health section. Access is optional and starts only after you grant the relevant permissions in Android's Health Connect permission screen. Only the data types you allow can be read. This integration reads existing records; it does not measure your health, write to Health Connect or request background health access.

Processing, storage and sharing

Health Connect readings are processed locally on your Android phone and held temporarily in memory for the health screen. SweetWonder clears that in-memory display when the screen stops or the signed-in account changes. These readings are not saved in the app's local database, uploaded to our servers or Supabase, sent to OpenAI, or shared with another caregiver. They are not used for advertising, tracking or sale. The account retention and cloud deletion periods elsewhere in this policy concern your saved, synced records, not these temporary Health Connect readings.

Turning off access and deleting data

You can refuse individual permissions or revoke SweetWonder's access at any time in Health Connect's app permissions. Without access, the corresponding readings are unavailable, but you can continue using the diary's manual entries. To delete the original health records, use Health Connect or the app that created them. Leaving SweetWonder, revoking access or deleting your SweetWonder account does not delete those original records. Contact [email protected] with questions about this processing.

Apple Health on iPhone

With your permission, SweetWonder reads your own steps, sleep sessions and stages, heart rate, dates and sources from Apple Health for the personal-health overview. It does not write these readings back. You can separately enable cloud synchronisation of daily summaries through Supabase to your account, and separately allow a summary on your paired Apple Watch. An optional AI summary sends the displayed health context, including relevant manually entered wellbeing records, to OpenAI only after confirmation. These readings are not shared through the baby's family diary. You can revoke Health permissions, stop cloud uploads or erase the cloud copy from the personal-health controls. Revoking access does not delete the original Apple Health records.

Where it goes

We use a small number of processors, and nobody else:

  • Firebase Authentication (Google) — sign-in and identity only. It does not receive any of your baby or pregnancy records.
  • Supabase — the database and server functions that hold your synced records and make sharing between caregivers work.
  • OpenAI — The AI assistant, Voice entry.
  • Firebase Cloud Messaging / Apple Push Notification service (APNs) — Reminders and push notifications.

These providers operate outside Bulgaria, including in the United States, so your data is transferred internationally. Those transfers rely on the standard contractual clauses each provider offers.

Reminders and push notifications

If enabled, Supabase stores a device installation identifier, Firebase Cloud Messaging (FCM) token, account link, platform, language, time zone and notification preferences. Our server uses synced diary records to calculate reminders and sends them through FCM; iOS delivery also uses Apple Push Notification service (APNs). The payload may include the baby's name, reminder time and medicine name. Consultation notifications carry request identifiers and a general status message. Content may appear on the lock screen according to your device settings. Change permissions and reminder preferences in the app and device settings; sign-out disables that installation's delivery.

The AI assistant

When you request an AI reply or summary, the relevant profile, diary entries and your question are sent through our server to OpenAI's API. Voice entry and optional personal-health summaries have the separate processing described below. These requests are triggered by those features; ordinary diary entry does not send every record to OpenAI.

Please do not type anything into the chat you would not want processed this way. The assistant produces general information and is not a clinician.

Voice entry

When you choose to record a voice entry, the audio is sent through our server to OpenAI for transcription. The resulting text is processed to suggest a diary entry for you to review. Recording is not continuous background listening. The recording may contain personal information you speak; use manual entry if you do not want this processing.

Sharing a baby

When you invite another caregiver, they can see and add to the records for the baby you shared — the daily entries, the supply count and the sleep plan. Your own pregnancy records, your weight and blood pressure, and your mood check-ins are not shared with them; those stay on your account. You can see who has access, and remove them, in the app’s settings.

Sleep consultations

If you request a consultation, we store the request, your contact details, messages, questionnaire answers and service dates. The consultant can access the information you submit and the child's diary and development information you explicitly share. This does not share your separate personal-health diary. Avoid including information that is unnecessary for the consultation.

How long it is kept

Your saved records are kept while your account exists. In the current app, Settings → Delete account requests server-side erasure before removing local records and the sign-in identity. A separate email is not required after successful in-app deletion. See account and data deletion for shared records, retained technical records and the email alternative.

Your rights

Under the GDPR you may ask for a copy of your data, ask for it to be corrected or deleted, object to or restrict how it is used, and ask for it in a portable form. Most of this you can do yourself in the app — you can edit or delete any entry, export reports, and delete your account outright. For anything else, write to [email protected] and we will answer within one month. You also have the right to complain to your national data protection authority; in Bulgaria that is the Commission for Personal Data Protection.

Children

SweetWonder is for parents and caregivers, not for children, and accounts are held by adults. The records are about a child, but they are entered and controlled by you.

Security

Data in transit is encrypted. Records on the server are reachable only through a server function that checks who is asking, and the database itself is not open to the public internet. No system is perfect, and we do not claim otherwise.

Changes

If this policy changes in a way that matters, the date at the top changes with it, and we will say so in the app. Continuing to use SweetWonder after that means the updated policy applies.

Website download statistics

When you open an App Store or Google Play link on this website, a redirect records a daily aggregate total by UTC date, store, website language and source page. We store these totals in a Cloudflare D1 database in the European Union to understand which pages lead visitors to the app stores. We retain aggregate totals to compare results over time; they count link requests, not unique visitors.

These counters do not store IP addresses, user agents, cookies, visitor identifiers or full referrer URLs. They are not used for advertising or profiling and do not measure activity inside the app. Cloudflare processes the technical connection data needed to serve the website and its redirects; this is separate from the aggregate counters.