Should you check your teenager’s phone?

You are probably not asking whether it’s technically allowed. You’re asking whether it’s the right thing to do, and what happens afterward.

The case for looking

Some things don’t surface in conversation. A young person being extorted over an image, groomed by an adult, or sent content about self-harm is often not going to raise it — sometimes out of shame, sometimes because they’ve been told not to, sometimes because they don’t recognize it as something to raise.

If you have a specific reason to think something like that is happening, looking is defensible and most people would do it.

The case against

A teenager who discovers you’ve read their messages generally learns one thing: tell you less.

That cost is not evenly distributed. The young people most likely to hide things afterward are the ones already inclined to manage things alone — which is to say, often the ones you most need to hear from. If the current problem is that your child isn’t talking to you, covert monitoring is unlikely to be the thing that fixes it.

The distinction that matters more than the decision

Openly and covertly are different acts with different consequences.

“I’m worried about you and I want to look at your phone with you” is a conversation. It will probably go badly in the moment. It doesn’t cost you the relationship, and it can be repeated.

Reading their phone at 2am and saying nothing costs nothing today and a great deal on the day it’s discovered. And it usually is discovered.

Age matters here too. Most parents treat a twelve-year-old’s phone differently from a seventeen-year-old’s, and that’s reasonable. What’s hard to defend at either age is a rule that changes without warning.

If you decide to look

Say so first, if you possibly can — before, not after. Look for what you’re actually worried about rather than reading everything. Don’t read it in front of them and comment as you go. And decide in advance what you’ll do with what you find, because deciding in the moment tends to produce the reaction you’d least have chosen.

If you find something frightening

Take a breath before you speak. The first thirty seconds set what happens next.

Don’t lead with anger, even if what you found makes you angry. A teenager who is frightened of your reaction manages your reaction instead of telling you the truth.

Don’t delete it yet. If what you found involves an adult contacting your child, extortion, or a threat, it may matter later. Screenshot it before anything else.

Say what you saw, plainly, and stop talking. “I saw the messages from [name]. I’m not angry with you. I need to understand what’s happening.” Then let a silence run.

If it involves self-harm or suicide, ask directly. Asking does not put the idea in their head. Then call 988 — with them if they’ll sit with you, without them if they won’t.

If it involves an image, they are not in trouble. A child being extorted over a photograph is the victim of a crime. Say that out loud and early, because they are almost certainly not assuming it. Images of someone under 18 can be reported through the National Center for Missing & Exploited Children, and their Take It Down service can have copies removed from participating platforms without the image itself being sent anywhere. More on reporting.

What monitoring software does and doesn’t do

Monitoring apps can show you activity. They can’t tell you what any of it means, and they can’t tell you how your child is.

They also tend to become the relationship: a parent watching a dashboard, a teenager finding the gaps. Some families use them well, usually openly and with a stated end date. Used covertly and indefinitely, they mostly generate anxiety in the parent and evasion in the child.

We don’t recommend particular products and we take no payment from any of them. More on monitoring and privacy.

Next

What to do first — the order of operations once you’ve decided something is wrong.

Sources referenced on this page

1. National Center for Missing & Exploited Children — CyberTipline and Take It Down. Verified 2026-09-03, primary source.