Founder Resources

How to Protect your Privacy on Android

Akshay Singh Apr 18, 2020 10 min read

Are apps on your phone spying on you? App privacy risks explained

You’ve handed your phone more personal information than almost anyone in your life. Your location, your contacts, your photos, your microphone, your banking app sessions — all of it accessible to the apps you install. Most of the time, you don’t think twice about it.

If you’re a startup founder, that trust cuts both ways. You’re a user who grants permissions carelessly, and you may also be building the app on the other end of that request. This post covers both sides: how app privacy risks actually work and what to do about them as a user, and — because the second half of this audience is building products, not just using them — what founders specifically need to get right before their own app ever asks a customer for a permission.

App-based privacy risks are real, growing, and increasingly sophisticated. In 2025, Google blocked over 1.75 million policy-violating apps from reaching the Play Store and its Play Protect system identified 27 million malicious apps distributed outside it — up from 13 million in 2024. That’s not a niche problem. It’s a mass-scale one, and it sits on both sides of every app relationship: the user granting access, and the company requesting it.


How Do Apps with Privacy Risks Actually Harm You?

There are two distinct categories of risky apps, and understanding the difference is the first step to protecting yourself — or to not becoming one of them.

Type 1: Apps That Misuse Data You Willingly Provide

When you sign up for an app, you often fill in details — name, email, profession, age, interests. You provide this voluntarily, assuming it’s used to personalise your experience. In most cases, it is. But in a significant number of cases, that data is packaged and sold to third-party advertisers, data brokers, or other companies without meaningful disclosure.

A practical example: you download a job-hunting app and enter your profession and salary expectations. That app sells this data to recruitment agencies and financial services companies. Suddenly you’re receiving targeted cold calls, promotional emails you never signed up for, and ads that feel unsettlingly specific. You didn’t give informed consent for any of that — but technically, buried in a terms-of-service document you didn’t read, you did.

Type 2: Apps That Collect Data Without Your Awareness

This category is significantly more dangerous. These apps request access to phone hardware and services — camera, microphone, contacts, location, screen recording — and then use that access in ways users would never expect or agree to if asked plainly.

Consider this scenario: you download what appears to be a simple utility app. During setup, it requests microphone and screen recording permissions. You grant them without much thought. From that point, the app has the technical ability to record your screen whenever it runs in the background — including when you open your banking app and enter your credentials.

This isn’t hypothetical. Security researchers have repeatedly found apps — including some that passed initial Play Store review — that quietly harvest data through overly broad permissions. In 2025, Google’s systems blocked over 255,000 apps from requesting excessive or unnecessary access to sensitive user data. The fact that this number has dropped from around 1.3 million in earlier years reflects improving detection, not a disappearing threat.


How to Avoid Downloading Dangerous Apps

The most effective protection happens before you install anything.

  1. Check what permissions an app requests before installing. The Play Store and App Store show an app’s data safety section before you tap install. If a flashlight app wants access to your contacts and microphone, that’s a red flag.
  2. Ask whether the permission makes sense for what the app does. A navigation app needs location. A calculator does not. A recipe app needs nothing beyond storage. Any permission that doesn’t logically connect to the app’s function should make you pause.
  3. Don’t provide personal details to apps you don’t trust or regularly use. If an app asks for your full name, date of birth, or financial information and you’re unsure why it needs that, don’t fill it in.
  4. Only download apps from official stores. Sideloading — installing from websites, messaging apps, or third-party stores — bypasses the security review process entirely. Play Protect identified 27 million malicious sideloaded apps in 2025 and blocked 266 million risky installation attempts.
  5. Check the developer’s reputation and download count. An app with tens of thousands of reviews and millions of downloads from a recognisable developer carries far lower risk than a newly published app with no track record.
  6. Stay aware of apps removed from official stores. If a removed app is still installed on your phone, delete it. Cybersecurity publications regularly report on Play Store removals if you want to stay current.

How to Check and Fix App Permissions on Android Right Now

Already have apps installed that you’ve never checked? Here’s how to audit what they can access and revoke anything they shouldn’t have. This works on Android 10 and above, though exact menu names vary by manufacturer.

  1. Open Settings on your Android phone.
  2. Tap Privacy (sometimes under Security & Privacy).
  3. Tap Permission Manager.
  4. You’ll see permission categories: Camera, Microphone, Location, Contacts, Storage, Phone, and more.
  5. Tap any category to see which apps have been granted that permission.
  6. Tap any app to change its permission level: Allow, Allow only while using the app, or Deny.
  7. For a full view of a single app’s permissions: go to Settings → Apps, select the app, tap Permissions.

Focus on: Camera, Microphone, Location, and Contacts. Any app with access to these that doesn’t clearly need them for its core function should be restricted or uninstalled.


Google Play Protect — The Built-In Defence Most Users Never Check

Google Play Protect scans over 350 billion apps every day across Android devices, checking for malicious behaviour — including apps that were initially clean but later updated to include harmful code.

  1. Open the Play Store.
  2. Tap your profile icon (top right).
  3. Tap Play Protect.
  4. Check the status of the last scan. Tap Scan to run one manually.

Play Protect’s Enhanced Fraud Protection mode blocks installation attempts from risky sources, particularly links in messaging apps or browsers that push installs outside the Play Store. Make sure it’s enabled in your Play Protect settings.


The Sideloading Problem

Sideloading — installing apps from outside the Play Store or App Store — is now the dominant vector for malicious apps. This includes APK files shared over WhatsApp or Telegram, random websites, and unofficial app stores.

