The Settings shortcut: why we built deep-linking into Guard
Three weeks before launch, a beta tester sent us a screenshot. She'd spent twenty minutes trying to find where to disable location access for a social app, bouncing between Settings menus, getting lost, giving up. She wrote: 'I know the permission is bad. I just can't find where to turn it off.' That message shaped everything we did with the deep-link feature.
The maze nobody wants to navigate
Here's what most people don't realise about iPhone permissions: Apple makes them incredibly granular, which is good for privacy, but terrible for quick action. Location can be set to Always, While Using, or Never. Contacts and Photos have sub-permissions for read and write. Clipboard access is buried three menus deep. When you're looking at Guard and see that your messaging app wants access to your microphone, or your weather app tracks your location, the natural instinct is to switch it off right now. But then you have to close Guard, open Settings, find Privacy, locate the app name, scroll through the permission list, and toggle the right switch. Half the time, users give up before they finish. We watched this happen in testing. It frustrated us enough to rethink the entire flow.What deep-linking actually does (and what it doesn't)
When you tap a flagged permission in Guard, the app doesn't revoke anything for you. That's important to say plainly. iOS doesn't allow third-party apps to change system settings; Apple's sandbox is too tight, and honestly, that's the right call. What our deep-link does is build a URL that opens iOS Settings directly to the exact permission you need to toggle. You tap 'Revoke Location Access' in Guard, and your phone switches to Settings, navigates to Privacy, finds the app, opens Location Permissions, and you land exactly where you need to be. No hunting. No wrong turns. One tap, and you're there. The revocation itself is yours to do, by your own hand, on your own device. That matters. It means you're in control, not us. It also means you can see exactly what you're about to change before you change it. That trust is non-negotiable to us.Building for the 12-app demo set
Guard's free version shows you a dashboard of 12 common apps: Instagram, TikTok, WhatsApp, Spotify, Maps, Camera, Contacts, Calendar, Photos, Health, Reminders, and Notes. We didn't pick these apps at random. We spent weeks analysing what permissions they request, what privacy problems users actually care about, and which ones generate the most frustration in forums and support channels. The deep-link feature was built specifically for this curated set. We test each one, make sure the URL routing works on every iOS version we support, and verify that the link lands you in the right corner of Settings every time. It's not a generic solution; it's tailored to the apps that matter most to the people we built Guard for. That granularity is why the feature feels fast and purposeful instead of clunky.The privacy risk score context
The deep-link only makes sense if you know which permissions are worth revoking. That's where the Privacy Risk Score comes in. For each app in the demo set, Guard calculates a score based on how many sensitive permissions it requests, which ones are unusual for its category, and how much exposure they create if misused. If an app requests five permissions and uses maybe two of them legitimately, that shows up as a higher risk. You can see the score, understand why it's flagged, and then tap through to revoke. The system isn't about fear or alarmism. It's about information and action. We've had users tell us they were shocked to see their news app requesting Bluetooth access, or their fitness app wanting Calendar permissions. Once they saw the risk score, the deep-link made sense. It transformed from 'why would I do this' to 'I need to fix this now.'What we learned from beta feedback
The deep-link feature changed significantly between our internal testing and launch. We originally built it to handle both granted and denied permissions, thinking users might want to re-enable something. But beta testers taught us otherwise. The request was almost always in one direction: 'I want to turn this off.' We stripped out the complexity and focused on revoking. The feature got faster, the code got simpler, and the user journey became clearer. We also discovered that people wanted to revoke multiple permissions at once, but iOS Settings won't let you stay in one place and toggle five things in sequence. So Guard now lets you flag multiple apps and permissions, and you can plan your revocation session before you open Settings. It's not perfect, but it respects how iOS actually works instead of pretending it works differently. That honesty, we found, matters more than false convenience.Beyond the free tier
The deep-link to iOS Settings is a free feature. It doesn't sit behind a paywall. We made that choice intentionally. Revoking app permissions shouldn't be a premium function. If someone is going to protect their privacy, the basic tools should be accessible. That's not generosity; it's principle. Personal Pro adds real-time alerts that notify you when an app requests a new permission, which makes the revoke action even more purposeful. You get a notification, you tap it, Guard opens with the flagged permission, you deep-link to Settings and switch it off. The flow works because each layer has a specific job. But you don't need Pro to use the deep-link itself. You just need curiosity and a few minutes to audit what you've installed.The deep-link feature is small, almost invisible. It's a tap that opens another app. But it solves a real problem: the gap between knowing a permission is wrong and actually doing something about it. When that beta tester finally found the location toggle and switched it off, she sent us a two-word message: 'Found it.' Simple as that. Have you looked at what permissions your own apps are actually using, and if you had a direct path to revoke them, would you?