Worth your attention

An SMS tracker that shows texting patterns, not messages

The SMS log on your child's Android phone records three things about each text: who it went to or came from, when, and how many that makes today. It never records the words. Not on a free account, not on any subscription, not at any price, because the code that would read a message does not exist in the app. The log is only in the direct-download (APK) build; Google Play does not allow SMS-log access for a parental-control app, so the Play build leaves this page blank. It also covers ordinary text messages only: WhatsApp, Snapchat and the rest are handled by notification counts under social media monitoring, not here.

Set it up with your child Open the demo

Android · Visible on their phone · Direct-download (APK) build only · Numbers and times, never message text

By MobileTracking Editor · Founder and editorUpdated October 6, 2026
The SMS log for Amara listing each contact or number with its direction, time and count for the day, and no message text anywhere on the screen

What does the SMS tracker record?

Who was texted, when, and how often. Nothing from inside the message.

Each text message that arrives on or leaves your child's phone adds one row to the log. The row holds the contact name if the number is saved, or the bare number if it is not, an arrow for sent or received, the time to the minute, and a running count for that number on that day. That is the whole record. In a normal week for Amara, who is thirteen, the log holds about 86 rows, and 31 of them belong to her friend Tyler. Priya can see that Tyler texted at 15:34 and again at 21:41. She cannot see what either of them said, and the app has no way to show her, because the words were never collected.

The feature is built on the same rule as everything else in MobileTracking: the app collects the shape of activity and never the contents. Names, times, counts and directions are the shape. The text is the contents. If you are looking for an app that reads messages, this is not it, and we would rather say so in the first paragraph than let you find out after pairing.

Can I see the text of a message on a higher plan?

No. There is no plan, price or setting that shows message text.

Some monitoring apps show you a locked preview of a message and offer the words for a monthly fee. That design depends on reading every message in the first place and holding it on a server somewhere, which is exactly what we refuse to do with a child's conversations. MobileTracking's child app does not contain a reader for SMS content, so there is nothing to unlock. A subscription changes which features are switched on across your account; it does not change what any feature is allowed to look at. The panel lists what each plan includes before you pay, and the SMS log is described there the same way it is described here: contact, direction, time, count.

This also means a support request cannot get you the text of a message. Support staff see the same rows you see, with limited and logged access for troubleshooting, and no more. If a page anywhere on the web promises to show you a child's texts through this app, it is not describing this app.

Why is the log missing from the Google Play build?

Google Play policy does not allow SMS-log access for this category of app, so the Play build does not ask for it.

Google restricts which apps may read the SMS log on Android, and a parental-control app installed from the Play Store is not permitted to. We follow that rule rather than work around it, so the Google Play build of the child app has no SMS permission, collects nothing about texts, and shows an empty state on the SMS page of the panel with a note explaining why. The same applies to the call log; the calls and SMS monitoring page has the full comparison of the two builds.

The direct-download build from this site's download page is the same app with the SMS and call-log permissions added. It installs through Android's "Install unknown apps" setting, which you switch on for one browser, use once, and switch off again. Play Protect still scans the file. If you already paired the Play build and want texts included, install the APK over it. The phone usually stays paired, and if the Devices page says otherwise a fresh code pairs it again in a couple of minutes. The SMS rows start from the moment the new permission is granted, not before.

Does it cover WhatsApp, Snapchat or Instagram messages?

No. The SMS log is text messages only. Messaging apps are covered separately, by notification counts.

A text message goes through the phone's messaging app and the mobile network, and Android keeps a log of it that this feature reads. A WhatsApp message goes through WhatsApp's own servers, is end-to-end encrypted, and never touches that log. The same is true of Snapchat, Instagram DMs, Messenger and Viber. No honest app on an unmodified phone can list those conversations, and this one does not try.

What MobileTracking can see for those apps is how many notifications each one raised and when, plus how long the app was open, which is the job of social media monitoring. Between the two features you get a comparable picture: 31 texts with Tyler on the SMS page, and perhaps 184 WhatsApp notifications in the week on the social page, each with its timing. Neither tells you a word of what was written, and for a thirteen-year-old most of the traffic will be in the apps, not in SMS. Expect this page to be the quieter of the two.

What does my child see about it?

A line on the "What's shared" screen of their own phone, reading "Texts: numbers and times only".

The child app is a visible app with its own icon, and its transparency screen lists every feature a parent has switched on. When Priya turns the SMS log on in the panel, Amara's phone updates the same afternoon with a new line under "What's shared" that names the feature and states what it collects: who she texts, when, how many. Directly under it is a line that says "Never the words of a message", because a child who assumes the worst behaves as if the worst is true, and a child who knows exactly what is shared can decide what to think of it.

