Guard and Truecaller solve different privacy problems. Here's which one you actually need.
Last month, a user emailed me asking whether Guard was 'like Truecaller but for iPhones.' I read the question three times. It was a genuine mistake, but it crystallised something I'd been thinking about since we launched: people often conflate any privacy tool with any other privacy tool, even when they're solving entirely separate problems.
The caller ID thing is solved. The permission thing is not.
Truecaller does one job excellently: it identifies spam and unwanted calls, and it's been doing that for years across iOS and Android. When a number rings your phone, Truecaller tells you whether it's a scammer, a marketing outfit, or a business you've dealt with. That's valuable. Most of us get nuisance calls.
Guard doesn't touch caller ID. We're not interested in it. What we noticed instead was that people install apps for genuine reasons - a banking app, a fitness tracker, a photo editor - but they have almost no idea what those apps are actually permitted to access. iOS shows you the permission prompt when you first install something, but after you tap Allow, it's gone. You forget. The app sits on your phone, holding permission to your contacts, your calendar, your location, your clipboard.
Those two problems exist in completely different spaces. Truecaller solves interruption. Guard solves opacity.
Why a permission audit isn't a caller ID service (and shouldn't be)
When we were building Guard, we made a deliberate choice: we'd show you permissions for 12 common apps upfront in the Free version. A demo set. Banking apps, social networks, photo editors, maps. The kind of software most people have installed and never think about.
We didn't try to scan every app on your phone because iOS doesn't allow that. Apple's sandbox is deliberate and protective. Third party apps cannot audit other third party apps' live permissions. So instead of pretending to omniscience, we educate. We show you real examples. We explain the risks. And when you see something that looks exposed, you can tap the app name and jump straight into iOS Settings to revoke permission yourself.
That's fundamentally different from what Truecaller does. Truecaller has access to a massive database of phone numbers and caller patterns. It's network data. Guard doesn't need a network. It needs you to understand what you're agreeing to every time you open an app.
The real insight: most people don't know what permissions they've given
In the first week after launch, we had a customer message me directly. She'd used Guard, tapped through her installed apps, and realised her maps app had location access, her notes app had microphone access, and her camera roll app had calendar access. None of that made sense to her. She didn't remember approving those things. Had she? Probably. In a permission prompt, years ago, without thinking.
She went into Settings and revoked most of them. The apps still worked. iOS lets you deny permissions and apps gracefully degrade. A maps app doesn't need microphone access. A notes app doesn't need calendar access. Nothing bad happened. She just got cleaner.
That's what Guard is for. It's not about scary headlines or threat detection. It's about the quiet realisation that you've handed apps more access than they need, and you can take some of that back. Truecaller would tell you which calls to ignore. Guard tells you which permissions to question.
When you graduate from the free dashboard
Our Free tier works for a lot of people. Twelve apps, a privacy risk score, the ability to revoke. But some users want more texture. They want real time alerts when an app's permissions change (which happens sometimes, quietly, after an update). They want to know what the clipboard traffic looks like. They want a breakdown chart showing which apps have what permissions. We built Personal Pro for that.
And then parents came to us with a different problem: they wanted to monitor permissions across their kids' devices. So we added Family tier, which gives you a 6-device family hub where you can see and manage permissions across your household.
None of this competes with Truecaller. None of it is even adjacent to Truecaller. Truecaller is about your incoming calls. Guard is about your installed apps and what they're watching.
The conversation we should be having instead
I think the real question isn't 'Guard or Truecaller.' It's 'Do you want to know what your apps can see, and do you want to change it?' If the answer is yes, Guard is built for you. If you're tired of spam calls, you want Truecaller. If you want both, install both. They're not competing for the same screen real estate in your brain.
What matters is that people stop being passive about privacy. Not paranoid. Passive. Most of us have never sat down and thought about what we've allowed. We've never asked: does my photo editor really need my contacts? Does my fitness app need my location when it's not running? Does anything need access to my clipboard?
Guard asks those questions for you. Truecaller asks different questions about different kinds of interruption. Both are worth the mental cycles, but they're not alternatives. They're answers to different worries.
The next time you unlock your phone and see an app ask for permission to something new, pause for a second. Does it make sense? That moment of friction is what Guard exists for. And if you're tired of unknown numbers calling, Truecaller's a separate conversation. Which one matters more to you today?