Call log monitoring for a child's Android phone
A list of the calls made and received on your child's phone: the saved contact name or the number, whether it was incoming, outgoing or missed, the time it started and how long it lasted. That is the whole feature. There is no recording and no audio of any kind, because the app never touches the microphone or the line. The log is only in the direct-download build: Google Play does not permit call-log access for apps in this category, so the Play version has no call log at all. This page walks through a week of Amara's calls, shows which patterns are worth a word at dinner, and lists what the log cannot tell you.
Android · Direct-download (APK) build only · Visible on their phone · Permission: Call log
- Five facts per call, nothing more. Name or number, direction, start time, duration, and whether it was missed. No recording, no transcript, no voicemail, no audio of any kind, on any plan.
- Direct-download build only. Google Play's policy does not allow call-log access for parental-control apps, so the Play build has no call log. The APK from the download page does.
- Your child sees the same list. "Who you call, when and for how long" is a line on the What's shared screen of the child app, and it appears there the same afternoon the feature is switched on.
- Patterns, not single calls. A 48-minute call is a Monday. Three calls after 22:00 in one week is a pattern, and the app draws a card for it so you don't have to count.
- Phone calls only. Voice calls inside WhatsApp, Snapchat, Discord or any other app go through the internet, not the phone's dialler, and never appear here.
Fourteen calls in seven days, and the two lines Priya reads twice.
The call log on a thirteen-year-old's phone is short. Amara's week has fourteen calls in it: six with Tyler, five with Priya, two with Grandma Ngozi, and one missed call from a number nobody has saved. Here is the week as the log shows it, with the entries that mattered and the many that didn't.
The longest call of the week, and a number with no name.
At 20:14 Amara rings Tyler and they talk for 48 minutes. The row shows exactly that: Tyler · outgoing · 20:14 · 48 min. Not a word of it is heard by anyone, including the app. At 21:48 a second row appears: 07700 900481 · missed · 21:48, with no name because the number is not in Amara's contacts. One missed call from an unsaved number is nothing; delivery drivers and wrong numbers produce one of these most weeks. The app notes it and does not alert anybody. If the same number comes back three or four times, it will.
Family calls make up most of a child's log.
Priya rings at 15:36 to say she's running late for pick-up: 3 minutes, incoming. At 18:20 Amara rings Grandma Ngozi for 11 minutes, as she does most Tuesdays. Two rows, both to people in the house or near enough. This is what the log looks like most days, and it is worth saying so before anyone installs it expecting drama. A parent who opens the call log on a Tuesday is usually looking at their own name.
A short call with Tyler, and one from the car park.
Tyler rings at 16:52 and they talk for 9 minutes, probably about homework because the maths test is Thursday. Priya rings at 17:40 for one minute from outside Swim Club to say she's parked. Nothing in either row would make anyone look twice, and the app treats them that way: they sit in the list, they count towards the week's totals, and nobody is notified. The unknown number from Monday has not come back.
The week's third Tyler call, at a sensible hour.
Priya, incoming, 15:33, 2 minutes. Then Tyler, outgoing, 19:05, 14 minutes. By now the contact list on the right of the screen shows Tyler at the top with three calls and 71 minutes, Priya second with three calls and 6 minutes, Grandma Ngozi third. The order is who Amara talks to most, measured in minutes, and it will not surprise any parent of a thirteen-year-old. The person with the most minutes is almost always a best friend.
The first call after ten o'clock.
A two-minute call from Priya at 15:40, and then at 22:18 Tyler rings and they talk for 21 minutes. It is a Friday and the weekend bedtime is later, so the wind-down hasn't started. One late call on a Friday is a Friday. The app doesn't flag it. What it does is start counting, because calls after 22:00 are one of the things it watches across a week rather than a night.
A second late call, and the card appears.
Grandma Ngozi rings at 11:10 for 6 minutes. At 23:05 Amara rings Tyler and they talk for 32 minutes. That is two calls after 22:00 in two nights, both with the same person, and a pattern card now sits above the log: Calls after 22:00 this week: 2 (all with Tyler). It is drawn from timestamps alone. The app has no idea what the calls were about, whether anyone was upset, or whether Tyler's parents know he's on the phone at eleven.
Three late calls, one question at breakfast.
Priya rings at 13:02 for a minute. At 22:41 Tyler rings and they talk for 17 minutes, and the card updates to three. On Monday morning Priya asks the only question the log supports: "You and Tyler have been on the phone late three nights running. Everything alright?" It turns out Tyler's parents are splitting up and he rings when the house goes quiet. That isn't in the log, and it couldn't be. The card got the question asked; Amara supplied the answer; the texting pattern would have shown the same late-night shape.
Every row in the log holds the same five things
The log is a table and each row is one call. The first column is the name from the phone's own contact list, or the bare number if there is no match. The second is an arrow: incoming, outgoing or missed. The third is the time the call started, in the child's local time. The fourth is the duration, counted from the moment the call connected, so a ringing-out call that nobody answered shows as outgoing with no duration. There is no fifth column for what was said, because the app has no way of knowing. That is not a plan limit or a setting. The Android permission the feature uses hands over a list, and nothing in the app touches the microphone or the call itself.
Names come from the phone, not from the panel. If Amara saves a number as "Tyler" the log says Tyler; if she saves it as "T" it says T. Priya can rename a number in the panel for her own reading, and that label stays on her side. The log is kept for a rolling window of recent weeks and then dropped, the same way location history is, and deleting a child removes all of it.
- Missed and declined are both "missed". The log can't tell whether a call was ignored on purpose or rang out in a bag.
- Unsaved numbers stay numbers. The app does not look a number up anywhere. If it isn't in the phone's contacts, you see digits.
- Deleted on the phone, still in the log. Clearing the dialler's recent list doesn't remove a call that was already reported, and the child app says so.
Pattern cards count what you would otherwise have to
Nobody wants to read fourteen rows a week, and a log that only works if you read it daily is a log that stops being read by October. So the app watches four shapes across the week and draws a card when one appears: calls after a set hour, an unsaved number that keeps coming back, a single call much longer than usual, and calls during school hours. The late-calls card is the one in the picture, Calls after 22:00 this week: 3 (all with Tyler), built from three timestamps and one contact name.
The settings screen is where you decide which cards to draw and when. Call monitoring can be switched off per child; the late-call hour defaults to 22:00 and can be moved; the unknown-number threshold is how many calls from one unsaved number before a card appears; school hours are the same window the smart alerts use. Every toggle you set here is mirrored on Amara's What's shared screen within the afternoon, down to the hour you chose.
- Cards sit in the log and the daily summary. They don't buzz your phone at 23:06. A card that arrives in the morning is read; a buzz at night is resented.
- The unknown-number card names the number. It cannot name the person. "07700 900481, 4 missed calls, not in contacts" is the whole message.
- Off means off. Switch call monitoring off and the log stops that minute, the card disappears, and the child app's list updates to match.
Five patterns worth a conversation, and what each one can't tell you.
Every one of these is a shape in the timestamps. None of them is a verdict. The right-hand column is the question each pattern supports, which is deliberately smaller than the question a worried parent wants to ask.
| Pattern | What the log shows | What it can't show | The question it supports |
|---|---|---|---|
| Calls after 22:00 | Three this week, all with Tyler: Fri 22:18, Sat 23:05, Sun 22:41. A card counts them. | Why. Whether anyone was upset. Whether the other family knows. | "Late calls three nights running. Everything okay with Tyler?" |
| One number, many times | An unsaved number calling repeatedly, with the count and the days. The card appears once it crosses the threshold you set. | Who it is. The app never looks a number up. | "A number you haven't saved keeps ringing. Do you know who it is?" |
| A long call with an unknown number | Duration against an unsaved number, for example 26 minutes with digits in the name column. | A word of what was said. Whether your child made the call expecting a friend. | "You were on the phone to a number for half an hour. Who was that?" |
| A friend who stopped calling | A name that was top of the list for weeks and now has no rows. The weekly totals make the drop visible. | Whether they fell out, moved to WhatsApp calls, or just see each other at school now. | "You and Tyler haven't talked much lately. Everything alright between you?" |
| Calls during school hours | Rows between 08:30 and 15:30 on a school day, which on a normal week should be few or none. | Whether the phone was supposed to be in a locker, or the teacher said it was fine. | "There were a couple of calls during lessons on Tuesday. What was happening?" |
Read the week, not the night
One call at 23:05 is a Saturday. The card needs three in a week before it exists, and even then it is a count, not an accusation. If you find yourself reacting to a single row, close the log and open it again on Sunday.
Most minutes go to one friend
At thirteen, the top contact is nearly always a best friend and the minutes are nearly always large. Tyler's 48 minutes on Monday is a normal Monday. Treat the name at the top of the list as who your child trusts, not as a problem to solve.
Phone calls are the smaller half
A thirteen-year-old's actual talking happens in WhatsApp calls and Discord voice channels, none of which pass through the dialler. If the log is quiet it may mean the talking moved, which social app timing shows and this page doesn't.
Four reasons the call log doesn't match the phone, in the order they happen.
Almost every question about a missing or odd call log comes down to one of the four cards below, and the first one accounts for most of them on its own. Before you assume a child has found a way round the feature, check which build is installed and what the health line says. A log that stopped on Tuesday with a permission named on the Device health page is a settings problem, and it is fixed on the phone in under a minute with your child beside you.
The one thing that is not on the list is "my child is deleting calls". Clearing the recent-calls list on the phone doesn't remove anything already reported, and the child app tells them so on the What's shared screen. The app was built on the assumption that a feature a child can't quietly defeat is also a feature they don't need to.
The log has been empty since pairing.
The Google Play build is installed. It has no call log, by Google's policy for this category, and the panel's Calls tab says so rather than showing an empty list that looks broken.
Fix: Install the direct-download APK from the download page over the top of the Play build; the pairing survives and the log starts from that moment. The download and setup guide covers the three Android dialogs you'll see.
The log worked, then stopped mid-week.
An Android update or a manufacturer "app permissions reset" removed the Call log permission for an app it decided was unused. Samsung's A-series phones do this after a few weeks without the app being opened by the child.
Fix: Device health names the missing permission and offers a fix-together prompt. On the phone: Settings → Apps → MobileTracking → Permissions → Call logs → Allow. While there, check that "Remove permissions if app is unused" is off.
A friend shows as a number, not a name.
The contact lives in an app's own list, usually WhatsApp, and not in the phone's address book. The log reads names from the address book only, and it needs the Contacts permission to do even that.
Fix: Have your child save the number to the phone's contacts, or give it a label in the panel for your own reading. Check Contacts is allowed under the same Permissions screen.
A call shows a duration of zero.
An outgoing call that rang and was never answered, or an incoming call declined at once. Both are real rows, and both have no connected time to count.
Fix: Nothing. Read a zero-duration outgoing row as "tried to ring" and a missed row as "was rung". Several zero rows to one number in a row are a child trying to reach someone, which is worth knowing and not worth worrying about.
What parents ask about the call log before switching it on.
Does the call tracker record calls or let me listen in?
No, and it never will. The feature reads the phone's call list, which gives it a name or number, a direction, a time and a duration. It does not use the microphone, does not capture the line, and holds no audio at all. This is the same on every plan and in both builds. Any product that offers call recording on a child's phone is in a different category from this one, and in most countries a legally risky one.
Can I see calls made in WhatsApp, Snapchat or Discord?
No. Those are internet calls inside an app, and they never pass through the phone's dialler, so they are invisible to the call log. What you can see is how long those apps were open and when, and how many notifications they produced, through social media monitoring. For a teenager that is often where the longer conversations happen, so a quiet call log is not a quiet phone.
Which build do I need for the call log?
The direct-download APK from this site. Google Play's policy stops parental-control apps from reading the call log, so the version in the Play Store has no Calls tab. Everything else, from the map to screen time, is the same in both. If you installed from Play and want the log, install the APK over the top: the pairing and the rest of the settings carry across.
Will Amara know her calls are logged?
Yes, the same afternoon it is switched on. The child app's What's shared screen gains a line reading "who you call, when and for how long", and the consent screen she accepted at pairing listed calls as a thing that might be shared. She can open the same list on her own phone. There is no setting that hides the feature from her, and no build that does.
How many weeks of calls does the panel keep?
A rolling window of recent weeks, after which the oldest rows drop off. That is long enough to see a friend stop calling or an unknown number keep coming back, and short enough that there is no archive of a child's whole adolescence sitting on a server. Deleting a child from the account removes all of it at once.
What does the log show for a number my child hasn't saved?
The digits, the direction, the time and the duration. The app does not look the number up against any directory or social network, so it cannot tell you who is calling. What it can do is count: if the same unsaved number calls more than the threshold you set in a short period, a card appears naming the number and the count, with Save as contact, Watch and Ignore buttons.
Can I block a number from the parent panel?
No. The app does not control the dialler and does not reject calls. Blocking a number is done on the phone itself, in the dialler's own settings, and that is a thing worth doing together with your child rather than for them. The panel's job is to make the pattern visible; the decision and the tap are theirs and yours.
If my child deletes a call from the phone, does it vanish from the log?
No. Each call is reported when it ends, and the log keeps its copy regardless of what happens to the phone's recent-calls list afterwards. The child app says this plainly on the What's shared screen, so clearing the list is not a secret workaround anyone is tempted to try. The reverse is also true: a call the phone never logged, because the permission was off, is not recovered later.
Can I get an alert for a call after a certain hour?
You can set the hour, 22:00 by default, and the app counts calls after it across the week and draws a card when the count reaches three. The card goes into the log and the next daily summary rather than interrupting you at the time. If you would rather be told straight away, the smart alerts rules let you promote it, but most parents find the morning version easier to act on.
Where the call log fits with everything else
The call log is one half of a pair, and the other half answers questions this page cannot: calls and SMS monitoring, SMS tracker and keyword alerts.
The call log 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 ring and when. Never a word of what was said.
Pair the phone together, install the direct-download build, and the log fills in from the first call. Your child sees the same list on their own screen.
Android · Free account · Visible on your child's phone