MEDTRONIC PUBLIC LIMITED COMPANY
ent_019fd5f93400f892a6ebf42cb7cc14d5
Disclosures
0
— · 0 jurisdictions
Multi-filing incidents
—
no multi-filing incident in sample
Max affected reported
—
no filed count in sample
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- MEDTRONIC PUBLIC LIMITED COMPANY
- Normalized
- medtronic public— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- 549300GX3ZBSQWUXY261
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (0)newest first
No disclosures linked to this entity yet.
Subsidiary disclosures (3)filed by group companies
◈ These filings were made by or about subsidiaries of MEDTRONIC PUBLIC LIMITED COMPANY — not by MEDTRONIC PUBLIC LIMITED COMPANY itself. Corporate relationships are mapped from GLEIF relationship records and SEC Exhibit 21 filings.
- Montana State AGvia MEDTRONIC MINIMED, INC.2023-04-14
Medtronic MiniMed disclosed that tracking technologies (Google Analytics, Crashlytics, Firebase Auth) in its InPen App inadvertently transmitted user data to Google starting Sept 2020. Discovered Feb 13, 2023. Data included emails, IPs, passwords, and device IDs. No SSN or financial data. Notifications sent April 14, 2023. Google Analytics removed; migration to new platforms underway.
- New Hampshire State AGvia MEDTRONIC MINIMED, INC.2018-11-26
Medtronic Minimed notified the NH Attorney General of an insider incident on Oct 11, 2018, where an employee improperly recorded sensitive customer info. 12 NH residents affected. Data included PHI, SSN, credit card info. Employee terminated, law enforcement notified, credit monitoring offered.
- Montana State AGvia MEDTRONIC MINIMED, INC.2018-11-21
Medtronic notified customers that an employee improperly recorded sensitive personal information (name, address, DOB, SSN, credit card data) of at least two known customers and potentially others. The employee was terminated. Medtronic offered 24 months of credit monitoring and notified HHS and state agencies. Incident discovered Oct 11, 2018.