GDPR has been enforced since May 2018. By 2026, European data protection authorities have issued over €4 billion in fines and the pace is accelerating. Yet the most common violations are not sophisticated data architecture failures — they are basic oversights: missing lawful bases, pre-ticked cookie consent boxes, unsigned DPAs, and unanswered subject access requests.

This checklist covers the seven areas that regulators examine first. For each area, there is a clear statement of what you must do and the most common violation that triggers enforcement action.

Area 1: Privacy Policy

What you must do:

Your privacy policy must be publicly accessible (typically linked in the website footer), written in plain language, and cover every processing activity your website carries out.

Mandatory content under Article 13 and 14 of GDPR:

  • Identity and contact details of the data controller (you)
  • Data Protection Officer contact (if you have one)
  • What personal data you collect (email addresses, IP addresses, cookie identifiers, payment data, etc.)
  • The purpose of each processing activity
  • The lawful basis for each purpose (see Area 4)
  • Data retention periods for each category
  • Third-party recipients and processors
  • International data transfers and safeguards (e.g., Standard Contractual Clauses for US processors)
  • All eight data subject rights
  • Right to lodge a complaint with a supervisory authority

Common violation: A privacy policy that was generated once in 2018 and never updated. Adding a new analytics tool, a chatbot, or an email newsletter without updating the privacy policy is a violation.

What you must do:

Non-essential cookies (analytics, advertising, social media pixels) require explicit, informed, freely given consent before being set. This means:

  • No pre-ticked boxes
  • No cookies firing before consent is given
  • Granular options — users must be able to accept analytics without accepting advertising
  • An equally prominent "Reject All" option alongside "Accept All"
  • Easy withdrawal of consent at any time (a re-openable cookie preferences panel)

Common violation: "Soft" consent — displaying a banner that says "By using this site you agree to cookies" without any accept/reject mechanism. This was the basis of Google's €90 million fine by the French CNIL in 2022.

Area 3: Data Minimisation

What you must do:

Article 5(1)(c) of GDPR requires that personal data be "adequate, relevant and limited to what is necessary in relation to the purposes." In practice:

  • Contact forms should ask only for the information needed (name and email for a quote; don't add phone number if you won't call)
  • Do not store data longer than necessary for its original purpose
  • Delete or anonymise data on a defined schedule
  • Avoid collecting data "just in case it might be useful"

Common violation: Contact forms with 10 fields when three would suffice, or databases retaining customer data indefinitely with no deletion schedule.

Area 4: Lawful Basis for Processing

What you must do:

Every processing activity needs a lawful basis from Article 6 of GDPR. There are six:

Lawful basisWhen it appliesExample
ConsentThe individual has given clear, specific, informed consentSending a marketing newsletter
ContractProcessing is necessary to perform a contractProcessing an order, invoicing
Legal obligationProcessing is required by lawTax record keeping
Vital interestsProcessing is necessary to protect someone's lifeRarely applicable for websites
Public taskProcessing is in the public interestMainly public authorities
Legitimate interestsProcessing serves your legitimate business interests and is not overridden by individual rightsFraud prevention, analytics (contested — use carefully)

You must document the lawful basis for each processing purpose in your privacy policy and internal records. You cannot change the lawful basis retrospectively — if you start with consent, you must always be able to demonstrate that consent was given.

Common violation: Relying on "legitimate interests" as a catch-all for everything, without conducting and documenting a Legitimate Interests Assessment (LIA). Regulators have rejected this basis for advertising and extensive tracking.

Area 5: Third-Party Processor Agreements (DPAs)

What you must do:

Under Article 28, every third-party that processes personal data on your behalf must be covered by a signed Data Processing Agreement (DPA). This is not optional.

Common processors requiring DPAs:

Tool/serviceDPA location
Google Analytics / Google WorkspaceGoogle's data privacy settings / Google Admin
StripeStripe's Data Processing Agreement (accepted in dashboard)
MailchimpMailchimp's DPA (accepted in account settings)
AWS / Google Cloud / AzureAvailable in cloud console settings
Intercom / ZendeskAvailable in account/legal settings
Facebook Pixel / Meta AdsMeta's Data Processing Terms

Common violation: Using a processor without ever signing their DPA. Most providers make DPAs available in their settings — they are not automatically in force until you explicitly accept them.

Area 6: User Rights

What you must do:

GDPR grants individuals eight rights. Your website must have a mechanism for users to exercise each one, and you must respond within one calendar month.

RightWhat it meansYour obligation
Right to accessUser can request a copy of all their personal dataProvide a complete data export within 30 days
Right to erasureUser can request deletion of their dataDelete all data unless a legal obligation requires retention
Right to rectificationUser can request corrections to inaccurate dataCorrect data and inform any third parties who received it
Right to portabilityUser can request data in a machine-readable formatProvide data in CSV, JSON, or similar format
Right to restrict processingUser can pause processing while a dispute is resolvedStop processing (not necessarily delete)
Right to objectUser can object to processing based on legitimate interestsStop processing unless you can demonstrate compelling grounds
Rights re: automated decisionsProtection from solely automated decisions with legal effectsProvide human review on request
Right to withdraw consentUser can withdraw consent at any timeStop processing immediately; withdrawing must be as easy as giving

Common violation: No mechanism to receive or respond to data subject requests. A contact form labelled "Privacy Requests" with no defined internal process for handling requests within 30 days.

Area 7: Data Breach Response

What you must do:

Maintain an internal data breach response plan that covers:

  1. Detection and containment: Identify what data was affected and stop the breach
  2. Risk assessment: Is the breach likely to result in a risk to individuals' rights and freedoms?
  3. 72-hour notification: If yes, notify your national supervisory authority within 72 hours
  4. Individual notification: If high risk to individuals, notify them directly without undue delay
  5. Documentation: Record all breaches in an internal breach register, even those that do not require notification

Common violation: Not knowing that a breach has occurred — common when using unsecured third-party integrations — or knowing about a breach and not notifying the supervisory authority within the 72-hour window.

Full GDPR Compliance Checklist at a Glance

AreaRequirementStatus
Privacy policyPublished, plain language, covers all data types✅ / ❌
Privacy policyUpdated whenever new tools are added✅ / ❌
Cookie consentNon-essential cookies blocked before consent✅ / ❌
Cookie consentGranular options, equal reject/accept prominence✅ / ❌
Cookie consentEasy consent withdrawal mechanism✅ / ❌
Data minimisationForms collect only necessary fields✅ / ❌
Data minimisationRetention schedule defined and enforced✅ / ❌
Lawful basisDocumented for every processing purpose✅ / ❌
DPAsSigned with every third-party processor✅ / ❌
User rightsMechanism to receive and respond to requests✅ / ❌
User rights30-day response process in place✅ / ❌
Breach responseInternal response plan documented✅ / ❌
Breach response72-hour notification process understood✅ / ❌

Use our GDPR Privacy Policy Generator to create a compliant, up-to-date privacy policy with all mandatory fields. For cookie consent specifically, see our Cookie Consent Generator.