Can You Trust Your Child's Favourite Apps?

"Everyone has it" is the argument, and it is not a safety assessment. But neither is a reflexive no, which mostly teaches a child to install things without asking.

What works better is a repeatable check you can run in about ten minutes, and that your child eventually learns to run themselves. That second part is the real goal — you are not going to vet every app for the next decade.

Why the store's age rating is weak evidence

Parents lean heavily on the 12+ or 13+ label. It carries less information than it appears to.

Ratings are largely self-declared by the developer and reviewed inconsistently. They describe the app's own content — violence, language, gambling mechanics — and generally not the thing that actually matters, which is who your child can talk to. An app rated 12+ with open messaging from strangers is riskier than a 16+ game with no chat at all.

The "13+" figure that recurs across social platforms is not a safety judgment either. It largely derives from US children's privacy law and the age at which data can be collected without parental consent. It is a compliance threshold, not developmental advice.

Use the rating as one input. Do not use it as the answer.

The ten-minute check

1. Who can contact your child? The most important question by a distance. Can strangers message them? Can adults find them by age or location? Is there open voice chat? An app where only approved contacts can make contact is in a completely different risk class from one with an open inbox.

2. What is public by default? Install it and look at the account as a stranger would. Many apps default to a public profile, visible location, and searchability by phone number. Defaults are set for growth, not safety.

3. What does it collect? Check the permissions it requests and whether they make sense. A photo editor asking for contacts and continuous location is telling you something about its business model.

4. How does reporting and blocking work? Find the buttons before you need them. An app with no visible reporting route, or where reports evidently go nowhere, is not one to trust with a child.

5. What is the culture actually like? Search the app name alongside "problems" or "safety" and read recent coverage. Better still, look at the content your child would actually see — not the marketing, the feed.

Do this with your child, out loud. It takes ten minutes, it is more persuasive than a verdict, and it teaches the method.

Features that warrant a hard "not yet"

Real-time location sharing with non-contacts. Broadcasting a child's live position to people they do not know offline is the most concrete risk on this list.

Disappearing messages as a core mechanic. Ephemerality is fine in itself, and it is genuinely good for privacy. The problem is that it removes the record — both the evidence if something goes wrong, and the friction that makes people think before sending. It also lets harm continue without leaving anything a parent or school could act on.

Anonymous or open contact from strangers. Anonymous question apps and open-DM platforms have a consistent track record of harassment, and the anonymity is the mechanism.

Weak or absent moderation. Apps positioning themselves on minimal moderation tend to deliver exactly that.

Any one of these is a reason to wait, or to allow the app with the relevant feature disabled — which is often possible and is a better negotiating position than a flat refusal.

Deciding together

Have them make the case. What is it, why do they want it, who else uses it, what would they do if someone they did not know messaged them. A child who can answer that has thought about it.

Say yes with conditions rather than no. Private account, no location, DMs restricted to approved contacts, and a review in a month. This gets you most of the safety of a refusal while keeping you inside the decision — and a child who negotiates an app with you is far more likely to tell you when it goes wrong.

Write down what "going wrong" means and what happens then. Chiefly: they tell you, and they do not lose the phone for it.

Diarise the review. Apps change. So does your child.

Expect to be wrong sometimes. An app you approved may turn out badly. Handling that calmly is what keeps your child bringing you the next decision instead of installing quietly.

What monitoring software does and does not add

App vetting is a settings-and-conversation job. Parental controls can tell you which apps are installed and how much they are used, and can limit or schedule them — genuinely useful for enforcing the conditions you agreed.

What they cannot do is tell you whether an app is safe. That is a judgment, and it comes from the check above.

They also cannot substitute for the conversation. An app blocked without explanation gets installed on a friend's phone; an app discussed and allowed with conditions stays inside a relationship where you will hear about problems. That distinction is set out in monitoring vs spying.

SmartProtect approaches this by making app rules visible and negotiable — your child can see which apps are limited and when, and can ask for changes. See app blocking.

Key takeaways

• Store age ratings are weak evidence — largely self-declared, and mostly silent on who can contact your child.
• "Who can contact my child?" is the question that matters most.
• Check the defaults yourself, as a stranger would see the account.
• Four red flags: live location with non-contacts, disappearing messages as a core feature, anonymous stranger contact, absent moderation.
• Yes-with-conditions beats no — it keeps you inside the decision.
• Vet it together. The aim is a child who can eventually run the check themselves.