My kid wanted a game. I did what every parent does: I opened the store listing and tried to work out, in about thirty seconds, whether it was safe to tap install. The privacy label told me the app "may collect" a category of data. That is not an answer; that is a shrug written in a smaller font.

I am an engineer, so the question I actually have is concrete. What does this app collect from a child? Does it include identifiers used for ad tracking? Is there any parental control, or an age gate that means anything? Is the content even age-appropriate? The store label is self-reported by the developer and too coarse to separate "collects a crash log" from "collects location and an advertising ID". COPPA and GDPR-K set expectations around children's data, but a parent standing in a shop aisle is not going to read a regulation. They want a readable view they can act on.

The thirty-second problem

I started keeping notes. For each app I looked at, I wrote down the data it asked for, whether ads appeared, whether there was a way to limit anything, and whether I could find a plain statement about kids. It was slow, and worse, it was inconsistent: some evenings I checked four things, some evenings one, depending on how tired I was. A checklist I apply inconsistently is barely better than no checklist.

What I wanted was a fixed set of questions applied the same way every time, ending in something short enough to read on a phone. Not a score that pretends to be a legal ruling, just a consistent read plus the concrete next action: install, adjust a setting first, or skip it.

The other thing I noticed is that "safe" is not one dimension. An app can be age-appropriate and still collect more than it needs. Another can be thin on data but have no parental controls at all. Collapsing that into one green light would be dishonest, so I kept the outputs as separate signals.

What I built

I built KidPrivacy as a decision-support view for parents and schools. It scans children's apps and games for COPPA and GDPR-K compliance signals, excessive data collection, and ad tracking. The declared features are: flag apps that collect kids' data unsafely, check age-appropriate use and parental controls, give a family privacy score, and hand back a simple parent action checklist. That is the whole set. It does not monitor an installed app, does not verify a developer's filing, and does not certify compliance.

The checklist is the output I care about. A score on its own is a number you argue with; a checklist is a thing you do - turn off this setting, read this disclosure, ask the school this question. The score is a summary of the signals, not a grade from a regulator.

I kept the "family privacy score" deliberately modest. It reflects what the available signals say, not what an audit would find. If an app's data practices are not visible from the outside, the honest result is a thin read, and I would rather show that than invent certainty.

The limits, stated plainly

This is decision-support, not a certification, not legal advice, and not a live audit. It does not observe an app at runtime, does not confirm that a developer's disclosure is accurate, and does not determine compliance with COPPA, GDPR-K, or any other law. A "family privacy score" is a heuristic over available information, not a compliance finding. If you need a legal determination, that belongs with someone who can review the app's actual behaviour and the current rules.

I am also careful about the inputs. A pre-install read is limited to what is published about an app before installation. That is genuinely useful for the thirty-second decision, and genuinely incomplete for everything after it. Treating it as a one-time guarantee would be a mistake.

If you have ever squinted at a privacy label and wished someone had already asked the boring questions, KidPrivacy gives you a consistent starting read and a checklist. If there is a signal you think it misses, that is a gap and I would like to hear about it.

FAQ

What does KidPrivacy produce?

A view of a children's app: unsafe data-collection flags, an age-appropriate and parental-control check, a family privacy score, and a parent action checklist. You look an app up in KidPrivacy and get the read back.

Does it certify that an app complies with COPPA or GDPR-K?

No. It does not observe the app at runtime or verify a developer's filing. It surfaces signals; a compliance determination belongs with someone who can review actual behaviour.

Is the family privacy score a legal finding?

No. It is a heuristic summary of available signals, not a compliance ruling or legal advice.

Does it keep watching after install?

No. It is a pre-install decision-support read. It does not monitor an installed app, so it is not a live audit.