The "What's shared" screen on Amara's phone showing the texts line as numbers and times only, with a note that the words of a message are never shared
The line Amara sees on her own phone once the SMS log is switched on.

Amara can also see that a parent opened the panel today, though not which pages. We think that is the right balance. A parent who looks at the SMS log is doing nothing to be ashamed of, and a child who knows a parent might look has every reason to keep their texting ordinary. The page on the child app walks through the whole transparency screen if you would like to show it to your child before you pair.

What is an unknown-number flag?

An alert when a number that is not in your child's contacts keeps texting, such as 11 texts in 2 days.

Most texts on a child's phone come from a few saved people: a parent, a sibling, two or three friends, the orthodontist's reminder service. A number with no name attached that appears once is usually a delivery, a verification code or a wrong number. A number with no name that appears eleven times in two days is something else, and that is the pattern the flag watches for. In the Okafors' demo week, 07700 900481 texted Amara on Tuesday evening and kept going through Wednesday, and the flag appeared on the second day with three choices: save it as a contact, watch it, or ignore it.

"Watch" keeps the number highlighted so you notice the next time it appears. "Ignore" stops that number raising the flag again, which is right for the dentist. "Save as contact" is the most common ending, once a parent has asked and learned that it is a classmate's new SIM. The flag never involves the content of the texts; it is counting rows. A number that sends one text a week will not trigger it, and a parent who wants every unknown number listed can see them all on the Calls and SMS overview, where they are counted separately.

What does the texting pattern view show?

Bars for each hour of the day, showing when texts happen. Amara's busiest hour is 21:00 to 22:00.

The pattern view takes the week's rows and sorts them into twenty-four bars, one per hour. It does not name anyone; it answers a different question from the log, which is "when does my child's phone do its texting?" For Amara the picture is unsurprising: almost nothing before 08:00, a small bump at lunch, a rise after 15:31 when school finishes, and the tallest bar between 21:00 and 22:00, which is the hour after homework and before the bedtime schedule turns the phone off at 21:30. Most of that tall bar is Tyler.

The bars are useful because they change slowly. A week that looks like the one above is a settled routine. A week where the tallest bar has moved to 23:00 to midnight, on a phone whose bedtime starts at 21:30, is worth a look at the bedtime schedule and a question at breakfast. A tall bar in the middle of a school morning is a different question again. None of these needs a message read; they need a parent who has seen the ordinary shape and notices when it moves.

What should I actually do with a week of it?

Look once, learn the normal shape, and only act when the shape changes.

The temptation with any log is to read it every evening, and the result is a parent who knows that Tyler texted at 21:41 on Wednesday and has no idea why that matters. It usually does not. A better routine is to open the pattern view on Sunday, glance at the top three contacts and the unknown-number count, and close it. In the Okafor house that takes under a minute: 86 texts, Tyler on 31, Priya herself on 19, Noah on 9, one flagged number dealt with on Wednesday. The number to remember is 86. If next week is 240, something has changed and it is worth asking about, kindly, with the phone nowhere near the conversation.

The other thing to do is tell your child the number. "You sent and received 86 texts this week, mostly Tyler" is not an accusation, and saying it out loud reminds both of you what the log is for. The smart alerts feed will carry the unknown-number flag to you so you do not need to check for it; everything else on this page can wait for Sunday.

The log: five columns, and no sixth

APK build onlyAndroid SMS permissionListed on "What's shared"

Open Amara's SMS page in the parent app and you see the current day at the top, then the days before it. Each row is a contact or number, an arrow pointing in or out, a time, and a small count showing how many texts that number has sent or received so far today. Tyler's row at 21:41 on Wednesday reads "Tyler · received · 21:41 · 7 today". A row for a number that is not saved shows the number itself, with a grey "not in contacts" tag, so the two kinds are easy to tell apart at a glance.

There is no sixth column, and the layout leaves no space for one. We drew the screen this way so that a parent cannot wonder whether the text is hidden behind a tap. It is not there. The row for a picture message looks like any other row; the picture is never collected, in the same way the app never reads the photos on the phone. A group text appears as one row per recipient, which is what the phone's own log records, so a message to four friends adds four rows.

  • Both directions, marked. Sent and received are separate arrows, and the pattern view can show either on its own.
  • Counts per number per day. The count resets at midnight, so "7 today" on Wednesday is Wednesday's seven, not the week's.
  • Nothing from the message. No preview, no first line, no word count, no attachment, no link. The row is complete as drawn.
Wednesday in the SMS log: Tyler received at 21:41 with seven that day, Priya sent at 15:40, and an unsaved number marked not in contacts

