DataPacts

GDPR Notices Before a Data Sale: Articles 13(3) and 14 and the SRB Ruling

Checked

At a glance

Under the GDPR, a company that licenses personal data for AI training must tell the people in it about the new purpose before the transfer (Article 13(3)), and the buyer must inform them within a reasonable period and at the latest one month after receiving the data (Article 14(3)(a)), unless an Article 14(5) exemption applies.

Independent reference. Every buyer is covered on the same terms, every figure carries its source and check date, and no buyer pays to be listed or placed higher.

Request an independent introduction

Tell us what data your company holds. We reply with the buyers that fit and what their terms leave out. Your details reach a buyer only after you agree to a named introduction.

IndependentYour details stay with us until you agreeNot selling is a valid outcome

Regulation (EU) 2016/679 applies from 2018-05-25, and a notice never replaces the legal basis or the transfer tool. As of 2026-11-17, this page covers the transparency layer of AI training data licensing.

Sources and dates are explained in how we source, date and check every figure.

Two Notice Duties in One Data Sale: Seller and Buyer

A data sale triggers two separate notices because seller and buyer are each controllers: the seller informs before it reuses the data, and the buyer informs because it obtained the data not from the people themselves. No notice is needed where and insofar as the person already has the information (Articles 13(4) and 14(5)(a)).

The table compares the duties, as of 2026-11-17.

Who Situation Provision Deadline Exemptions Source
Seller data collected from the people, reused for licensing Art. 13(3) before the further processing Art. 13(4) only (already informed) eur-lex.europa.eu
Seller data it obtained from others, reused for licensing Art. 14(4) before the further processing Art. 14(5)(a) to (d) eur-lex.europa.eu
Buyer receives the training set Art. 14(1) to (3)(a) reasonable period, at the latest one month Art. 14(5)(a) to (d) eur-lex.europa.eu
Buyer contacts the people or passes the data on Art. 14(3)(b), (c) at first communication; at the latest at first disclosure Art. 14(5)(a) to (d) eur-lex.europa.eu
Buyer later uses the set for another purpose Art. 14(4) before that use Art. 14(5)(a) to (d) eur-lex.europa.eu

Both notices must be concise, transparent and in plain language (Article 12(1)) and are free of charge (Article 12(5)).

The Seller's Notice Before Licensing: Article 13(3)

A company that intends to process personal data for a purpose other than the one it collected them for, such as licensing them for AI training, must give the people information on that purpose and the relevant Article 13(2) information before the further processing starts.

The transparency guidelines (WP260 rev.01, revised 2018-04-11, endorsed by the EDPB on 2018-05-25) add in paragraph 47 that, where the basis is neither consent nor law, the notice should explain why the new purpose is compatible. The test is set out under purpose compatibility (Article 6(4)) when reusing data for AI training.

How Far Ahead of the Transfer: A Reasonable Period

The GDPR sets no fixed lead time for a further-processing notice, but the transparency guidelines say a reasonable period should pass between notice and processing.

Under paragraph 48 of WP260 rev.01 the more intrusive or less expected the processing, the longer the period, and the controller must show the timing is fair. The right to object must be brought to attention clearly and separately at the latest at the first communication (Article 21(4)).

Two dated benchmarks exist. The German supervisory authorities (DSK, 2024-09-11) described an objection route of about six weeks for customer data in asset deals in negotiation.

The Higher Regional Court of Cologne (OLG Köln, 15 UKl 2/25, interim, 2025-05-23) took 2024-06-26, the training start Meta announced on 10 June 2024, as the date from which users could expect AI training.

Records the Seller Itself Obtained From Others: Article 14(4)

Where the seller did not collect the records from the people themselves, such as third parties named in tickets, the same before-reuse duty runs through Article 14(4), with the Article 14(5) exemptions. Notice or consent is decided under customer consent before licensing data for AI, or notice where that suffices.

What the Buyer's Article 14 Notice Must Contain

An AI data buyer that receives personal data must give the people thirteen items of information, from its identity to the source of the data, under Article 14(1) and (2).

The table lists the thirteen items in article order, as of 2026-11-17, and its middle column is an editorial reading for a training buyer.

Point Information (short) Note for a training buyer (editorial reading) Source
14(1)(a) identity and contact details of the controller and representative buyer's own identity, not the seller's eur-lex.europa.eu
14(1)(b) DPO contact, where applicable n/a eur-lex.europa.eu
14(1)(c) purposes and legal basis AI training named as purpose eur-lex.europa.eu
14(1)(d) categories of personal data not in Art. 13 eur-lex.europa.eu
14(1)(e) recipients or categories vendors and co-developers eur-lex.europa.eu
14(1)(f) third-country transfer and safeguard if the set leaves the EU eur-lex.europa.eu
14(2)(a) storage period or criteria n/a eur-lex.europa.eu
14(2)(b) legitimate interests, where Art. 6(1)(f) applies n/a eur-lex.europa.eu
14(2)(c) rights incl. objection and portability objection also under Art. 21(4) eur-lex.europa.eu
14(2)(d) consent withdrawal, where consent is the basis n/a eur-lex.europa.eu
14(2)(e) complaint to a supervisory authority n/a eur-lex.europa.eu
14(2)(f) source, and whether publicly accessible Recital 61 general information only for mixed sources eur-lex.europa.eu
14(2)(g) automated decision-making under Art. 22(1) and (4) where applicable eur-lex.europa.eu

