Google Maps Security & Privacy Scorecard
by Google · iOS
Location, search, and usage data are collected and shared with Google, Firebase, and Adjust for analytics and ad attribution. Advertising identifiers are used via Google Mobile Ads and Apple SKAdNetwork. The app includes consent management and privacy-preserving attribution paths, and several Firebase data collection features are explicitly limited.
Best for
Everyday navigation with standard Google analytics
Findings
- 0 critical
- 0 high
- 6 medium
- 4 low
- 6 info
1 issue identified across security and privacy analysis.
Top security issues
- WKWebView JS bridge transmits Folsom vault encryption keys without origin guard, enabling potential key exfiltration if WebView navigation is not strictly isolated
- App Transport Security globally disabled via NSAllowsArbitraryLoads=true with no per-domain exceptions, permitting cleartext HTTP for all network connections
- Keychain items stored with deprecated kSecAttrAccessibleAlways accessibility class, readable on jailbroken devices without passcode or unlock
Top privacy issues
- 49 app scheme queries used to enumerate installed apps, linked to persistent Google Account GAIA ID and transmitted via Clearcut analytics pipeline
- All behavioral events (navigation, location, search, Gemini interactions) linked to persistent GAIA/Zwieback identifier spanning entire Google product cross-profile
- IDFA transmitted to Google Ads conversion endpoint without confirmed ATT authorization gate
Full analysis
Google Maps
What This Means for You
Your location, navigation history, search queries, and the list of apps installed on your phone are continuously linked to your Google Account and used to build a profile that spans all Google services.
Recommendation: Acceptable with Awareness
Settings that permit unencrypted connections and an unguarded in-app browser key exchange create some theoretical risk. Core navigation features are legitimate and well-implemented, but your activity is persistently linked to your Google Account identity across all Google products. Users who understand and accept Google's cross-product data practices will find this a capable, feature-rich tool.
Best For: Users already invested in the Google ecosystem who accept Google's cross-product data practices in exchange for deep integration and navigation features.
Key Findings
Data Security - 3 findings (1 medium, 1 low, 1 info)
Network Security - 1 finding (1 medium)
Code Safety - 6 findings (2 medium, 2 low, 2 info)
Privacy - 6 findings (2 medium, 1 low, 3 info)
Privacy Concerns
What Data is Collected
- Location data: Collected continuously in the background, even when the app is not open
- Behavioral data: Navigation sessions, search queries, place interactions, and Gemini AI conversations
- Device inventory: The list of apps installed on your phone (up to 49 apps queried)
- Advertising identifiers: Your device's advertising ID, used for ad conversion tracking
- Account identity: All of the above is linked to your Google Account across every Google service
Third-Party Data Sharing
The following third parties may receive your data:
- Google Clearcut (CCT) - First-party analytics pipeline linking all events to your Google Account identifier
- Firebase Analytics - App behavior reporting (screen auto-reporting disabled)
- Firebase Crashlytics - Crash and error reporting
- Adjust - Advertising attribution, with a consent-gated tracking path implemented
- Google Mobile Ads / AdServices - Ad conversion tracking using your device's advertising ID
- Apple SKAdNetwork - Privacy-preserving ad attribution (implemented as an alternative path)
Understanding the Scores
Security: 88/100
Privacy: 82/100
Security Breakdown
- Data Security: 91/100 - Account data is stored with strong protection on device; a small number of items use an older accessibility setting that permits access while your phone is locked
- Network Security: 87/100 - Most connections use secure channels, though a global setting permits unencrypted connections when no other restriction applies
- Code Safety: 89/100 - The app is generally well-built; some internal test configurations and staging service references remain in the production version
Privacy Breakdown
- Data Collection: 83/100 - Extensive location, behavioral, and device data is collected to power navigation features and fuel Google's broader data platform
- Data Sharing: 91/100 - Sharing with third parties is focused on core service and advertising partners, with privacy-preserving alternatives implemented
- User Control: 90/100 - Meaningful consent controls for advertising and data collection are present, including support for Apple's privacy framework
Positive Security Features
- Multiple Firebase automatic data collection settings are explicitly disabled, narrowing what Firebase gathers without user action
- Consent management pages are integrated into the app for GDPR and privacy compliance
- Privacy-preserving ad attribution via Apple's SKAdNetwork is implemented alongside traditional tracking
- Advertising tracking uses a consent-gated mechanism that respects opt-out choices
- Clipboard access for navigation links is explicitly disabled, preventing background clipboard reads
- Device integrity verification is implemented to protect against unauthorized service access
Areas for Improvement
GDPR / CCPA Compliance
The app's privacy practices could be strengthened by:
Narrowing the App Inventory Scope
The 49 app scheme queries go well beyond what is needed for navigation handoffs. Reducing this list to only the apps Maps needs to hand off directions to would limit the behavioral profile that can be built from your installed apps.Clearer Disclosure of Cross-Product Profiling
The linking of navigation behavior, location history, and search queries to a persistent Google Account identifier that spans all Google services could be surfaced more prominently in the app's privacy disclosures, so users can make a fully informed choice.
Security Enhancements
Restrict the Global Network Security Exception
Rather than disabling encrypted connection requirements for all network activity, the exception should be narrowed to only the specific services that require it. This would ensure all other connections benefit from transport security enforcement.Strengthen On-Device Account Data Protection
Some account data stored on your device uses an older accessibility setting that allows access even when your phone is locked. Updating these items to require the device to be unlocked would improve protection if your phone is lost or accessed without your knowledge.
Technical Context
App Type: Mapping, navigation, and local discovery - high location and identity sensitivity
Classes Analyzed: 313
Third-Party Services: Google Clearcut, Firebase Analytics, Firebase Crashlytics, Adjust, Google Mobile Ads, Apple SKAdNetwork, Spotify iOS SDK, TensorFlow Lite, and others
Context Tags: location, camera, ads, analytics, social
About This Analysis
This security analysis was conducted by CITT (Can I Trust That), an independent security analysis service. We perform static code analysis on iOS applications to help users make informed decisions about app security and privacy.
App Details
Developer: Google LLC
Version: 26.16.0 (Build 26.16.0.8989542150)
Analysis Date: 2026-04-18
Package: com.google.Maps
Analysis Limitations
- Static analysis only (code review without running the app)
- Based on iOS app version 26.16.0 analyzed on 2026-04-18
- May not reflect server-side security controls
- Cannot detect all runtime behaviors
Versions & scan history
| Scan | Date | Overall score |
|---|---|---|
| #3 (current) | 84/100 |