who_to_notify
Works out every data breach notice a company owes and the deadline for each. Give affected (how many people in each US state or country), the data types exposed (for example ssn, drivers_license, payment_card, financial_account, medical, health_insurance, username_password, biometric, passport, dob, email_address), whether the data was encrypted with the key kept safe, the date the breach was discovered, and flags: sec_registrant (US public company), sector (hipaa_covered_entity, hipaa_business_associate, glba_financial, health_app, nydfs_licensee) and role (owner, or service_provider holding data for another company). Returns each notice owed (people affected, state attorneys general, credit bureaus, HHS, SEC Form 8-K, FTC, EU and UK data protection authorities, Canada, Australia) with the deadline as a date where the law sets a fixed period, the deadline rule in words, what the notice must contain, how to send it and the official source, earliest first. Unclear cases give the SAFE answer (notice treated as required) plus what it depends on. Free.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| role | No | owner (default): the company that owns or licenses the data. service_provider: holds it for another company, which mostly means notifying that company quickly. | |
| sector | No | Sector rules that apply: hipaa_covered_entity, hipaa_business_associate, glba_financial (non-bank financial firms under the FTC Safeguards Rule), health_app (FTC Health Breach Notification Rule), nydfs_licensee (New York DFS regulated). | |
| affected | Yes | Where the affected people live: [{"state":"CA","count":1200},{"state":"TX","count":300},{"country":"Germany","count":40},{"country":"United Kingdom","count":15},{"country":"Canada","province":"Quebec","count":5}]. A bare two-letter code is read as a US state (CA = California); use {"country":"CA"} or "Canada" for Canada. | |
| encrypted | No | True only if all the exposed data was encrypted and the key was not exposed. Many US state laws then need no notice. Default false. | |
| data_types | No | Personal data exposed, for example ["ssn","drivers_license","payment_card"]. If left out every law is treated as triggered (SAFE). | |
| sec_registrant | No | True for a company that files reports with the US SEC (listed in the US). Adds Form 8-K Item 1.05. | |
| date_discovered | No | Date the breach was discovered (or you became aware of it), YYYY-MM-DD. Defaults to today. Deadlines are counted from it. | |
| materiality_date | No | SEC registrants: date the company decided the incident is material, YYYY-MM-DD. The 8-K is due 4 business days after it. |