Clustered 3 filings across 3 jurisdictions · filing window Feb 22, 2024 → Aug 21, 2024. View entity profile → Other incidents for this victim →
incident inc_fa7fc05a87474a61 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
NH VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 7, 2024
Reported by VERMONT AG filing
PEER, a full-service environmental engineering consulting firm, provides personalized service to our valuable clients, fosters andmaintains long-term partnerships, and hires passionate and diverse team members. 20Gb of data will be uploaded lots of documents with personal information. Passports, SSNs, driver licenses, confidential agreements, NDAs and so on.
Aug 21, 2024
When the intrusion reportedly occurred, per the linked filings
PEER Consultants, P.C. notified 4 New Hampshire residents and 1 Rhode Island resident of a data security incident occurring on August 21, 2024. The firm implemented technical safeguards, revised policies, and offered Experian IdentityWorks credit monitoring services to affected individuals.
Affected (this filing): 4
PEER Consultants, P.C. notified consumers of a data breach where unauthorized access occurred between Jan 18 and Feb 7, 2024. Affected data included names, SSNs, and government IDs. The company offered 24 months of credit monitoring. No specific total count was disclosed, though one Rhode Island resident was identified.
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.