Where the buyer relies on Article 6(1)(f), it states the interest pursued (Article 14(2)(b)), as described under legitimate interest (Article 6(1)(f)) for AI training data.

Deadlines: One Month, First Contact or First Onward Disclosure

Article 14(3) gives the buyer one outer limit and two earlier triggers: one month after obtaining the data, the first communication with the person, or the first disclosure to another recipient, whichever comes first.

WP260 rev.01 (paras. 27 and 28) says points (b) and (c) shorten the month and never extend it, and a recipient may be a controller, joint controller or processor.

A buyer that hands the set to an annotation vendor within days therefore informs the people first. The CNIL note of 2022-12-05 on selling customer files states the one-month buyer deadline.

Naming the Source of Each Record, and Recital 61

The buyer must say where the data came from (Article 14(2)(f)); only where records cannot be traced to one source may it give general information (Recital 61). WP260 rev.01 (para. 60) says compiling from several sources does not lift the duty if each person's source can be identified.

The Article 14(5)(b) Exemption: Impossible or Disproportionate Effort

Article 14(5) lifts the buyer's notice duty in four cases, and only point (b), impossibility or disproportionate effort, is realistic for a training set.

  • (a) the person already has the information
  • (b) informing is impossible or a disproportionate effort, with appropriate measures including public information
  • (c) Union or member state law requires the disclosure and protects the person
  • (d) professional secrecy

WP260 rev.01 (para. 57) reads the exceptions narrowly, and paragraph 62 notes that the seller's Article 13(3) notice has no such exemption.

A Documented Balancing Test, Not a Routine Exit

The transparency guidelines say Article 14(5)(b) "should not be routinely relied upon" by controllers that do not process for archiving, research or statistics, and a commercial license is not one of those purposes on its face.

The effort must stem directly from the indirect collection (para. 62), and Recital 62 names the factors: the number of people, the age of the data and the safeguards.

Paragraph 64 requires weighing the effort against the impact of not informing, and documenting it. Whether training counts as research is open under the EDPB's Guidelines 1/2026, a consultation version, not final as of 2026-11-17.

Appropriate Measures, Starting With Public Information

Where the exemption applies, the controller must still take appropriate measures, and making the information publicly available is one it must always take (Article 14(5)(b); WP260 rev.01 para. 64).

  • public information on a website, in a newspaper or on posters
  • a data protection impact assessment
  • pseudonymization
  • minimization and high security

EDPB Opinion 28/2024 (para. 103) adds media and e-mail campaigns, FAQs, model cards and voluntary transparency reports. The practical steps are under PII removal and de-identification before licensing data for AI training.

Scraped and Bulk Training Data in EDPB Opinion 28/2024

The EDPB's Opinion 28/2024 of December 17, 2024 says reliance on Article 14(5)(b) is "strictly limited to when the requirements of this provision are fully met" where AI development collects large amounts of publicly accessible data (para. 63).

Paragraph 92 adds that a privacy-policy mention is not necessarily enough to create a reasonable expectation. The opinion is soft law; see when an AI model is anonymous under EDPB Opinion 28/2024.

Notices for Pseudonymized Training Sets After C-413/23 P

In EDPS v SRB (C-413/23 P, First Chamber, September 4, 2025) the Court of Justice held that the duty to tell people about recipients is judged at collection and from the controller's point of view, so a seller cannot skip naming a buyer because the records are pseudonymized.

The duty applies before the transfer, irrespective of whether the data were personal for the recipient after pseudonymization (paras. 108, 111 and 112).

The Court also held that an information duty cannot be imposed on an entity "in no way in a position" to identify the person (para. 89).

Read with GDPR Article 11(1) and WP260 rev.01 (para. 64), this suggests, as a reading and not a holding, that a buyer for whom the set is not personal data may owe no Article 14 notice, while the seller's duty stands.

Where the buyer can reasonably re-identify, for example by cross-checking, Article 14 applies in full (para. 85); the case record is on EDPS v SRB (C-413/23 P) and pseudonymised data.

A seller checks:

  • whether the collection notice named recipients or categories such as AI developers (paras. 111 and 112)
  • who holds the key (para. 77)
  • what the buyer can cross-check (para. 85)

The judgment applied Regulation (EU) 2018/1725, Article 15(1)(d), the EU-body counterpart of GDPR Article 13(1)(e), so carrying it over is a reading. The EDPB's Guidelines 01/2025, a consultation version, not final as of 2026-11-17, treat pseudonymized data as personal even where another person holds the key; see anonymization vs pseudonymization for AI training data.

Regulator and Court Positions on Notices in Data Sales and AI Training

