SMS Tracker

The activity view lists the people and numbers your child is texting with, how many messages have gone each way, when the last exchange happened, and whether the sender is a saved contact or unknown. It is the address book of the conversation, not the conversation. You can see that your child swaps a dozen messages a day with three friends and the odd one with family, and you can see when a new, unfamiliar number appears in that mix.

What it does not show is the body of any message. You will never open a thread and read what your child said, or what was said to them, because that text is not collected in the first place. This is a firm, deliberate boundary. The SMS tracker here is about who and how often, with the option of being told when a specific worrying word appears, and it goes no further into the private content than that.

The reason to build it this way is trust that survives being explained. A child who knows you can read every text will simply move the real conversation somewhere you cannot see, and you will have traded a little visibility now for none later. A child who knows you can see the pattern but not the words is far more likely to keep texting openly, which is the only state of affairs that actually keeps them safer over time.

• The contact or number, and whether it is saved or unknown.
• How many messages have been exchanged, and in which direction.
• When the most recent message happened.
• Optional keyword alerts, without any message body.

Healthy texting has a recognisable rhythm. A few regular friends, family in the mix, bursts after school and in the evening, quiet overnight. Once you have watched that rhythm for a week or two you know it by feel, and a change in it is the thing SMS monitoring is really for. You are not hunting through words, you are noticing when the shape shifts.

Consider what a worrying change looks like without a single sentence of content. A brand new unknown number suddenly accounting for most of the day’s messages. A sharp jump in overnight texting when there used to be none. A contact your child will not name who is messaging far more than they are messaged back. A friend who has gone silent when they used to be constant. Every one of these is a story you can read from counts and timing, and every one is worth a gentle question rather than a search of their phone.

This is the same logic that makes the call log useful, applied to texting. The metadata carries the warning. A stranger working hard to reach your child looks like a stranger working hard to reach your child whether they call or text, and you do not need the words to see the effort. What you do with that knowledge is have a conversation, from a position of noticing rather than accusing.

It also keeps you honest about proportion. A single new number is not a crisis, it is a data point. Let the pattern build, watch whether the unfamiliar sender becomes a fixture, and raise it calmly if it does. The activity view is a prompt for parenting, not a substitute for it, and it works best when you treat it that way.

Alongside the activity view, you can set a small list of words you would want to know about. When one of those words appears in a message notification on your child’s phone, the app raises an alert. Crucially, the alert tells you three things and only three things: which word matched, which app the notification came from, and when it happened. It does not carry the message. It does not carry the sentence the word sat in. It does not open a thread for you to read.

The distinction matters, so it is worth being exact. A keyword alert is triggered from the notification preview, the short flash of text Android shows on the lock screen, and what leaves the phone is the fact of a match, not the text itself. You learn that the word “drugs”, say, appeared in a message today at half past four. You do not learn who wrote the sentence around it, what else it said, or how the exchange went. The word, the app, the time, and then it is over to you.

That is by design, because a keyword alert is meant to start a conversation, not end one. Knowing a charged word appeared is enough to check in warmly and ask how things are, and it protects you from the far worse instinct to read everything and confront on the basis of half a sentence taken out of context. You get the nudge. Your child keeps the conversation. The alert respects the line between the two.

MobileTracking does not collect the contents of your child’s text messages. There is no screen where you read their conversations, no stored copy of what they wrote, and no way to reconstruct a thread from what the app holds. When we say SMS monitoring, we mean the activity around the messages and, if you enable it, alerts on specific words. We do not mean message reading, and we are careful to say so because a lot of products in this space blur exactly this point.

The keyword feature does not create a back door to the content either. It reports that a word matched, not the message the word came from, so even with alerts switched on there is no path from the app to the sentence your child actually typed. The body of the message stays on the phone, in the conversation, where it belongs. All that travels is a small, deliberate signal.

This restraint is part of a wider promise the app keeps everywhere. It never records call audio. It never turns on the microphone to listen to the room. It never uses the camera. It never logs keystrokes to capture what was typed. Message content sits firmly on the same side of that line as all of those things: off limits, by design, permanently.

We hold this line because we think it is the only version of monitoring that deserves a child’s trust and keeps them genuinely safer. The moment a tool reads private messages, it teaches the child to hide, and a child who hides is harder to protect, not easier. Seeing the pattern and being warned of a serious word gives you real, actionable awareness without turning you into a reader of your child’s private life. That is the trade we have chosen, and we will not quietly walk it back.