Last updated: 6 October 2026
Anka is a baby tracker. You write down feeds, sleeps, diaper changes, measurements and moments, and share them with whoever is helping you.
This policy explains what happens to what you write down. It is deliberately short and in plain English, because a policy nobody reads protects nobody.
Anka is a Mandala Tech product, built by Pratima, who founded the company and who wrote this app because she is a mom and knew what was missing.
Mandala Tech is the data controller.
If you need a postal address for a formal request, ask at this address and it will be given.
Only if you turn backup on:
| What | Why |
|---|---|
| Your baby's name, birth date and sex | To show the right name, work out age, and pick the right WHO growth chart |
| Feeds, sleeps, diaper changes | The point of the app |
| Growth measurements | To plot against the WHO growth standards |
| Pumping sessions and stash counts | So you can see what you pumped and roughly what is left in the freezer |
| Milestones and any notes you write | Because you asked Anka to remember them |
| Your email address | To sign you in and to identify your account |
| Your settings, such as units and theme | So the app looks the same on your other phone |
| Who you have invited and their role | So the right people see the right things |
Never, even with backup on: your cycle and your pregnancies. If you track them, your period days, pain, mood, notes, due dates, appointments and any earlier pregnancies stay on your phone only. They are not sent to the servers, not shared with anyone in your family, and not counted in the usage numbers or crash reports. They have their own export, in a file apart from the baby's. Deleting the app, or Delete everything, removes them from the phone.
Your phone's own backup is separate from Anka's. On an iPhone, Anka's data is left out of iCloud Backup and of backups made on a computer. On Android, Google's backup of the phone can copy them along with the rest of Anka's data. That copy is held by Google under your account, not by me, and it goes when that backup is replaced or deleted.
If you send feedback, Anka stores what you wrote, your email if you chose to give one, and roughly how old your baby is. That is it. You can leave it anonymous.
Anka never asks for your contacts, your location, your photos, your phone number, or your payment details.
Feeds, sleeps and growth measurements are information about a child's health. Pumping is information about yours, and so are your cycle and any pregnancy, which is why Anka never sends those anywhere. Some laws treat both as a special category needing extra care. Anka's legal basis for holding it is your consent, given when you turn backup on. Withdraw it by deleting your data, which the app does in one step.
Anka is for parents and carers, who are adults. It is not designed for or directed at children, and children do not have accounts. The data is about a child but is entered and controlled by their parent.
Only the people you invite, and the person who runs Anka.
This used to read differently, and the honest thing is to say so. Until the support window existed I could read any family's logs at any time, because I run the servers, and this policy said that in plain words. It is now the server that refuses me, not a promise I make. The check happens on every single read, so a shut window is not something I have to remember to respect.
No one else. Anka has no advertisers and no data partners.
Anka counts how many people use it, which screens get opened, and roughly how long a visit lasts. That goes to Aptabase, on a pipeline that never touches your logs. Anka uses Aptabase's EU-hosted service in Germany for app-usage analytics.
Every event it can send is declared in one file in the source, `lib/analytics-events.ts`. A property can only be a value from a fixed list, a whole number, a duration bucket, or a yes or no. Anything else is dropped before it leaves your phone. What that rules out:
So I can see that the Patterns screen was opened 40 times yesterday. I cannot see that you opened it, and I cannot see what it told you.
Aptabase was chosen over Google Analytics for Firebase on purpose. The Google one is next door to an advertising business, and using it would put "shares data with third parties" in Anka's Play Store data safety form. Aptabase uses no advertising id and does not follow you between apps.
Crash reports go to Sentry, which is a third pipeline again. A crash report carries the line of code that failed. It never carries a log, a note, or anything you typed.
On Google Firebase, in europe-west6 (Zurich, Switzerland). If you are outside Switzerland, your data is transferred there under Google Cloud's standard contractual clauses.
Invitation and deletion requests run on AWS in Mumbai, India (ap-south-1). A queued deletion has a temporary job record containing account and family identifiers and the deletion scope. It contains no log contents or note text. The queue carries only a job identifier. Firebase also holds the temporary deletion instructions so an interrupted request can continue safely.
Your saved logs stay until you delete them. There is no automatic expiry. Deletion removes the records from Firebase and from this phone. Anka keeps no backup of the deleted logs.
A server deletion can continue after you close the app. The temporary job instructions remain until deletion finishes so an interrupted job can be retried. Once it finishes, those instructions are removed. A completion receipt remains usable for seven days so the app can confirm the result. It then expires and is scheduled for automatic removal. AWS may take longer to physically remove expired items. Queue messages contain only a job identifier and expire within 14 days if not removed sooner.
Firebase keeps a small deletion marker for each erased account or child. A marker contains the old identifier and a deletion flag. It has no contact details or log contents. These markers have no automatic expiry: they stop an old phone from uploading deleted records when it reconnects.
Wherever you live, and specifically under UK and EU GDPR, you can:
You can do this in the app. If you cannot use the app, email dev@mandalatech.io from your account email address with the subject Delete my Anka account. I verify account ownership and the scope of the request before deleting anything. Never send passwords or sign-in codes. You can also request removal of particular records without closing the account. The account deletion instructions explain what is removed and what remains. We cannot remotely erase offline-only logs or previously exported files on another person's device.
Anka is a small app run by one person. It is built carefully, but no service can promise perfect security, and this policy does not.
If this policy changes in a way that affects what happens to your data, the app will tell you. Quietly widening who can see your logs would defeat the point of writing this down.
Anka records what happened. It does not tell you how much to feed, how long a baby should sleep, or whether growth is on track. It only knows what someone remembered to write down, so treat its totals as a rough picture, not a medical record. Ask your health visitor, midwife or doctor.