Google Maps
Google Maps is a feature-rich navigation app with legitimate location needs, but it collects 6 trackers including Meta SDK and retains background location access even when not navigating. The persistent location profiling and Meta ad-targeting integration warrant caution for privacy-conscious users.
How we got to 41.
Firebase, Meta SDK (behavioral ad targeting), FCM, Google Sign-In, Maps SDK
Continuous location collection enables movement pattern analysis and behavioral inference
READ_CONTACTS, RECORD_AUDIO, and CAMERA not core to navigation
Meta SDK means location patterns and device identifiers flow to Meta's ad platform
Permanent searchable record of movements enabled by default
Location and search data monetized through ad networks
Google - mature privacy infrastructure, GDPR compliance mechanisms
Data deletion, access requests available; compliance is reactive
Hidden inside the code.
What it asks for.
Continuous GPS tracking even when not navigating
Contact list harvesting - not needed for navigation
Voice search feature - continuous audio capability
Starts on device boot for background location tracking
Keep reading.
What is a tracker in an app, and why should you care
Trackers are code libraries hidden inside apps that collect your data for third parties. Here is how they work, what the...
Why does this app need microphone permission?
Why do apps request microphone, location, or contacts access they don't need? A field guide to Android permission creep ...
Similar risk profiles.
Scan Google Maps yourself.
Get the full report on your device - with real-time DEX analysis, permission auditing, and breach monitoring. Free, no account needed.