Play Protect identified 27 million new malicious sideloaded apps in 2025, roughly double the 13 million found in 2024. Bad actors are shifting away from the Play Store precisely because its own review defences have improved, and sideloading remains largely unguarded by comparison.

The simple rule: don’t install apps from outside the Play Store or App Store unless you have a specific, well-understood reason to do so — and even then, research the source first.


If You’re Building an App: Your Permission Requests Are Data Collection Too

Everything above describes the threat from a user’s side. If your startup has an app — or is about to build one — you’re on the other side of that same exchange, and the DPDP Act now makes that exchange a legal one, not just a trust one.

The permission you request is a consent request, not a technical formality

Under the DPDP Act, asking a user for camera, location, or contacts access is a form of collecting personal data, and it needs the same standard of informed, specific consent as any other data collection. A generic “this app needs the following permissions to function” screen shown once at install, with no explanation of why, does not meet that bar. If your app requests location access, the user should understand, in plain language, why — delivery tracking, nearby search results, fraud checks — before they grant it.

The practical fix is cheap: add one line of context to each permission prompt explaining what it’s for and what happens if the user declines. This is a UX change, not an engineering one, and it materially improves both consent quality and grant rates, because users are more likely to allow a permission when they understand its purpose.

Request the minimum, not the convenient maximum

It’s common for early-stage apps to request a broad set of permissions upfront — camera, microphone, contacts, location — because a future feature might need them, or because a template or boilerplate included them by default. Every permission you don’t currently use for a shipped feature is pure liability: it increases your data collection footprint, your breach exposure, and your compliance surface, with no corresponding benefit to the user or the product.

Request permissions contextually, at the moment a feature actually needs them, rather than all at once at first launch. This is both better practice and, increasingly, what app store review guidelines expect.

Third-party SDKs collect data on your behalf, often more than you realise

Analytics SDKs, ad networks, crash reporting tools, and attribution platforms are standard in most startup apps, and nearly all of them collect device identifiers, usage data, and sometimes location or contact data as part of their normal operation — frequently more than the feature they provide strictly requires. Google’s own 2025 enforcement blocked 255,000 apps specifically for requesting excessive access to sensitive data; a meaningful share of that excess access traces back to bundled third-party SDKs rather than the app developer’s own code.

Under the DPDP Act, the app owner is the Data Fiduciary, not the SDK vendor. If an embedded SDK collects data your privacy notice doesn’t disclose, that’s your compliance gap, not theirs. Before adding any SDK, check its documented data collection scope, confirm it’s reflected in your app’s Play Store and App Store data safety labels, and make sure your privacy notice covers it.

Your data safety label is now a compliance document, not marketing copy

Both the Play Store’s Data Safety section and Apple’s App Privacy label are frequently filled out quickly and inaccurately at launch, then never revisited as the app adds features or SDKs. Regulators and users increasingly treat these labels as the app’s own disclosure of its data practices — which means an inaccurate label is not a minor oversight but a direct discrepancy between what you told a user and what your app actually does.

Review your data safety labels every time you add a new SDK, a new permission, or a new data collection point. This takes minutes and closes one of the most common and easily avoidable compliance gaps in early-stage apps.


Frequently Asked Questions

Q: Can apps spy on you through your camera or microphone without you knowing?
A: Technically yes, if the app has camera or microphone permission. Android 12 and above show a green indicator dot at the top of the screen whenever an app is actively using the camera or microphone, making unexpected activity easier to spot. Revoking permissions from apps that don’t need them is the most effective protection.

Q: Is it safe to download apps from the Google Play Store?
A: Significantly safer than other sources, but not risk-free. Google blocked over 1.75 million policy-violating apps from the Play Store in 2025, though some still slip through by initially appearing benign and adding malicious behaviour through later updates. Check permissions, reviews, and developer history before installing.

Q: What app permissions are the most dangerous to grant?
A: Camera, Microphone, Screen Recording, Location set to Always Allow, Contacts, SMS/Call logs, and Accessibility Services. Accessibility permissions are especially exploited, since they let an app observe and interact with everything on screen — a common mechanism in banking malware.

Q: Does having fewer apps make a phone more secure?
A: Yes. Every installed app is a potential attack surface, even one that’s currently legitimate but could be updated later to include malicious code. Uninstalling unused apps reduces that exposure meaningfully.

Q: What should a startup check before adding a third-party SDK to its app?
A: What data the SDK collects, whether it shares data with its own third parties, whether that’s reflected in the app’s Play Store and App Store data safety labels, and whether it’s covered in the app’s privacy notice. Under the DPDP Act, the app owner is accountable for that collection, not the SDK vendor.


Conclusion

App privacy risk is one problem viewed from two seats. As a user, the fix is the same as it’s always been: check permissions before installing, stay off sideloaded APKs, keep Play Protect active, and audit what’s already on your phone. Fifteen minutes of attention covers most of it.

As a founder, the same underlying behaviour — a permission request, an SDK, a data safety label — is now a compliance surface under the DPDP Act, not just a product decision. The apps causing the harm described above aren’t hypothetical outliers; they’re what happens when permission requests and third-party data collection go unexamined. Building the opposite habit into your own app, asking for less, explaining more, and auditing your SDKs regularly, costs very little and is the difference between being a founder who reads posts like this and a founder who ends up as a case study in one.

Have a question about a specific app, permission, or SDK you’re unsure about? Drop it in the comments.

📂 Category: Founder Resources
🏷️ Tags: data-privacy, cybersecurity, dpdp-compliance, android-tips, india-startup

Related Articles

Read next

Start Building Today

Read smarter. Build faster. Use the right tools.

Explore Founder Tools
Scroll to Top