The pattern: a week as twenty-four bars

APK build onlyNo names on this screen

The pattern card sits above the log and compresses the week into one picture. Each bar is an hour of the day, and its height is the number of texts in that hour across all seven days. Amara's week has 86 texts, and the card distributes them: a few bars of one or two before school, a cluster of around five in the hour after 15:31, and the tallest bar, fourteen, between 21:00 and 22:00. The bars after 22:00 are empty, because her bedtime schedule stops texts reaching the screen, and the phone's own log confirms that nothing was sent either.

The point of the card is comparison, not detail. Keep it in mind for a fortnight and you will know, without thinking about it, what an ordinary week looks like. Then the bars do the work: a new bar at 02:00, a school-hours bar that has doubled, or a tall bar that has moved later are each a one-line question for the next day. Nobody needs to read a text to notice any of them, and the card does not offer one.

  • Seven days at a time. Tap back a week to compare; the panel keeps a rolling window of recent weeks, not an archive.
  • Sent, received or both. A filter at the top redraws the bars for one direction, which separates "being texted at midnight" from "texting at midnight".
  • Same numbers as the log. The card counts rows; it adds no estimate and no score. If the log says 86, the bars add up to 86.
The texting pattern card for Amara with one bar per hour of the day and the tallest bar between 21:00 and 22:00
Three situations

Three weeks in the Okafor house where the SMS log earned its place

A log of who and when is only useful if a parent knows what to do with it. These three situations are the kinds of thing it catches, and each one ends in a conversation rather than in a screen, because the screen has nothing more to give.

Situation 1

The number with no name that would not stop

On Tuesday evening a row appeared in Amara's log for 07700 900481, with the grey "not in contacts" tag. One unknown number is nothing; Priya did not notice it and would not have been told. By Wednesday afternoon the same number had sent or received eleven texts in two days, mostly between 16:00 and 18:00, and the unknown-number flag went into her alerts feed as a single line with the count, the number and three buttons.

Priya chose "Watch" rather than acting on it, and asked at dinner. The answer was that Tyler's cousin had come to stay for half-term and was texting from his own phone to arrange a swim on Thursday. Priya saved the number as "Tyler's cousin Sam" from the alert, the flag cleared, and the number has never been flagged since because it now has a name. The whole episode was two taps, one question and no message read.

What the app did: Counted eleven rows from one unsaved number across two days, raised one alert, and offered Save, Watch or Ignore. It did not show, and could not show, what any of the eleven texts said.

Situation 2

The week the tallest bar moved to 23:00

Amara's bedtime schedule turns her phone off at 21:30 on school nights, so her pattern card normally has nothing after the 21:00 bar. One Sunday in March the card looked different: a bar of nine between 23:00 and midnight, all received, all from Tyler, spread across Wednesday and Thursday. Nothing had been sent back, which the direction filter showed in one tap, so Amara's phone had been asleep as scheduled and the texts had simply queued.

That changed the conversation. The question was not "why were you up texting", because she had not been; it was whether Tyler was all right, texting a sleeping phone at that hour two nights running. Priya mentioned it to Amara without the phone in the room. It turned out Tyler's parents were away and he was unsettled, and Amara had already noticed. The log gave Priya a reason to ask a day earlier than she otherwise would have.

What the app did: Drew the week's bars, showed a new tall one at 23:00, and let the sent/received filter show that every text in it was incoming. Nothing about the texts themselves was collected, and the bedtime schedule's own log confirmed the phone had been off.

Situation 3

Fourteen texts between 10:15 and 11:00 on a Tuesday

Oakridge School keeps phones in bags during lessons, and Amara's pattern card normally shows a flat line from 08:49 until the 12:30 lunch bump. On one Tuesday the 10:00 bar stood at fourteen, all sent, all to Tyler. The log put every one of them between 10:15 and 11:00, in what Priya knew from the timetable was a double maths lesson. There was no alert for this, and there should not be: fourteen texts to a saved contact in a school morning is unusual for Amara, but it is not the kind of event that should interrupt a parent's day.

Priya raised it that evening, with the fact and nothing else: "Your phone sent fourteen texts in maths on Tuesday." Amara's answer was that the class had a supply teacher and half the room was on their phones. That is a school matter more than a texting one, and the conversation ended with Priya adding a school-hours block for the messaging app through app blocking, which Amara could see on her own phone the same afternoon, with Priya's name on the rule.

What the app did: Logged fourteen sent rows to one saved contact with their times, and showed them as one tall bar in a normally empty hour. It did not alert, because nothing in it matched an alert rule, and it did not reveal what the texts were about.

