The moment of installation is a poor time to make every privacy decision. You may not yet know which features matter, and permission prompts often appear while a child is eager to continue. A review after one week gives you better evidence: you can see what the app was used for, what it requested and whether the family still wants it.
Choose a calm ten-minute window. Ask the child to show you the parts they actually use. This keeps the review connected to function rather than turning it into a mysterious inspection of their device.
Make a quick map of real use
Write down the app’s two or three valued tasks. Perhaps it records a short video for class, scans a worksheet and sends reminders. Then list the permissions currently allowed. On iPhone and iPad, App Privacy Report can show access to data and sensors and network activity when the feature is enabled. On Android, permissions can be reviewed app by app or by permission type. Exact menus vary by device and software version.
For every allowed permission, finish this sentence together: “The app needs this when we…” If neither of you can name a feature, turn the permission off and test the app. You can restore it later if a genuinely useful feature stops working.
Review the sensitive permissions one by one
- Location: Does the app need any location? If yes, would approximate location or access only while using the app work?
- Photos and files: Can you choose selected items instead of the whole library?
- Camera and microphone: Are they used only when the child deliberately records, calls or scans?
- Contacts: Is contact upload essential, or can the child add a friend through a code, school group or parent-managed invitation?
- Notifications: Keep the few that convey timely information; silence prompts designed mainly to pull the child back.
- Background activity: Ask what needs to happen when the app is not open.
Test before declaring the review finished
After changing access, ask the child to complete one normal task. If a feature fails, read the new prompt rather than approving everything. A video assignment may need the microphone only during recording, not all day. A map feature may need location while open, not in the background.
Watch for workarounds that create new risks. If turning off photo access leads a child to share a password with a friend, pause and find a safer route. The review should make the app more usable and understandable, not simply more restricted.
EdCaptain’s private digital portfolio guide offers a useful way to minimise personal data in children’s creative work. For devices shared by several children, use the shared-device agreement to clarify whose files, messages and accounts may be opened.
Use language that builds judgement
With a child aged three to five, narrate your choice: “The app wants the microphone so we can record this sound. We will allow it while we record.” Children aged six to twelve can sort permissions into needed, not needed and not sure. Teenagers can lead the audit and explain trade-offs, while a caregiver keeps responsibility for payment, family safety and legal consent.
A permission change is not a punishment. Avoid secretly removing access and waiting for the child to discover it. Say what you changed, why, and how the child can ask for a feature to be reconsidered.
Set a light review rhythm
Repeat the audit after a major update, when the app adds social features, or if the child’s use changes. Otherwise, a seasonal check is usually more sustainable than constant monitoring. Remove unused apps, close old accounts where possible and keep operating-system updates current.
If the activity report shows unfamiliar domains or repeated sensor access that does not match use, stop and investigate. A report does not prove wrongdoing, but a mismatch deserves a clear answer from the developer or school.
