Automatic Data Processing, Inc.
ent_019de1a6845a8876d8263b206c8a5385
Disclosures
5
State AG · HHS OCR · 3 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
12,360
nationwide · HHS OCR FL
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Automatic Data Processing, Inc.
- Normalized
- automatic data processing— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- HGBOLILQXWER4SAL2I23
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- adp.com
Disclosure history (5)newest first
- 🦬Montana State AGas victim2020-02-19
ADP reported a data breach to the Montana Attorney General. The breach was reported on 2020-02-19. The breach occurred from 1/24/2020 to 2/11/2020. 2 Montana residents were affected.
- 🐻California State AGas victim2015-06-08
ADP, LLC reported a data breach to the California Attorney General. The incident occurred between April 7, 2015, and May 18, 2015. The provided source document contains only the filing metadata and an empty attachment placeholder; no narrative details regarding the nature of the breach, data types affected, or number of individuals impacted are available in the text provided.
- 🐻California State AGas victim2013-06-05
California state AG breach notification sample for ADP. The filing is a template/sample submission containing no specific incident details, dates, or affected data types.
- FLHHS OCRas victim2012-11-29
Advanced Data Processing, Inc. (dba Intermedix) reported to HHS on 2012-11-29 a Theft affecting 12,360 individuals. Breached information located on Desktop Computer. An employee inappropriately accessed and sold patient PHI (names, SSNs, addresses, DOB, claims) to third parties. The CE engaged third-party reviewers, implemented DLP and log management solutions, improved employee training, and launched a vendor management program.
- 🐻California State AGas victim2012-11-28
Advanced Data Processing, Inc. reported a data breach to the California Attorney General. The unauthorized access occurred between June 15, 2012, and October 1, 2012. The filing provides only the occurrence window; no discovery date, affected count, data types, or incident details are disclosed in the available metadata or attachments.