“No tracking” can mean very different things. Here’s a clear, practical way to understand it and choose apps that respect your privacy on Android.
Project BS
Privacy-first apps
“No tracking” sounds simple. In practice, it’s often vague—or used as marketing shorthand.
This guide explains what tracking usually is, what it isn’t, and how to do a quick, realistic check before you install an app on Android. No paranoia, just clarity.
If an app truly avoids tracking, it generally means:
That said, an app can still be functional without tracking while keeping minimal technical logs (for example, local error logs). The details matter.
In mobile apps, tracking typically refers to collecting data about how you use the app, then using it to:
Tracking becomes more concerning when:
An app might store things like your settings, recent actions, or preferences on your device to work properly. That’s not tracking by itself.
Some developers use crash reporting to fix bugs. This can be privacy-friendly if it’s minimal and avoids identifiers—or it can be very invasive if it includes identifiers and detailed usage trails. You want to know what is sent, and to whom.
Not selling data doesn’t automatically mean “no tracking.” An app can still track usage for internal analytics or share data with partners without “selling” it.
Here are the big buckets you’ll see in real apps:
If an app is ad-supported, it often includes ad SDKs that collect usage signals to optimize ad delivery and measure performance.
Used to measure installs and conversions from campaigns (“This user installed after clicking ad X”). This often relies on device signals and identifiers.
Events like:
Some systems rely on persistent IDs or device fingerprint-like signals. Even when “anonymous,” persistent identifiers can still behave like tracking.
You don’t need to be an expert. Use a few signals together.
If you can’t use basic features without signing up, the app is more likely to tie activity to an identity.
Permissions aren’t automatically bad—but mismatches are a red flag. Example: a unit converter asking for contacts or location.
(If you want a practical permissions breakdown, see: Android App Permissions: A Minimal Guide.)
Apps that work without constant network access often have less incentive (and less ability) to transmit usage events.
Local-first is not a guarantee of privacy, but it’s often a good sign. (More here: Local-First Apps: Pros, Cons, and When It Matters.)
It can be useful, but remember: it’s typically self-reported. Look for consistency with the app’s purpose.
You’re looking for:
You don’t need to read every word—just find the sections about data collection and sharing.
Even with the best intentions, many social apps require accounts and network calls. Privacy can still be strong—but “no tracking” is harder to achieve because identity and sharing are core to the product.
Offline-first reduces exposure, but it’s not a perfect guarantee. You still want permission and policy consistency.
It helps, but some subscription apps still run analytics or attribution. You still want clarity.
Privacy is about tradeoffs. For many people, the best win is: no account, minimal permissions, and no third-party trackers—especially for simple utilities.
No tracking. No private data collection.
If you prefer everyday utilities with minimal friction (no account, minimal permissions), start with a focused use-case and keep your checklist simple.
You can also follow the practical guides: