UnknownMedium

Resort Data Processing

bd_ddf170b689ea8fa4 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Apr 23, 2025

Filed

May 14, 2025

To disclose

21 days

Affected

5,007

Linked

10 filings

Confidence

95%

Full breach record for Resort Data Processing →4 incidents on file

Resort Data Processing reported a data breach to the Oregon Attorney General. The breach was reported on 2025-05-14. The breach occurred during 2/19/2025 - 4/17/2025. The breach was discovered on 4/23/2025. 5,007 individuals were affected. Notice was sent on 5/14/2025.

J jump to incidentP pin to compareR raw source

Oregon clock✓ OR AG ≤45d21 days discovery → filing

⚠ AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Incident timeline

undetected · 63 days

discovery → filing · 21 days

Feb 19, 2025

Begins

Apr 23, 2025

Discovered

May 14, 2025

Filed

This filing is one of 10 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (9) · sorted by filing gap

Indiana State AGbd_96ce6993e847b9e62025-05-14Candidate
New Hampshire State AGbd_a0e4b4a06e21d23f2025-05-14Verified
Maine State AGbd_d61dcb6e96e3a4202025-05-14Verified
Nebraska State AGbd_f4a978a89704c9482025-05-14Verified

Show 5 more filings ↓up to 55d gap

Massachusetts State AGbd_92132c96d31f711e2025-05-15 · +1dVerified
Massachusetts State AGbd_7dd00237ee453ab12025-03-21 · +54dVerified
New Hampshire State AGbd_f4dce13e49c6cc3f2025-03-21 · +54dVerified
Nebraska State AGbd_1196423476f86fb92025-03-20 · +55dVerified
Indiana State AGbd_4c495ff1bf829a512025-03-20 · +55dCandidate

Name: Resort Data Processing
norm: resort data processing
Domain: resortdata.com

Name: Resort Data Processing
norm: resort data processing
Domain: resortdata.com

Discovered: Apr 23, 2025
Breach occurred: Feb 19, 2025 – Apr 17, 2025
Undetected for: 63 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 14, 2025
Affected individuals: 5,007nationwide
Data types: —
Attack vector: Unknown

Time to disclose: 21 days(21 days from discovery to filing)
Compliance flags: OR AG ≤45d
Discovery-date grounding: AG web formThe discovery date came from the AG web-form field, which is systematically later than the detection date stated in the letter. Treat the clock as indicative.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 10 filings · 6 states

View merged incident ↗

Nebraska State AGMar 20 · first

Indiana State AGMar 20 · first

Massachusetts State AG+1d

New Hampshire State AG+1d

Indiana State AG+55d

New Hampshire State AG+55d

Maine State AG+55d

Nebraska State AG+55d

Oregon State AG+55d · this page

Massachusetts State AG+56d

Pattern: first filing Mar 20 (NE), last May 15 (MA) — a 56-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://justice.oregon.gov/consumer/DataBreach/
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 14, 2025
Raw hash: bef0a07214d25f72ac501387ed88fe90bcc5358a76fd23f18311bb45a696783c

Linked disclosures

Regulatory filings (9) · sorted by filing gap

Reporting entityResort Data Processing

Victim entityResort Data Processing

Incidentdiscovered Apr 23, 2025

ComplianceOR AG ≤45d

Extraction provenanceno artifact recorded

Source provenancejustice.oregon.gov