Because Waze is owned by Google, the data Waze collects about you may be combined with your data from other Google products like Search, Maps, or YouTube, and used according to Google's broader privacy policy.
This analysis describes what Waze's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision authorizes the transfer of Waze-specific location, behavioral, and device data to Google's broader data infrastructure, where it may be integrated with data from other Google services to build a more comprehensive user profile.
Interpretive note: The policy does not specify whether Google acts as a joint controller or data processor with respect to Waze data, creating ambiguity about the applicable legal framework governing this data combination under GDPR.
The updated policy now explicitly discloses that Waze periodically collects all phone numbers stored on your device's contact book as part of the 'find friends' feature. According to the revised term…
The updated policy removes explicit language describing how Waze collects phone numbers from device contact books and integrates social network accounts. Previously, the policy stated that Waze would…
The updated privacy policy now explicitly discloses that Waze periodically collects all phone numbers stored in your device's contact book as part of the 'find friends' feature. According to the poli…
The policy states that Waze data including precise location and driving behavior may be combined with a user's activity across all other Google services, meaning the data scope extends well beyond navigation use; users who are concerned about cross-service profiling should review Google's privacy settings via the Google Account dashboard.
Cross-platform context
See how other platforms handle Google Data Integration and Cross-Service Data Combination and similar clauses.
Compare across platforms →Monitoring
Waze has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"Waze is a member of the Google family of companies. We may share information we collect with Google and other members of the Google family of companies. Google may combine information it collects from Waze with information from other Google services and use it in accordance with Google's privacy policy.— Excerpt from Waze's Waze Privacy Policy
1) REGULATORY LANDSCAPE: This provision engages GDPR Article 26 (joint controllers) or Article 28 (processor relationships), depending on how the Waze-Google data relationship is legally structured; the policy does not clearly specify whether Google acts as a joint controller or processor with respect to Waze data, which may require further disclosure under GDPR transparency obligations. The combination of Waze location data with Google account data for advertising purposes may engage ePrivacy Directive requirements and GDPR consent obligations for EU users. CCPA/CPRA requires disclosure of cross-context behavioral advertising uses of personal information. 2) GOVERNANCE EXPOSURE: High. The scope of authorized data combination is broad; the policy delegates the legal basis and purpose framework for combined data to Google's own privacy policy, which compliance teams must independently review. This delegation of purpose specification may create transparency gaps under GDPR's specificity requirements for lawful basis disclosures. 3) JURISDICTION FLAGS: EU/EEA regulators have previously scrutinized intra-Google data sharing and combination practices; this provision may require evaluation under GDPR adequacy and transfer mechanism requirements if data flows cross jurisdictions outside the EEA. UK ICO would apply equivalent scrutiny post-Brexit. California users have CPRA rights regarding cross-context behavioral advertising that may be relevant to how combined data is used. 4) CONTRACT AND VENDOR IMPLICATIONS: Enterprises assessing Waze as a business tool should note that data governance obligations do not end at the Waze service boundary; the Google family data sharing structure means that data handling obligations extend to Google's broader infrastructure, requiring review of Google's Data Processing Addendum in addition to Waze's own terms. 5) COMPLIANCE CONSIDERATIONS: Legal teams should map the data flows from Waze to Google and identify the specific legal instruments (DPAs, Standard Contractual Clauses, or Binding Corporate Rules) governing intra-group transfers for EU data subjects. The ambiguity regarding joint versus separate controller status should be resolved in internal documentation and reflected in Records of Processing Activities (RoPA) maintained under GDPR Article 30.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Watcher: 10 platforms + same-day alerts. No credit card required.
Professional Governance Intelligence
Need to monitor specific governance provisions?
Professional includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
This provision authorizes the transfer of Waze-specific location, behavioral, and device data to Google's broader data infrastructure, where it may be integrated with data from other Google services to build a more comprehensive user profile.
The policy states that Waze data including precise location and driving behavior may be combined with a user's activity across all other Google services, meaning the data scope extends well beyond navigation use; users who are concerned about cross-service profiling should review Google's privacy settings via the Google Account dashboard.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Waze.