The app your child uses has no analytics in it. No advertising, no crash reporting, no push notification service. Nothing in it reports what they do to anybody.
That is an unusual thing to be able to say, so it is worth explaining what it means and how you can check it rather than taking my word for it.
What is actually in there
The kid app is built from 27 outside libraries. None of them is an analytics, advertising, crash reporting or push notification service.
Those four categories are how a typical app leaks. Not through anything sinister: a developer adds a crash reporter because crashes are hard to debug blind, and an analytics library because it is the default in every tutorial. Each one opens a connection to a company you have never heard of, carrying whatever it was configured to carry.
This is not a promise that we will not sell your child's data. There is no third party collecting it in the first place.
The part that changed
Until this week, that was a fact about the app rather than a rule the app had to keep. I knew it was true because I had looked. Nothing stopped a future version of me adding a library on a Tuesday and forgetting what I had written here.
So it is now checked by the thing that builds the app. Before the kid app can be published, a script reads the full list of everything the app depends on, including everything those things depend on in turn, and compares all of it against a list of known trackers.
Run right now, it reports:
no-trackers: ok. 492 packages checked, none on the denylist.
If a tracker is ever added, deliberately or by something else pulling it in, that check fails and the app does not build. Not a warning in a log somebody reads later. The release stops.
Why I would rather not be able to change my mind
There is a structural reason this is unlikely to reverse, beyond me deciding to be good.
The way Achievabee asks for your permission before collecting anything about a child is only available to a service that keeps children's information to itself. Adding tracking would not be a switch to flip. It would break the thing underneath, and I would have to change how consent works to accommodate it.
That is a much better guarantee than my intentions, because it does not depend on my mood in a year.
Checking it yourself
You cannot read my build logs, which is a fair objection to everything above.
What you can do is watch the app. An app that is reporting to somewhere has to talk to somewhere, and that traffic is visible to any network tool, including the ones built into a home router. The kid app talks to exactly one place, which is the service that stores your family's chores.
If you ever find it talking to anything else, tell me and I will explain or fix it. That is a genuinely checkable claim, which is the only kind worth making.