Summary
Generated by a model from the captured document; not read by a person
The submitted document is a security interstitial page generated by AWS WAF rather than Booking.com's privacy statement. The page serves a bot-detection function and contains no provisions related to data collection, processing, retention, or user rights. A complete privacy policy document is required for analysis of Booking.com's data practices.
Analysis
The submitted document does not contain Booking.com's privacy policy text. Instead, it contains an AWS WAF (Web Application Firewall) bot-challenge page, which is a security interstitial served to verify that the requester is not an automated system before granting access to the actual policy. No substantive privacy policy provisions, legal bases, data collection disclosures, user rights, or governance terms are present in the provided text. As a result, no regulatory frameworks, data practices, or compliance obligations can be identified or assessed from this submission. A valid analysis requires the actual Booking.com privacy policy document text.
What this means for you
This document does not establish terms governing data collection or processing and therefore does not define user obligations or data subject rights. The submitted content is a technical access control mechanism rather than a privacy policy, and contains no provisions affecting user data handling or consent requirements.
2 important changes detected
20 versions captured · Latest change detected by ConductAtlas: October 2026
What changed
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.
Why this matters
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.
View full change record →
What changed
Booking.com restructured its privacy notice to reorganize sections and clarify data collection practices. The updated policy expands the description of personal data collected to explicitly include date of birth, current location, work travel status, traveling companion names and dates of birth, dietary and accessibility preferences, and passport/ID information for certain trips. The policy also reorganizes how it describes data sharing and processing purposes, separating 'Trip & payments management' from 'Platform services & operations' and removing some prior marketing-focused language while adding detail about review collection and communication services.
Why this matters
The updated privacy notice expands the explicit disclosure of personal data Booking.com collects during trip reservations. Previously, the policy described collection of 'contact details' and 'reservation identifiers and dates' in general terms. The revised policy now itemizes collection of date of birth, current location, whether you are traveling for work, names and dates of birth of traveling companions, dietary and accessibility preferences, and passport or ID information for certain trip types. The policy also clarifies that this data is used for trip and payment management, platform operations, and review collection. These are disclosures of existing or expanded collection practices; the policy does not state when this expanded collection began or whether it applies retroactively to prior bookings.
View full change record →
No provisions indexed for this document yet.
Archival ProvenanceSource & Archival Record
This version captured
October 21, 2026 00:34 UTC
Last successful capture
October 21, 2026 00:34 UTC
Capture Method
Automated scheduled archival capture
Document ID
CA-D-000238
Version ID
CA-V-007732
SHA-256 (extracted text, extractor v5)
e7fbb3932699c9cf251e05c6e35cc96821aad0980be0ec1f49c0c71c9ef4cbd6
Archived bytes SHA-256 (anchor)
ebaf403a9e8aaebbd821002d73a815d880c8998fa8c6754a2cca94687599ef5f
✓ Snapshot stored
✓ Archived bytes anchored (verified Oct. 21, 2026)