One row, explained

What a row in the SMS log contains, field by field

This is the complete record for one text message. If a field is not listed here, the app does not have it. We would rather a parent read this and decide the feature is too thin for them than install it expecting more.

Contact or number

The name from your child's own contacts list if the number is saved there, otherwise the number as the network delivered it, such as 07700 900481. The app does not look up unsaved numbers against any directory, and it does not guess a name. If your child saves the number later, rows from before that day keep showing the bare number, so you can see when a contact was new.

Direction

Sent or received, shown as an arrow. A text your child wrote is "sent"; one that arrived is "received". A failed send is not recorded, because the phone's log does not record it either. The pattern view can filter on this field, which is how Priya told a child who was texting at 23:00 from a child whose sleeping phone was being texted.

Time

The minute the message was sent or arrived, in the phone's local time: 21:41, not "evening". A text that arrives while the phone is off is logged when the phone receives it, which may be the next morning, so a bedtime-schedule phone can show a small cluster of received rows at 07:00. The time is also what the pattern card is built from.

Count that day

How many texts have passed between your child and this number so far that day, in both directions. It resets at midnight. "Tyler · 7 today" at 21:41 means seven since 00:00, including this one. The weekly figures on the Calls and SMS overview and the unknown-number flag are both built by adding these counts up.

Whether the number is saved

A grey "not in contacts" tag on any number your child has not saved. This is the field the unknown-number flag watches: it counts rows with the tag from the same number and raises the flag when they pile up, which in the demo is eleven in two days. Saving the number, on the child's phone or from the alert, removes the tag from that day onward.

Nothing else

No message text, no preview, no first word, no length, no attachment, no link, no emoji, no draft, no deleted message, no screenshot of the messaging app. The child app has no component that reads the body of an SMS, and the permission it asks for is used only to read the five fields above. This is true in the direct-download build, the only build that has the log at all, on every plan.

SMS tracker questions

Six questions parents ask about the text log.

Does the SMS log show group texts or picture messages?

Both appear as rows, and only as rows. A group text adds one row per person it went to, because that is how the phone records it, so a message to four friends shows as four sent rows at the same minute. A picture message is one row with the same five fields as any other; the picture itself is never collected, in the same way the app never reads the photos on the phone.

Can I switch the SMS log off and keep the call log?

Yes. Calls and texts have separate toggles in the Calls and SMS settings, so a parent who wants the call log for a nine-year-old but sees no need for texts can leave SMS off. Each toggle has its own line on the child's "What's shared" screen, which updates the same afternoon, so your child sees exactly which of the two is on. Switching SMS off stops collection at once; nothing is recorded until it is switched back on.

Does deleting a text on my child's phone remove it from the log?

No. The row is recorded when the message is sent or arrives, with its five fields, and deleting the conversation afterwards on the phone does not reach back into the log. What you see is still a contact, a direction, a time and a count, never the message, so a deleted text looks exactly like one that was kept. Deleting the child's history from the panel removes the rows; nothing else does until the rolling window lets them go.

Does it work on a tablet with no SIM card?

There is nothing to record. A tablet without a SIM has no mobile number and cannot send or receive SMS, so the SMS page for that device stays empty whichever build is installed. Messaging on such a tablet happens in apps, and those are covered by notification counts under social media monitoring. Some tablets with a SIM do support texts, and on those the APK build records the log as it would on a phone.

Does an unknown-number flag mean something is wrong?

Usually not. The flag means a number that is not in your child's contacts has texted repeatedly, eleven times in two days in the demo, and nothing more. In most families the answer is a new friend, a classmate's new SIM or a club's reminder line. Ask, then save or ignore the number from the alert so it is not flagged again. The flag counts rows; it has no view of what the texts said and makes no judgement about them.

What happens to the log if we move back to the Google Play build?

Collection stops. The Google Play build has no SMS permission, so no new rows are recorded from the moment it is installed, and the SMS page shows an empty state explaining why. Rows recorded under the APK build before the switch stay in the panel until the rolling window drops them or you delete the child's history. Reinstalling the APK later starts the log again from that day, not from the gap.

Where this fits with everything else

The SMS log is one column of a wider picture, and these pages hold the rest of it: calls and SMS monitoring, call log, keyword alerts, social media monitoring and smart alerts.

SMS tracker switches on once your child's phone is paired with your account, which takes about ten minutes with both devices on the table. The download and setup guide walks through every screen.

Know who they text and when, and never a word of it.

Install the direct-download build with your child beside you, switch the text log on, and let the first week show you the ordinary shape before you decide anything.

Set it up with your child Open the demo

Android · Free account · Visible on your child's phone