The table lists every dated position on notices in a training data sale recorded here, oldest first, as of 2026-11-17.

Date Author Document Position on notices Status Source
2018-04-11 (endorsed 2018-05-25) Article 29 Working Party; EDPB WP260 rev.01 transparency guidelines reasonable period before further processing (para. 48); 14(5)(b) narrow, documented, public information always (paras. 60 to 64) guidelines, endorsed ec.europa.eu
2022-12-05 CNIL note on selling customer files buyer informs the people within one month guidance cnil.fr
2024-06-26 (court date of 2025-05-23) OLG Köln 15 UKl 2/25 (interim) date users could expect AI training (training start Meta announced 10 June 2024) interim, injunction rejected nrwe.justiz.nrw.de
2024-09-11 DSK (German supervisory authorities) asset-deal resolution objection route for customer data in negotiations in progress, period about six weeks authorities' resolution datenschutzkonferenz-online.de
2024-11-02 Garante (Italy) decision n. 755, OpenAI six-month information campaign ordered (Art. 166(7) Privacy Code) opposition upheld by Tribunale di Roma n. 4153/2026, published 2026-03-18 (as of 2026-11-10) garanteprivacy.it
2024-11-27 Garante (Italy) provvedimento n. 741, warning to GEDI on its OpenAI content deal processing could breach Arts. 9, 10, 13, 14 and Chapter III; information duties not met formal warning (art. 58(2)(a)) garanteprivacy.it
2024-12-17 EDPB Opinion 28/2024 14(5)(b) "strictly limited" for scraped data (para. 63); privacy-policy mention not enough for expectation (para. 92) adopted, soft law edpb.europa.eu
2025-01-17 EDPB Guidelines 01/2025 on pseudonymisation pseudonymized data personal even if another person holds the key consultation version, not final edpb.europa.eu
2025-09-04 Court of Justice (First Chamber) C-413/23 P, EDPS v SRB recipient information judged at collection from the controller's side (paras. 111 to 112) judgment; T-557/20 referred back eur-lex.europa.eu (62023CJ0413); curia.europa.eu
2025-11-03 (checked 2026-11-09) LinkedIn EU privacy notice update on generative AI training resumes saved and screening answers used, private messages excluded (LinkedIn's statement) company's own page (claim) linkedin.com

The Garante ordered an information campaign in decision n. 755, against which a Rome court upheld OpenAI's opposition (as of 2026-11-10). The LinkedIn row is the company's own claim. No fine for a missing Article 14 notice in a training data sale is recorded here.

Pending, Not Final: Proposed Article 13(4) in COM(2025) 837

The Commission's proposal COM(2025) 837 of November 19, 2025 would replace Article 13(4) with an exemption for clear, circumscribed and not data-intensive relationships, not applying where data go to recipients or third countries, to automated decision-making or to high-risk processing.

A sale has a recipient, so the draft would not exempt it. The Parliament's procedure file shows "Awaiting committee decision" (re-checked 2026-11-17), and the text has no legal effect today; see proposed GDPR changes in the EU Digital Omnibus.

Giving Notice Before Licensing: Benefits, Risks, Downsides and Alternatives, Including Not Licensing

Telling people before a license costs time and may lose records to objections, but skipping it moves the risk to both parties, and not licensing at all remains a valid choice.

Benefits

  • People can object before the transfer (Article 21(4)).
  • Naming AI developers as recipients at collection answers C-413/23 P.
  • Public information is always available under Article 14(5)(b).

Risks

  • Article 14(5)(b) is narrow and case by case.
  • A privacy-policy line may not create a reasonable expectation (Opinion 28/2024, para. 92).
  • Onward disclosure needs a notice first.
  • As of 2026-11-17, breaches of Articles 12 to 22 fall in the tier up to EUR 20,000,000 or 4 % of worldwide annual turnover (Article 83(5)(b)).

Downsides

  • Objections shrink the set.
  • Waiting delays delivery.

Alternatives

Notices are one step in a training data deal. The parent page, GDPR rules for AI training data, sets them beside the other GDPR duties.

How This Page Is Sourced and Dated

Every rule here cites the Official Journal text of Regulation (EU) 2016/679, a judgment by case number and date, or a regulator's or company's own document with the date it was read. This page is general information about GDPR notices, not legal advice for any specific dataset or deal.

Frequently Asked Questions

Does a company have to tell customers before licensing their data for AI training?

Yes under the GDPR, before the further processing starts (Article 13(3)), unless they already have the information; the buyer then gives its own Article 14 notice.

How long does an AI data buyer have to send an Article 14 notice?

Within a reasonable period, at the latest one month after obtaining the data, earlier at first contact or before first passing the data on (Article 14(3)).

Can a buyer of a large training set skip individual notices?

Only if informing each person is impossible or a disproportionate effort, documented, with public information and other measures (Article 14(5)(b); WP260 para. 64).

Does pseudonymization remove the duty to inform?

Not for the seller: recipient information is judged at collection from the controller's side (C-413/23 P, paras. 111 to 112); a buyer unable to identify anyone may owe none.