Why we built real-time alerts into Guard
Three months into Guard's beta, a user emailed us. She'd revoked location access from a fitness app using the deep-link feature we'd built, felt secure, and didn't check Guard again for six weeks. When she opened it one morning, the app had quietly re-requested location. She'd never see the notification. She'd never know. That message changed how we thought about the product.
The permission that came back
The fitness app scenario isn't rare. iOS lets apps request permissions again after a user has denied them, and many do. Some are careless. Some are intentional. The sandbox rules mean third-party apps on iPhone can't actually see what permissions another app holds. Guard works around this with a curated dashboard of 12 common apps, showing what each one would access if you let it, and a privacy risk score so you know what matters.
But the dashboard is a snapshot. You revoke something on a Tuesday. By Friday, the app asks again. You're swiping through settings, your phone's buzzing, and you tap yes by accident, or you assume Apple's already asked and said no. And you're exposed again.
We'd given people a map. We hadn't given them a lookout.
Building the alert layer
Real-time permission-change alerts became a Personal Pro feature because they sit at the heart of what privacy actually means on a phone. It's not just knowing what an app could access. It's knowing when the situation changes.
The technical side was straightforward enough. The harder part was deciding what matters. We could alert on every permission request. That would be noise. Instead, we watch for the moment an app you've already flagged regains access to something you'd revoked. If you've told Guard that location matters to you (because you've marked it as concerning), and an app reacquires it, you get an alert.
It's not a lock. It's a notification. You still have to make the choice. But you're not flying blind.
What the alerts actually solve
After launch, the feedback loop was immediate. Parents using the Family tier (which lets you monitor six devices with child controls) were the first to see the value. A parent sets up Guard on their child's iPhone, reviews the permissions, and revokes access to location or contacts from specific apps. Then life happens. The child updates an app. An app developer pushes a new version with a new permission request. Without alerts, the parent wouldn't know until weeks later, if at all.
Professionals handling sensitive data came next. A user working in healthcare told us she now uses the real-time alerts to audit her own apps weekly, almost without thinking. The alert hits, she taps into iOS Settings from Guard, revokes, and moves on. It's not a burden anymore; it's a reflex.
The clipboard safety check (also in Personal Pro) feeds into this same tension. Apps ask to read your clipboard, often for legitimate reasons, but sometimes to log what you've copied. We surface that, and when it changes, you know.
Why we didn't call it a security tool
Guard is not an antivirus. It's not a VPN. It's not a camera or microphone monitor, because iOS doesn't expose that telemetry to third-party apps in the first place. If you want to know whether an app is siphoning your location data, Guard shows you when it requests access. What happens after that lives in iOS's hands.
The alerts are honest about this boundary. They tell you when a permission request lands, not whether the app is malicious. They help you notice change, not prove intent. That's intentional. We built Guard for privacy-conscious people aged 25 to 45, parents worried about their children's devices, and professionals who need to audit their own security posture. None of them need reassurance; they need information.
The permission breakdown chart (also Personal Pro) lets you see the full permission profile across your apps, not just the 12 demo set. That transparency matters more than a vague security score ever could.
The moment it clicked
Three weeks after we shipped real-time alerts, a user sent another email. She'd been working late, her phone buzzed, and Guard had caught an app re-requesting microphone access after she'd revoked it months earlier. She'd gone into iOS Settings, revoked it again, and updated her awareness. No drama. No cleanup required. Just a person staying in control of her own device.
That's what the alerts do. They're not flashy. They don't solve the bigger problem of app surveillance or data brokers or corporate incentives. But they turn privacy from something you set once and forget into something you can actively manage. And on a device you carry every day, that difference matters.
If you've revoked a permission from an app and never checked whether it came back, you've been in that gap we were trying to close. Do you know which app on your phone has asked for location access most recently?