Booking.com B.V.
bd_098a048b0df21d9a · schema v1 · pii pii-v1
Full breach record for Booking.com B.V. →2 incidents on fileRegulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
The AP (The Netherlands) issued a investigation regarding Booking.com B.V. A fine of EUR 475,000 was imposed. Outcome: Violation Found. GDPR articles: Article 33(1) GDPR.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Dec 10, 2020
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (1) · sorted by filing gap
- Massachusetts State AGbd_72a4ca5ccbe8de482019-01-10 · +700dCandidate
Filing propagation · 2 filings
View merged incident ↗Pattern: first filing Jan 10 (MA), last Dec 10 — a 700-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- data categories
- cross-border scope
- outcome + articles (decisions)
- discovery date
- affected count
- notification clock
See the underlying breach notice, if filed.