What makes a parent trust a children's product? Eight questions a team can score itself on

What makes a parent trust a children's product, rather than merely tolerate it?

Trust is not the absence of complaints. It is reassuring answers to eight specific questions, answers the product team itself can give honestly without a lawyer translating the policy. These eight questions are the Parent Trust Index: an internal Dawani framework, not a government standard and not the result of a field survey with real parents, so it carries no single percentage, only a list a team scores itself on honestly.

What are the eight questions?

• Does it require a real name or identity data the play does not need? Any identity field that serves no function inside the experience raises risk for no real benefit.
• Do ads appear inside the child's experience, and are they clearly separated from what surrounds them? An ad that resembles the play content itself is riskier than one plainly labelled as an ad.
• Can the child talk to strangers through unmoderated chat? Free conversation with no human moderation is a risk on its own, regardless of the rest of the design.
• Are in-app purchases built so a child can trigger one unintentionally? A purchase button that looks like an ordinary play button is a small design difference with a large financial effect on the family.
• Does continuous autoplay run with no natural end to a session? One video or level after another with no pause turns stopping into a fight, not a calm choice.
• Can a parent delete their child's data completely with one simple request? Deletion that needs an email, a wait, and multiple approvals is deletion in name only.
• Does a parent know, in under a minute, what their child learned or did? If a parent needs several screens to understand one session, the stated transparency is only nominal.
• Does the company clearly explain why it collects each type of data, not only what it collects? Naming the data collected is not enough on its own; a parent needs to know the purpose, not just the list.

How does a product team score itself against these questions?

Each question has three possible answers: clearly yes, partly, or no. A product that answers "clearly yes" to most of the eight questions can explain its trustworthiness to a parent in one sentence per question, not a long policy paragraph. A "partly" answer is not a failure; it is a specific action item, one data field to review, or a purchase button that needs more distance from the play button. The value of this scoring is that it turns a vague feeling of "seems safe" into eight separate design decisions, each one traceable on its own.

This assessment deserves repeating, not a single pass: after every new feature, and after every change to the ad or purchase policy, because a correct answer today can slip to partial once one feature is added that was never checked against these same eight questions. A team that repeats this assessment every few months catches a small slide in trust before it becomes a parent complaint, while a team that scores itself once at launch and then forgets the list gets surprised when trust declines with no clear cause.

Why eight questions, not twelve axes?

Because the eight questions are a quick entry point a small team can apply in one sitting, before committing to a full review across twelve axes. The difference between the two lists is one of depth, not of subject: the eight questions ask about what a parent sees and feels directly, data, ads, chat, purchases, autoplay, deletion, knowledge, and purpose clarity; the twelve axes in the Child Product Safety Score add axes a parent never sees directly, such as internal moderation, measurement practice, and the child's best interest in decisions that never reach the parent at all. A team that starts with the eight questions, then moves to the full review once the product is ready for a deeper look, is working in the right order.

What is an example that builds trust, and what deserves a second look?

An illustrative example that builds trust: a simplified parent dashboard showing a child's session summary on one screen, with no ads, no open chat with strangers, and one delete button that erases all the child's data immediately with a confirmation message.

An illustrative example that deserves a second look: a sign-up asking for a real name and an exact birth date the play never needs, an ad video appearing between every two levels with no clear break, and an in-game currency purchase button similar in size to the continue button. Each element alone may look small, and their sum is what explains declining parent trust even though the product works with no technical problems.

What are the limits of the Parent Trust Index?

This is an internal assessment that relies on a team's honesty with itself, not an independent review and not the result of a survey with real parents, and it does not measure actual satisfaction. A product that answers "yes" to all eight questions still needs real testing with children and their parents, not only a theoretical assessment. The eight questions are themselves Dawani's own selection, not a list drawn from any particular regulatory standard, and the evidence level behind them is internal practice rather than a professional body's guidance.

Where should you start?

Try the Parent Trust Index on your product: the same eight questions in about four minutes, and the result stays in your browser and is sent to no one.

Apply the eight questions to your current product yourself, honestly, before someone else does. If most answers come out "partly" or "no," read How parents can judge a children's app to see these same questions from the parent's own angle, or check our safety page for our general stance on these decisions. And if you need a deeper review across twelve axes rather than eight, try the Child Product Safety Score. You can tell us about your project through the Start a project form.

References

No external source is cited in this article; the Parent Trust Index and its eight questions are an internal Dawani framework (evidence level: D), not a government or regulatory standard in any jurisdiction.

Quick questions

Is the Parent Trust Index the result of an actual survey with parents?

No. It is an internal Dawani assessment a product team uses to score itself honestly, not a field survey and not an official government standard, and it carries no percentage drawn from real parents.

What if a product answers \"no\" to more than one question?

This is not a final verdict of failure, but a priority order: fix the question about the child's data or unmoderated chat first, since those two carry the highest risk among the eight, then complete the rest.

Are these eight questions enough on their own instead of a full safety review?

No. They are a quick entry point that surfaces the clearest signs of trust or its absence. A full review needs the twelve axes in the Child Product Safety Score, and these eight questions are a small part of that, not everything it covers.