Chapel Hill Presbyterian Church
ent_019dd1b47869036c691755fa817a826a
Disclosures
4
State AG · 4 jurisdictions
Multi-filing incidents
1
incidents joining 2+ filings here
Max affected reported
1,000
nationwide · State AG ME
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- Chapel Hill Presbyterian Church
- Normalized
- chapel hill presbyterian church— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- 549300CZOJQL9WP9OA56
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (4)newest first
- Massachusetts State AGas victim2026-03-24
Chapel Hill Presbyterian Church notified Massachusetts residents of a data security incident that may have involved their information. The notice offers complimentary identity monitoring through Iris Identity Protection and provides guidance on security freezes and fraud alerts. No specific dates, attack vectors, or affected counts were disclosed in the provided text.
- Nebraska State AGas victim2026-03-23
Chapel Hill Presbyterian Church, located in Gig Harbor, WA, notified the Nebraska Attorney General of a data security incident affecting one Nebraska resident. The church became aware of unusual network activity on January 30, 2026. Unauthorized access to data occurred on or about February 6, 2026. The affected individual's name and Social Security Number were potentially compromised. Notification was mailed on March 23, 2026. The church engaged cybersecurity experts and offered complimentary identity monitoring.
- Maine State AGas victim2026-03-23
Chapel Hill Presbyterian Church (WA) reported an external system breach (hacking) on Jan 30, 2026, discovered Jan 30, 2026. 1,000 individuals affected, including 1 Maine resident. Name and other personal identifiers were acquired. No evidence of misuse. Forensic investigation engaged; 12 months credit monitoring offered.
- Washington State AGas victim2026-03-23
Chapel Hill Presbyterian Church, a non-profit/charity sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2026-01-30 and filed notice on 2026-03-23. 879 Washington residents were affected. 52 days elapsed between awareness and notification. -27 days to identify the breach. 27 days to contain the breach.