ComplianceCheckup

Compliance Checklist

GDPR Compliance Checklist (2026)

Authority: European Data Protection Board (EDPB)Updated: 2026-01Official source
Zeta Solutions|Compliance Research
Last verified: May 2026Zeta Solutions is a web and software studio that researches, builds, and maintains ComplianceCheckup.org.

This checklist covers the core operational requirements of the General Data Protection Regulation (GDPR) for organisations that collect or process personal data from EU or EEA residents. Each item cites the specific Article so you can verify the requirement directly in the official text at gdpr-info.eu. This checklist is a self-assessment starting point, not a substitute for legal advice.

Disclaimer: This checklist is for informational purposes only. It does not constitute legal advice and is not a substitute for advice from a qualified attorney or licensed compliance professional in your jurisdiction. Always consult a professional before making compliance decisions. Full disclaimer

Want to see how your website scores on GDPR? Run a free PrivacyGrader scan.

Grade my site
0%
0 of 30 items complete

Lawful Basis for Processing

Article 6Official source
Article 5(2)Official source
Article 9Official source
Articles 7–8Official source
Article 7(3)Official source

Privacy Notice & Transparency

Articles 12–14Official source
Article 12Official source
Article 12Official source
Articles 13–14Official source

Data Subject Rights

Article 15Official source
Article 16Official source
Article 17Official source
Article 18Official source
Article 20Official source
Article 21Official source

Data Protection by Design

Article 5(1)(c)Official source
Article 5(1)(e)Official source
Article 32Official source
Article 32Official source

Records & Documentation

Article 30Official source
Article 30(1)Official source
Article 30(5)Official source

Data Breaches

Article 33Official source
Article 34Official source
Article 33(5)Official source

Third Parties & Transfers

Article 28Official source
Article 28(1)Official source
Articles 44–46Official source

Data Protection Officer (DPO)

Article 37Official source
Articles 37–39Official source

What is GDPR and who does it apply to?

The General Data Protection Regulation (GDPR) is the European Union's comprehensive data privacy law, in force since May 25, 2018. It applies to any organisation — anywhere in the world — that collects, stores, or processes personal data belonging to EU or EEA residents. If your website is accessible from Europe and you collect email addresses, IP addresses, cookie identifiers, or any other personally identifiable information, GDPR applies to you. There is no minimum size exemption: a solo founder with a newsletter list of 100 EU subscribers is subject to GDPR.

The regulation defines two key roles: controllers (organisations that determine why and how personal data is processed) and processors (organisations that process data on behalf of controllers, such as cloud providers or email services). Both carry legal obligations under GDPR, and controllers must sign Data Processing Agreements (DPAs) with all processors under Article 28.

What are the consequences of GDPR non-compliance?

Fines are tiered under Article 83. Less serious violations — such as failing to maintain records of processing activities (Article 30) or not notifying a breach within 72 hours (Article 33) — can result in fines of up to €10 million or 2% of global annual revenue. More serious violations — such as processing data without a lawful basis (Article 6) or violating data subject rights (Articles 15–22) — can attract fines of up to €20 million or 4% of global annual revenue, whichever is higher. In 2023, total GDPR fines exceeded €2 billion for the first time.

Beyond financial penalties, supervisory authorities can issue warnings, reprimands, and orders to stop processing data entirely. The regulation is enforced by national Data Protection Authorities (DPAs) in each EU member state, coordinated by the European Data Protection Board (EDPB).

How to use this GDPR compliance checklist

Work through each category systematically. The checklist covers the seven GDPR principles from Article 5, the six lawful bases for processing from Article 6, and the eight data subject rights from Articles 15–22. Each item includes a reference to the specific GDPR article so you can verify the requirement directly in the official regulation text at gdpr-info.eu.

Start with your lawful basis for processing — you cannot lawfully process personal data without one, and this determines much of your compliance posture. Then work through data subject rights, which require internal processes to respond to requests within 30 days. If you also process health data, review our HIPAA checklist; if you serve California residents, review the CCPA checklist.

What this checklist is for, and what it is not

This checklist is for any organisation that collects or processes personal data from EU or EEA residents. It covers the core operational requirements a small to mid-sized business can self-assess: identifying a lawful basis for each processing activity, implementing data subject rights workflows, maintaining records of processing activities under Article 30, conducting Data Protection Impact Assessments where required under Article 35, signing Data Processing Agreements with vendors under Article 28, and meeting the 72-hour breach notification deadline under Article 33.

What it does not cover: jurisdiction-specific guidance from individual Data Protection Authorities (the German Datenschutzkonferenz, the UK ICO, and the Irish DPC each publish supplementary guidance that may apply to your specific sector); evolving legal interpretation of concepts such as legitimate interest and cookie consent; formal certification schemes under Article 42; or the specific requirements of GDPR's implementing regulations in each EU member state. Compliance requirements vary significantly based on your sector, the categories of data you process, and where your users are located. Last verified May 2026 against the official text at gdpr-info.eu.

Real-world GDPR enforcement cases

In May 2023, the Irish Data Protection Commission fined Meta Platforms Ireland €1.2 billion for transferring personal data of EU Facebook users to the United States in violation of Article 46 GDPR. Meta was relying on Standard Contractual Clauses, but the DPC found that U.S. surveillance law (specifically FISA Section 702) meant those SCCs did not provide an essentially equivalent level of protection. The fine was the largest in GDPR history and required Meta to suspend the transfers. The case demonstrates that international data transfers are a live enforcement risk, not a paperwork exercise.

