Booking.com's privacy statement now explicitly states that users with an account can make some personal data corrections directly within their account, rather than only through manual requests to the company. This clarifies an existing capability and provides users with a more direct method to update their information.
The updated privacy statement clarifies that users with a Booking.com account can correct some of their personal data directly within their account settings, in addition to requesting corrections from the company. This provides account holders with a more convenient method to manage their information without requiring manual contact with Booking.com's data protection team.
→ Log into your Booking.com account and review available settings to correct personal data directly.
Clarifies that account holders can correct some personal data directly in their account settings.
This change record describes what was added, removed, or modified in the document. Analysis reflects what the updated agreement states or permits. It does not constitute a legal determination about enforceability. Applicability may vary by jurisdiction. Methodology
This change is a clarification of existing functionality rather than a material policy shift. It documents a self-service capability for account holders to correct personal data, which aligns with GDPR Article 16 rights to rectification. …
Regulatory exposure, obligation change, escalation trigger, board-ready language, and recommended action for legal and compliance teams.
Unlock the full institutional analysis — InsightConductAtlas provides verified policy intelligence sourced directly from platform documents. All analysis is intended to support, not replace, legal and compliance review. Record CA-X-005718.
Booking.com restructured its privacy notice to reorganize sections and clarify data collection practices. The updated policy expands the description of …
Get the weekly coverage letter
Companies change their terms without announcing it. We capture governance documents, compare each new version with the last, and publish what changed, with the source text behind it. One email a week on what we found and what we could not reach.
Get alerted when this policy changes again, including what changed and why it matters.