Traduction en préparation
Cet article est pour l'instant disponible en anglais. La version française paraîtra dans une prochaine vague.
GDPR Article 13 checklist: the disclosures most privacy policies miss
Article 13 of GDPR lists the information a controller must provide at the point of data collection. It is more specific than "have a privacy policy." Here is the full checklist, with the four disclosures most storefronts miss.
GDPR Article 13 lists the information a controller must provide to the data subject at the moment personal data is collected directly. It is more specific than "have a privacy policy." Each item on the list is a separate disclosure obligation, and missing any of them is a breach regardless of how thorough the rest of the document is.
GDPR Article 13(1) checklist
Article 13(1) requires the controller to provide the following information at the time of collection.
- Identity and contact details of the controller, and where applicable, the controller's representative.
- Contact details of the Data Protection Officer where one is appointed.
- Purposes of processing and the legal basis for each purpose.
- Where processing is based on legitimate interests under Article 6(1)(f), the specific legitimate interests pursued.
- Recipients or categories of recipients of the personal data.
- Where applicable, the fact that the controller intends to transfer personal data to a third country or international organisation.
GDPR Article 13(2) checklist
Article 13(2) layers six further disclosures on top.
- Retention period or the criteria used to determine it.
- The right to access, rectify, erase, restrict, port, and object.
- The right to withdraw consent at any time, where processing is based on consent.
- The right to lodge a complaint with a supervisory authority.
- Whether the data subject is obliged to provide the data and the consequences of failing to do so.
- The existence of automated decision-making, including profiling, and meaningful information about the logic involved.
Four disclosures we see missing most often
1. Legitimate interest specifics
Stores relying on legitimate interests (typical for fraud prevention or product analytics) state the basis but rarely state the specific legitimate interests. "To improve our services" is not specific. The Article 29 Working Party guidance, carried forward by the EDPB, is that the interests pursued must be identifiable to a level that allows the data subject to weigh them.
2. Recipients of personal data
Article 13(1)(e) requires recipients or categories. "Third-party service providers" is a category that EDPB guidance has called insufficient. A defensible disclosure names the categories with enough specificity that a reader can identify the kinds of processors involved (payment processor, email service provider, analytics provider, customer support platform).
3. Retention period or criteria
"As long as necessary" is not a criterion. A criterion is something a reader can evaluate. "For 90 days after order fulfilment for customer support purposes, for 7 years after invoice issuance for tax record-keeping obligations" is a criterion.
4. Right to lodge a complaint
Article 13(2)(d) requires disclosure of the right to lodge a complaint with a supervisory authority. The relevant DPA depends on the controller's establishment and the affected data subjects. EU stores often omit this entirely or reference "the relevant data protection authority" without naming one.
ApplicationThe Spanish AEPD has issued more sanctioning decisions for Article 13 disclosure failures than for any other GDPR article. The pattern in those decisions is that the policy exists but a specific 13(1) or 13(2) item is missing or generic.
Comment nous testonsComplianceGuardHQ does not assume your privacy policy fails Article 13. We read it in its native language (one of 15 EU languages we cover) and check it against every 13(1) and 13(2) sub-requirement, returning the specific items missing with the exact section we expected to find them in. Run a free scan to find out which line items are missing from your policy.
Questions fréquentes
What is GDPR Article 13?
Article 13 of the General Data Protection Regulation lists the information a controller must provide to a data subject at the moment personal data is collected directly from the subject. It applies to any data collection on a public storefront.
How is Article 13 different from "having a privacy policy"?
Article 13 is prescriptive. It lists 12 specific items (six in 13(1), six in 13(2)) that must be communicated. A privacy policy is the typical vehicle for the disclosures, but the policy must contain each item to satisfy the article.
What is the most common GDPR Article 13 failure?
Generic recipient disclosures ("third-party service providers" without specifying categories), missing or vague retention criteria, and missing reference to the right to lodge a complaint with a supervisory authority. The Spanish AEPD has issued the most decisions on these specific failures.
When does Article 13 information have to be provided?
At the time the data is collected. For a web form, that is on the page that contains the form, not in a separate document linked from the footer. Most storefronts satisfy this by linking the privacy policy directly under the form fields.
Does Article 13 require the privacy policy to name a specific DPA?
Yes, where one applies. Article 13(2)(d) requires disclosure of the right to lodge a complaint with a supervisory authority. The relevant authority depends on establishment and data subject location. Naming the specific authority (for example, the Hamburgischer Beauftragte for a Hamburg-established controller) is best practice.
Lancer la vérification sur votre boutique
ComplianceGuardHQ exécute des contrôles automatisés sur 8 textes européens contre votre boutique en environ 60 secondes. Scan de référence gratuit, sans installation.
Lancer un scan gratuitComplianceGuardHQ exécute un scan technique automatisé. Les constats citent le texte des directives et la précédence d'application. Ils ne constituent pas un conseil juridique. Pour une interprétation contraignante dans votre juridiction, consultez un avocat qualifié ou un délégué à la protection des données.