FlightAware, Inc.
ent_e8262b701be797e0328823cf
Disclosures
3
State AG · 3 jurisdictions
Incidents
1
filings grouped by incident
Max affected reported
2,000,000
as filed · State AG OR
Leak-site claims
0
none in sample
Identity resolution
- Canonical name
- FlightAware, Inc.
- Normalized
- flightaware— dedupe via name-norm; Microsoft / MSFT collapse to one row
- GLEIF LEI
- No match
- SEC EDGAR CIK
- None — not an SEC registrant
- Domain
- None on record
Disclosure history (3)newest first
- 🦫Oregon State AGas victim2024-08-13
FlightAware reported a data breach to the Oregon Attorney General. The breach was reported on 2024-08-13. The breach occurred during 1/1/2021 - 7/26/2024. The breach was discovered on 7/25/2024. 2,000,000 individuals were affected.
- 🐻California State AGas victim2024-08-13
FlightAware, Inc. disclosed a data security incident discovered on July 25, 2024, caused by a configuration error that potentially exposed personal information of account holders. The exposed data may include user IDs, passwords, email addresses, full names, billing/shipping addresses, IP addresses, social media accounts, telephone numbers, year of birth, last four digits of credit card numbers, aircraft ownership info, industry, title, pilot status, and account activity. Social Security Numbers may also have been exposed. The company remedied the error and is requiring password resets and offering two years of credit monitoring.
- 🌲Washington State AGas victim2024-08-13
FlightAware, a business sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2024-07-25 and filed notice on 2024-08-13. 1,407 Washington residents were affected. 19 days elapsed between awareness and notification. 1301 days to identify the breach. 1 days to contain the breach.