In September 2022, the Irish DPC fined Meta €405 million for processing children's personal data contrary to Articles 5, 6, and 25 GDPR. The violation concerned Instagram's default public account settings for users aged 13 to 17, and the display of contact information in public-facing business account profiles for minors. The case illustrates that privacy-by-design under Article 25 is an active design obligation with real enforcement consequences, not a documentation checkbox.

In July 2021, Luxembourg's CNPD fined Amazon €746 million for processing personal data for advertising purposes without a valid legal basis under Article 6. Amazon's cookie-based advertising system loaded tracking cookies without obtaining genuine, freely given consent as required by Articles 4(11) and 7. The Amazon case reinforces that consent mechanisms that load advertising trackers by default before any user action do not meet GDPR's consent standard.

Common GDPR mistakes

Relying on legitimate interest without a balancing test. Legitimate interest under Article 6(1)(f) requires a three-part test: a legitimate purpose, necessity of the processing for that purpose, and a finding that your interests do not override the data subject's rights and freedoms. Organisations frequently treat legitimate interest as a blanket basis for any processing they consider reasonable. Without a documented balancing test, this basis will not survive regulatory scrutiny. See checklist item: documented lawful basis.

Pre-ticked consent boxes and bundled consent. Consent under Article 7 must be a freely given, specific, informed, and unambiguous indication through a clear affirmative action. Pre-ticked checkboxes, opt-out mechanisms, and consent bundled with terms of service are all invalid under GDPR. Many websites still fail this basic test, particularly for marketing emails and analytics cookies.

Generic or missing Data Processing Agreements. Article 28 requires a written DPA with every processor that handles personal data on your behalf. SaaS tools, analytics platforms, cloud infrastructure, email service providers, and payment processors are all typically processors. A DPA must specify the nature, purpose, duration, and type of data being processed. A generic addendum that does not reflect actual processing activities does not fulfil the obligation.

Missing DSAR deadlines. Articles 15 to 22 grant data subjects rights including access, rectification, erasure, and portability. Requests must be responded to within one month of receipt, extendable by two months for complex requests with written notice. Organisations with no DSAR workflow treating incoming requests ad hoc frequently miss this deadline.

US data transfers without a valid mechanism. Since Schrems II (CJEU, July 2020) invalidated the EU-US Privacy Shield, transfers to US processors require Standard Contractual Clauses supplemented by a transfer impact assessment, or self-certification of the US recipient under the EU-US Data Privacy Framework (in force from July 2023 under Decision 2023/1795). Many businesses still transfer data to US SaaS providers without checking either mechanism.

What changed in GDPR: 2024 to 2026

The European Commission adopted Adequacy Decision 2023/1795 in July 2023, establishing the EU-US Data Privacy Framework (DPF) as a valid transfer mechanism under Article 45. US companies self-certified under the DPF can receive personal data from the EU without SCCs. As of May 2026, over 2,500 US companies are DPF-certified. Privacy advocacy groups have indicated intent to challenge the DPF before the CJEU; verify the status of any legal challenge before relying on the DPF as your sole transfer mechanism.

The EDPB published Guidelines 3/2022 on Dark Patterns in Social Media Platforms (adopted September 2022), providing detailed examples of what constitutes deceptive UX design that violates GDPR consent requirements. In 2024 and 2025, multiple DPAs issued enforcement actions specifically targeting cookie banner design, making non-compliant consent flows one of the most actively enforced GDPR requirements.

Regulation (EU) 2024/1689 (the EU AI Act) entered into force in August 2024. For AI systems that process personal data, compliance overlaps significantly with GDPR obligations, particularly around data minimisation (Article 5(1)(c)), automated decision-making (Article 22), and transparency (Articles 13 to 14). If your product uses AI to process personal data, both frameworks apply concurrently. Last reviewed May 2026 by the Zeta Solutions editorial team.

Frequently Asked Questions

What is the maximum penalty for GDPR non-compliance?
The maximum fine under GDPR is €20 million or 4% of global annual revenue, whichever is higher (Article 83(5)). A lower tier of up to €10 million or 2% of global annual revenue applies to less serious violations such as record-keeping failures. In 2023, total GDPR fines exceeded €2 billion. Notable penalties include Meta (€1.2 billion), Amazon (€746 million), and Instagram (€405 million).
Does GDPR apply to US companies?
Yes. GDPR applies to any organisation that processes personal data of EU/EEA residents, regardless of where the organisation is based. If you have EU customers or website visitors from the EU and collect any data about them (including IP addresses via analytics), GDPR applies.
What are the fines for GDPR non-compliance?
GDPR fines operate in two tiers. Serious violations (unlawful processing, violating data subject rights, transferring data without safeguards) can reach €20 million or 4% of global annual turnover, whichever is higher. Less serious violations (technical requirements) can reach €10 million or 2%.
What counts as personal data under GDPR?
Personal data is any information relating to an identified or identifiable natural person. This includes names, email addresses, IP addresses, cookie identifiers, location data, photos, and any data that can be used alone or in combination to identify someone.
Do I need a cookie consent banner?
If you use non-essential cookies (analytics, advertising, session tracking beyond basic functionality), you need prior consent from EU users before setting those cookies. Implied consent and pre-ticked boxes are not valid. A properly implemented consent management platform (CMP) is the standard solution.
What is the difference between a controller and a processor?
A controller determines the purposes and means of processing — this is typically your business. A processor processes data on behalf of the controller — this is typically your vendors (cloud providers, analytics tools, email platforms). Both have obligations under GDPR, and you must have a DPA with every processor.

Related compliance checklists