Churchill Downs Technology Initiatives Company
ent_1a3669fb2b26b727dbcc4add
Disclosures
4
State AG · 4 jurisdictions
Multi-filing incidents
2
incidents joining 2+ filings here
Max affected reported
950
nationwide · State AG ME
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Churchill Downs Technology Initiatives Company
- Normalized
- churchill downs technology initiatives— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- Maine State AGas victim2020-10-30
Churchill Downs Technology Initiatives Company reported an external system breach (hacking) occurring between September 5, 2020, and October 2, 2020. The incident compromised the personal information of 950 individuals, including 4 Maine residents. Acquired data included names combined with financial account or credit/debit card numbers (including security codes, access codes, passwords, or PINs). The company provided written notification to affected consumers on October 30, 2020.
- Massachusetts State AGas victim2020-10-30
Churchill Downs Technology Initiatives Company reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2020-10-30. 20 Massachusetts residents were affected. The report records the breach type as electronic.
- New Hampshire State AGas victim2012-09-04
Churchill Downs Technology Initiatives Company (dba TwinSpires.com) notified the NH AG of a data breach discovered on August 3, 2012. Unauthorized access exposed names, emails, DOBs, and hashed SSNs for approximately 370 NH residents. Notices mailed September 4, 2012. Response included forensic investigation, legal counsel, credit bureau notification, and 1-year Experian identity protection.
- California State AGas victim2012-09-04
Churchill Downs Technology Initiatives Company dba TwinSpires reported a data breach to the California Attorney General. The breach occurred on August 3, 2012. The attached consumer notification letter was empty, so specific details regarding data types, affected counts, and response actions are not available in this filing.