Anything you add to the Waze map or report within the app (such as traffic incidents or road edits) may be publicly visible to other users and can be used by Waze and shared with third parties to improve its services.
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 establishes that user-contributed map data and incident reports are treated as community data that may be publicly visible and commercially used, meaning contributions are not private communications but shared content subject to broad use rights.
Interpretive note: The policy does not specify whether GDPR erasure rights extend to user-contributed map data that has been incorporated into the public map, creating uncertainty about the practical scope of deletion rights for EU users.
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 user map contributions and incident reports may be publicly visible and shared with third parties; users who contribute location-tagged content should be aware that such contributions may be linked to their activity and disclosed beyond the Waze platform.
How other platforms handle this
While the categories of Restricted Content above provide a clear framework, we may also moderate other types of Content in response to evolving challenges posed by advancements in Machine Learning. As we assess such Content, we hold consent as a core value, ensuring our approach remains thoughtful, ...
Mistral AI may monitor use of the Mistral AI Products through automated means in accordance with the Usage Policy. This monitoring is conducted to ensure compliance with Mistral AI's terms and policies, and to maintain the security and integrity of Mistral AI Products. We reserve the right to review...
By submitting, posting or displaying Content on or through the Services, you give Miro a worldwide, non-exclusive, royalty-free license (with the right to sublicense) to use, copy, reproduce, process, adapt, modify, publish, transmit, display and distribute such Content in any and all media or distr...
Monitoring
Waze has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 10 platforms.
"When you contribute to Waze, such as by reporting incidents, editing the map, or submitting other user-generated content, this information becomes part of the Waze community and may be publicly visible. We may use this information to improve our services and may share it with third parties.— Excerpt from Waze's Waze Privacy Policy
1) REGULATORY LANDSCAPE: User-generated content that is location-tagged may constitute personal data under GDPR if it is linkable to an identifiable individual, requiring a lawful basis for its processing and public disclosure. CCPA personal information definitions may encompass location-tagged contributions if they are associated with a user's profile. 2) GOVERNANCE EXPOSURE: Low to Medium. The provision is relatively standard for community mapping platforms, but the combination of public visibility and third-party sharing of location-tagged contributions creates a potential de-anonymization risk if contributions can be correlated with user identity. 3) JURISDICTION FLAGS: EU/EEA users contributing location-tagged content should be aware that GDPR rights including erasure may apply to such contributions if they constitute personal data, though the policy does not specifically address the erasure of user contributions from public map data. 4) CONTRACT AND VENDOR IMPLICATIONS: Third parties receiving map edit and contribution data should be assessed in the context of Waze's data sharing agreements to ensure that downstream use is consistent with the purposes disclosed to users. 5) COMPLIANCE CONSIDERATIONS: Compliance teams should assess whether the public visibility of user contributions is adequately disclosed at the point of contribution within the app interface, and whether users can delete or correct their contributions in exercise of GDPR rights.
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 establishes that user-contributed map data and incident reports are treated as community data that may be publicly visible and commercially used, meaning contributions are not private communications but shared content subject to broad use rights.
The policy states that user map contributions and incident reports may be publicly visible and shared with third parties; users who contribute location-tagged content should be aware that such contributions may be linked to their activity and disclosed beyond the Waze platform.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Waze.