Clustered 5 filings across 3 jurisdictions · filing window Mar 14, 2025 → May 6, 2025. View entity profile → Other incidents for this victim →
incident inc_2cf1b92f21a141ed · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
PII · Government ID
ME NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 14, 2025
When the intrusion reportedly occurred, per the linked filings
Mar 14, 2025
Reported by NEW HAMPSHIRE AG filing
Shop our Lifestyle & Gift Boutique for Designer Stationery, Journals, Planners, Calendars, Holiday, Home Decor, Greeting Cards, Gifts & beyond! Fashion Your Life with Graphique!
Shop our Lifestyle & Gift Boutique for Designer Stationery, Journals, Planners, Calendars, Holiday, Home Decor, Greeting Cards, Gifts & beyond! Fashion Your Life with Graphique!
Shop our Lifestyle & Gift Boutique for Designer Stationery, Journals, Planners, Calendars, Holid...
Apr 7, 2025
Reported by MAINE AG filing
Graphique De France notified the NH Attorney General of a data incident occurring on March 14, 2025, involving unauthorized access to employee personal information. 20 NH residents were affected. The company engaged forensic investigators, reported to federal law enforcement, and offered credit monitoring services.
Affected (this filing): 20
Graphique De France reported an external system breach that occurred between March 13 and March 14, 2025. The breach was discovered on April 7, 2025, and affected one resident of Maine. The company offered 12 months of identity protection and credit monitoring services through TransUnion.
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.
Affected (this filing): 1