Most app listings sound similar. This checklist helps parents verify what actually protects children, not just what marketing claims.
These five are not a scorecard to be averaged against other features. If any one of them fails, the app is not a children's app, regardless of how good the content is. Work through them before you install, using the store listing, the website, and the privacy policy, all of which you can read without handing over an account.
Privacy, terms, and child safety pages must be easy to find and read. Not buried, not a single combined document, and not written to be technically compliant while meaning nothing. If you cannot find the child safety page from the homepage, that is the finding.
You should be able to set age filters and session limits quickly, and they should be enforced by the app rather than left to your own discipline. Check that a young child's profile cannot be changed without a parent gate.
Safety incidents should have a direct support escalation path, with a stated response time. A report button that goes to a generic contact form, or that a child cannot reach at all, is not a reporting route.
Find out how the app is funded. If it is free, that question matters. Advertising that profiles young children is the specific practice to rule out, and the answer should be stated plainly in the policy rather than left to inference.
Collecting less is the strongest protection available. Check what is gathered about the child specifically, whether an account can be closed, and whether deletion is as easy to perform as sign-up was.
While you are testing, try to get out of the intended experience. Open links, check whether a young child's profile can reach a browser, a store, or social media, and see whether anything escapes the age band you set.
If safety language is generic without process details, pause and verify. "Kid-safe", "child-friendly", and "100% secure" describe nothing. A real answer names the moderation process, the retention period, and who can access the data.
If you cannot review child activity or controls, trust risk goes up. An app that shows you nothing cannot tell you whether anything went wrong, which makes the absence of complaints meaningless as a signal.
A policy several thousand words long with no summary is a policy designed for legal teams, not parents. You should be able to find the answer to "what do you collect from my child" in a couple of minutes.
Having to email support and wait for a reply in order to delete an account means data is being retained deliberately. Deletion should be self-service.
You do not need a long trial period. Almost everything worth knowing surfaces quickly if you look in the right places.
Open the privacy policy and search for three things: advertising, third parties, and retention. If all three are addressed concretely, keep reading. If the document is vague on any of them, that is enough to stop there.
Attempt to reach adult content, another profile, an external link, and content above the stated age range. An app that holds its boundary under a determined ten-year-old is far more likely to hold it against other pressures.
Store age ratings are assigned from the developer's own questionnaire, so they are only as accurate as the answers given. Use them as a starting point, not a conclusion.
Frequent updates can mean active development, or it can mean a business model under pressure. Read the release notes: they tell you what the priorities are, including whether safety features get maintained or quietly dropped.
Review these pages before installing any kids app, and apply the same checklist to whatever you are evaluating: privacy, terms, child safety, and support. If the answers are specific, you can verify them. If they are not, you already have your decision.