Rights and contracts
AI data supplier incident notification: what should the supplier report?
By SourceX Editorial · Reviewed by Noah Loul ·
10 sections
Short answer
After a privacy or rights incident, an AI data supplier should report in three stages: a first alert with what is known, the affected batches and record IDs, and a named contact; a containment update confirming what was stopped, quarantined or replaced; and a closing report with root cause and the corrected manifest. Clocks and fields belong in the license, because privacy laws mainly govern who notifies regulators, not what a licensee needs.
Record timeline
AI data supplier incident
Key takeaways
- Require notice in three stages, so the first alert never waits for a finished investigation.
- Classify the incident first: a privacy incident, a rights incident and a quality defect trigger different owners and different follow-up.
- Privacy law sets duties to notify the data's owner or controller; a licensee usually needs a contract clause to get the same information.
- A notice the buyer cannot act on is incomplete: it must name batches, record IDs and manifest versions.
- Containment means proof, such as revoked links, quarantined IDs and a replacement manifest, not a statement that the issue is fixed.
- Drill the notice during the pilot before committing to the full purchase.
What should an AI data supplier report after a privacy or rights incident?
The supplier should report what happened, which delivered records are affected, what it has already done to contain it and what the buyer must do now, in that order and in stages. A first alert goes out fast with incomplete facts; a containment update follows once the affected scope is fixed; a closing report confirms the root cause and the corrected delivery.
Buyers usually discover the gap the first time something goes wrong. A support transcript dataset turns out to contain unredacted phone numbers, or the supplier learns that one source system was covered by a reseller agreement that excluded resale. The supplier sends an email that says an issue was found and is being handled. The buyer's data team cannot tell which files to pull, whether a training run in progress is affected or whether a model already shipped needs review.
The template on this page fixes that by turning the notice into a set of fields the license requires. It sits beside the takedown and deletion procedures a license may already have: those say what the buyer does with a withdrawal, while the incident notice says what the supplier must tell the buyer to make that withdrawal possible.
Privacy incident, rights incident or quality defect: which notice applies?
Classify the event before anyone drafts the notice, because the class decides who owns the legal assessment and what the buyer must do. A privacy incident concerns personal information that is exposed, accessed or retained where it should not be. A rights incident concerns the supplier's authority to license the records at all. A quality defect is a data error with no privacy or rights consequence.
Keep four questions apart: who could access the data, whether privacy rules permitted the use, who owns the records and what the license actually grants. De-identification alone does not create a right to license, and a valid license does not cure a privacy exposure. Under EDPB guidance on controllers and processors, a processor must tell the controller whenever it discovers a personal data breach affecting its own or a sub-processor's systems, which is why the supplier's subcontractors belong in the classification too.
| Class | Typical trigger in a licensed dataset | Who decides legal notification | What the buyer usually must do |
|---|---|---|---|
| Privacy exposure in delivered data | Direct identifiers survived redaction in a delivered batch | The data's controller or owner, advised by counsel | Quarantine named records, pause new training on them, await the replacement batch |
| Privacy incident at the supplier | A staging bucket holding the source export was publicly readable | The controller of the source data, with the supplier assisting | Usually nothing in its own systems, but it needs the facts for its own risk review |
| Rights incident | A source contract, consent basis or ownership chain did not cover licensing | The supplier with its counsel; the buyer's counsel reviews remedies | Withdraw the affected records and assess derived models under the license terms |
| Third-party claim | A copyright or confidentiality claim names specific records or documents | Both parties' counsel under the indemnity and claims clauses | Preserve evidence, quarantine named material, follow the claims procedure |
| Quality defect | Duplicated or truncated records, wrong labels, broken joins | No legal notification; the acceptance terms govern | Reject or accept the corrected batch under the acceptance criteria |
What do privacy laws already require a supplier to tell its customer?
Privacy laws mostly require a supplier that holds personal data for someone else to tell that party promptly, and they leave the regulator and individual notices to the party that owns or controls the data. A licensee that receives a copy of the dataset is often not that party, so its right to be told comes from the contract.
Under the GDPR, a processor must notify the controller without undue delay after becoming aware of a personal data breach (Article 33(2)). The 72-hour deadline for notifying the supervisory authority sits with the controller under Article 33(1), and Article 33(3) lists the minimum content: the nature of the breach including categories and approximate numbers of people and records, a contact point, likely consequences and the measures taken or proposed. Article 28(3)(f) requires the processor contract to oblige the processor to assist the controller with these duties. The EDPB's breach guidelines add that the controller keeps overall responsibility while the processor plays an important part in making notification possible.
In the United States the pattern is similar. HHS explains that a HIPAA business associate must notify the covered entity without unreasonable delay and no later than 60 calendar days after discovering a breach, identifying each affected individual to the extent possible. California Civil Code section 1798.82(b) requires a business that maintains computerized personal information it does not own to notify the owner or licensee immediately following discovery of a breach.
Two practical consequences follow. First, borrow the statutory content lists for your contract fields, because a supplier already has to produce that information for its own customers. Second, set a contract clock for notice to the buyer that does not depend on whether a legal duty applies, since rights incidents and many delivered-data exposures fall outside breach statutes altogether. Counsel confirms which laws apply to the specific records.
The incident notification and containment template
Write these ten fields into the license as the required content of an incident notice, and mark in which stage each must be complete. A field may say unknown in the first alert; it may not be missing.
At a glance
The incident notification and containment template
- First alert: due within the contract clock, for example 24 or 48 hours from confirmation (illustrative choices, not legal minimums), even if half the fields read unknown.
- Containment update: due once the affected scope is fixed, with record IDs, completed actions and the replacement plan.
- Closing report: due at an agreed interval after containment, with root cause, the corrected manifest and confirmation that later batches were rechecked.
| Field | What the supplier states | Complete by stage | Why the buyer needs it |
|---|---|---|---|
| Incident ID and class | A stable reference and one class from the classification table | First alert | Routes the notice to privacy, legal or data acceptance owners |
| Discovery and awareness times | When the issue was first observed and when it was confirmed | First alert | Starts the contract clock and any legal clock on either side |
| Affected deliveries | Batch IDs, delivery dates and manifest versions | First alert, refined in the update | Tells the buyer which stored copies and pipelines to check |
| Affected records | Record IDs or a hash list, with the count and how it was derived | Containment update | Lets the buyer quarantine exactly what is affected and nothing else |
| Data categories involved | Which fields or identifier types, and whether sensitive categories appear | First alert | Drives the buyer's own privacy assessment |
| Rights basis affected | Which source agreement, consent or ownership link failed, if a rights incident | Containment update | Shows whether the remedy is replacement, withdrawal or renegotiation |
| Actions already taken | What the supplier stopped, revoked, quarantined or corrected, with times | Containment update | Separates done from planned and avoids duplicate work |
| Actions requested of the buyer | Quarantine, deletion, pause on training, preservation or no action | First alert | Converts the notice into a task the buyer can assign today |
| Root cause and prevention | What failed in the pipeline or contract chain and what changed | Closing report | Tells the buyer whether later batches carry the same risk |
| Contacts and next update time | Named incident lead, privacy or legal contact, and when the next update arrives | First alert | Prevents silence between stages |
How precisely must the notice identify affected records?
Precisely enough that the buyer can find every affected copy without opening the whole dataset: batch, file, record ID and a hash or checksum per record. A count alone forces the buyer to quarantine entire deliveries and wastes clean data.
Copyright law offers a useful benchmark. The U.S. Copyright Office explains that a takedown notice under section 512 must identify the work and give information reasonably sufficient to locate the material, often specific URLs or pages. A data license can apply the same standard to every incident class: the notice is not complete until the buyer can locate the material.
This only works if identifiers were agreed before the first delivery. Ask for stable record IDs that survive re-exports, a manifest per batch with per-file checksums and a version number on every corrected batch. Without them, the supplier will send a description of the problem and the buyer will spend days reconstructing which rows it means.
Which containment actions should the notice confirm, and in what order?
Contain at the source first, then in transit, then at the buyer, and ask for evidence of each step rather than a statement. NIST's SP 800-61 Revision 3, finalized in April 2025, frames incident response as part of an organization's overall cybersecurity risk management under CSF 2.0 rather than a fixed procedure, so the contract should name the outcomes each party must evidence.
| Order | Action | Owner | Evidence the buyer can check |
|---|---|---|---|
| 1 | Stop further deliveries of affected batches and revoke open download links | Supplier | Revocation time and the access log showing no later downloads |
| 2 | Quarantine affected records at the supplier and its subcontractors | Supplier | List of locations checked and the record IDs moved |
| 3 | Quarantine the same record IDs in the buyer's storage and feature stores | Buyer | Internal ticket listing paths and IDs quarantined |
| 4 | Pause new training or evaluation runs that read the affected batch | Buyer | Run IDs paused or tagged with the incident ID |
| 5 | Preserve logs and the original batch under restricted access | Both | Retention hold reference, so evidence survives the deletion steps |
| 6 | Deliver a corrected batch with a new manifest version | Supplier | Manifest diff showing removed and replaced record IDs |
| 7 | Assess trained models and outputs under the license terms | Buyer, with counsel | Written decision on retain, retrain or restrict, referencing the incident ID |
What must the pilot establish before the buyer commits to the larger purchase?
The pilot should prove that the supplier can produce a usable notice under time pressure, not only that its sample data is clean. Run a short tabletop drill: plant a synthetic problem in a pilot batch, ask the supplier to notify under the draft clause and score the result.
If the supplier cannot pass this on a small pilot, it will not pass on a multi-batch program. Record the drill result in the procurement file next to the data quality results.
- The first alert arrives within the draft clock and names a reachable incident lead.
- Affected records are identified by ID and checksum, and the count matches what was planted.
- The supplier names every subcontractor location it checked.
- A corrected batch arrives with a new manifest version and a readable diff.
- The supplier can state which source agreement covers each batch, so a rights incident can be traced.
- The buyer's own team can complete its quarantine steps from the notice alone.
Worked example (illustrative): two incidents in a support transcript license
A buyer licenses de-identified customer support transcripts in monthly batches. Everything in this example, including the counts and percentages, is illustrative.
Incident one is a privacy exposure. During a routine recheck, the supplier finds that its redaction step missed phone numbers written with spaces, affecting about 2 percent of conversations in batch 4. The first alert arrives the next morning with class, batch, manifest version, the identifier type and a request to quarantine the batch, with record IDs marked unknown. Two days later the containment update lists 412 record IDs with checksums, confirms the download link was revoked and attaches a corrected batch 4.1. The buyer quarantines exactly those IDs, tags one paused evaluation run and resumes.
Incident two is the exception that shows the limits of the template. The supplier learns that transcripts from one product line came from a contact center vendor whose contract did not allow resale of recordings. No personal data was exposed and no statute requires notice, but the supplier's authority to license that slice is gone. The notice names the source agreement, the affected batches and about 9 percent of records, and requests withdrawal. Here the template only starts the work: whether models already trained on that slice may be kept depends on the license's survival and withdrawal clauses, which go to both parties' counsel.
Signals that an incident has outgrown the template
Stop treating the incident as a notice exercise and bring in specialists when the facts change who carries legal duties or when the remedy affects models already in use.
- Health, financial, biometric, children's or other sensitive categories appear in the affected records.
- The buyer may itself be a controller or covered entity for the affected data, which creates its own notification duties.
- The supplier cannot identify affected records by ID, or its count keeps changing between updates.
- A third party has made a written claim, or the incident affects the supplier's ownership of the whole dataset.
- Models trained on the affected records are already in production or licensed onward.
- The supplier's subcontractor will not confirm what it holds.
Putting incident terms into a data request
If you are sourcing new operational data, state the incident terms when you scope the request rather than after the first delivery. SourceX looks for operational data at U.S. businesses only after a buyer asks, and its request form already collects scope, volume, format, timing and licensing needs, so the notice fields and pilot drill above can travel with that brief.
Each supplying company approves the scope and terms and signs its agreement before any data is delivered, which is the right moment to settle record identifiers, manifests and notice stages. This page is general information, not legal advice; counsel should review the clause against the specific records and laws involved.
Frequently asked questions
Is a data supplier legally required to notify a buyer of a breach?
Sometimes. Laws such as GDPR Article 33(2) and California Civil Code 1798.82(b) require a party holding data for someone else to tell the controller or owner, but a licensee holding its own copy may not be that party. Put a contract duty in the license so notice does not depend on how a statute classifies the buyer.
How fast should the first incident alert arrive?
Set a short contract clock from confirmation, for example a day or two (an illustrative choice, not a legal minimum), and require the alert even when facts are incomplete. Legal deadlines such as the GDPR's 72 hours for controllers run in parallel and do not replace the contract clock.
What is the difference between a rights incident and a privacy incident?
A privacy incident concerns personal information that was exposed or used where it should not be. A rights incident concerns whether the supplier could license the records at all, for example because a source contract excluded resale. They can occur together, but they have different owners and remedies.
Should the buyer delete affected records immediately?
Quarantine first and delete only when the license and counsel say so. Preserving the original batch under restricted access keeps the evidence needed for any claim or regulator question, and deletion can follow once the incident is closed.
Does an incident affect models already trained on the data?
It can, depending on the incident class and the license's withdrawal and survival terms. Record which runs read the affected batch, then let counsel decide whether to retain, retrain or restrict each model.
Sources
- GDPR Article 33(2) requires a processor to notify the controller without undue delay; Article 33(1) gives the controller a 72-hour deadline to notify the supervisory authority; Article 33(3) lists minimum content; Article 28(3)(f) requires processor assistance. Source
- The EDPB says the controller retains overall responsibility, while the processor has an important role in enabling breach notification. Source
- The processor must notify the controller whenever it discovers a breach affecting its own or a sub-processor's facilities or IT systems. Source
- A HIPAA business associate must notify the covered entity without unreasonable delay and no later than 60 days after discovery, identifying affected individuals where possible. Source
- A California business maintaining personal information it does not own must notify the owner or licensee immediately following discovery of a breach. Source
- NIST SP 800-61 Revision 3 integrates incident response recommendations into cybersecurity risk management under CSF 2.0. Source
- A section 512 takedown notice must identify the work and give information reasonably sufficient to locate the material. Source
Tell us what data you need
Share scope, volume, format, timing and licensing needs. Datasets are sourced on request.