Confirmed breach. Intrusion Aug 10, 2016–Mar 9, 2017, discovered Jun 16, 2017 — the first regulatory filing landed 13 days later. 1 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksCalifornia✓ CA 60-day OK · 13dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Affected (total reported)
1
Data types
2
Identity (basic) · Financial account
Jurisdictions
2
CA MT
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 10, 2016 → Mar 9, 2017
When the intrusion reportedly occurred, per the linked filings
Google Inc. notified California AG that unauthorized access to Sabre Hospitality Solutions' SynXis CRS compromised hotel reservation data for Google travelers. Incident occurred Aug 2016–Mar 2017. Data included names, contact info, and payment card data. Google engaged cybersecurity firm and offered 24 months credit monitoring.
CA 60-day OK · 13d
🦬Montana State AGMost recentlinked via multistate filing link · 95%
Google reported a data breach to the Montana Attorney General. The breach was reported on 2017-07-06. The breach occurred from 8/10/2016 to 3/9/2017. 1 Montana residents were affected.
Affected (this filing): 1
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.