The permission your child's apps have - and why you probably haven't checked

The permission problem nobody talks about

Most of us install an app, tap 'Allow,' and move on. We don't go back to iOS Settings to audit what we've actually granted. And why would we? iOS hides this information across a dozen different settings screens. One app gets location. Another gets your photos. A third gets clipboard access. You're meant to know what you've permitted, but the system makes it exhausting to check.

For parents, it's worse. Your child's iPhone is their own device. You can't easily see which apps have asked for what, let alone help them decide whether a permission makes sense. iOS Family controls let you restrict app downloads, but they don't give you visibility into permissions. I realised we had a gap.

What a privacy audit actually looks like

Guard solves this by doing something simple but useful. It shows you a dashboard of 12 common apps (Instagram, TikTok, Spotify, Maps, and others most families use). For each one, you see exactly which permissions that app typically requests: location, contacts, calendar, microphone, photos, and more. Each app gets a privacy risk score based on how many sensitive permissions it asks for and whether those requests match its functionality.

Tap on any flagged permission, and Guard deep-links you straight into iOS Settings. You can revoke it immediately without guessing which menu to navigate. It's not rocket science, but it saves you the fifteen-minute Settings scavenger hunt.

The demo set is intentionally curated. iOS's sandbox architecture means third-party apps can't actually audit what permissions other apps currently have on your device; that's a system-level restriction. So Guard educates with a real, representative list. You see what these apps ask for in the wild, then you check your own device to see which ones you've actually granted.

Why parents need more than app store ratings

When we launched, I expected most users to be security professionals and privacy advocates. The uptake from parents surprised me. They were downloading Guard in clusters, often after a single conversation with a child about an app. One parent told me she'd finally understood why her teen's messaging app needed microphone access (voice notes), and why it probably shouldn't have location. Another said the risk score gave her language to have that conversation in the first place. 'Why does this need your photos?' is easier to ask when you're both looking at the same score.

The Family tier was built because of those conversations. It lets you monitor permissions across six devices from one hub, and it surfaces alerts when an app requests new permissions or when permissions change. If your child's phone suddenly starts broadcasting location to an app that never asked before, you see it. You're not spying on their device; you're staying aware of the permission landscape they're navigating.

The clipboard check that caught us off guard

One of the features in Personal Pro is the clipboard safety check. It's simple: it tells you when an app has accessed your clipboard in the last few hours. iOS logs this in the background, but unless you're digging through Settings, you won't notice. Apps legitimately copy and paste, but some apps copy more than they should. We added this feature after reading about apps that were silently harvesting clipboard data during installation.

It's not a smoking gun if an app accesses your clipboard once. But patterns matter. If a shopping app checks your clipboard five times in an hour, that's worth knowing. You might want to revoke clipboard access and see if the app still works. Parents use this feature differently than professionals do. They check it and then ask their child, 'Why would this app need to see what you just copied?' It's a teaching moment.

What we're not trying to do

I want to be clear about the limits. Guard is not an antivirus. It won't catch malware. It's not a VPN, and it doesn't hide your traffic. We can't tell you if an app is spying through your microphone or camera because iOS doesn't expose that telemetry to third-party developers. What we can do is show you the permissions landscape, help you see what apps are asking for, and give you a friction-free way to make changes.

For parents, that's often enough. It transforms the conversation from 'I don't know what this app does' to 'I can see what it's asking for, and we can decide together whether that makes sense.' The tools are already in iOS. Guard just makes them visible and accessible.

The real work is the awareness

I sometimes hear from parents who've used Guard to revoke a permission, only to find the app stopped working. They're frustrated, and they let me know. But more often they're relieved. They discovered they didn't need that app anyway. Or they reinstalled it without granting certain permissions and found it worked fine. They learned something about what their devices are actually capable of.

That's the real win. Not a feature. Not a score. It's the moment when someone realises they have agency over their device, and they can exercise it. For a parent helping a child navigate the mobile internet, that matters.