Clustered 3 filings across 3 jurisdictions · filing window Oct 22, 2025 → May 5, 2026. View entity profile → Other incidents for this victim →
incident inc_05d2d233f6524d4a · merge_method human · 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.
IN NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 24, 2025
When the intrusion reportedly occurred, per the linked filings
Time Equities is a globally diversified real estate firm, founded in 1966, based in New York City. The company focuses on 3 main aspects: acquisition, development, and management of properties. It handles a variety of types, ranging from office and retail to industrial and residential. They have properties in 30 states in the US, as well as in Europe and Canada.
Apr 24, 2026
Reported by NEW HAMPSHIRE AG filing
Time Equities Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2025-09-24 and was reported on 2026-04-30. 46 Indiana residents were affected.
Affected (this filing): 46
Time Equities, Inc. notified the New Hampshire Attorney General of a data event affecting 26 state residents. Unauthorized access occurred on October 16, 2025, via suspicious email activity (phishing). The incident involved names, SSNs, and driver's license numbers. The company discovered the breach on April 24, 2026, notified the FBI, and provided 12 months of credit monitoring 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): 26