Most small businesses do not fail at GDPR because of one big mistake. They fail because of a handful of small gaps: no written record of what data they hold, a privacy notice that does not match reality, no plan for a breach. The good news is that these gaps are fixable in days. This checklist covers the ten areas that matter most, with the article of the GDPR behind each.

πŸ› οΈ
Free tool
Want a score first?

Answer 10 questions and get your GDPR score and priority gaps in 3 minutes.

Take the free GDPR check

1. Know what personal data you process (Article 30)

Write down what personal data you handle, why, who receives it, how long you keep it and how it is protected. That list is your record of processing activities. Start with the obvious ones: payroll, customers and invoicing, your website contact form, your newsletter, recruitment. See our guide on whether you need a RoPA.

Every use of personal data needs one of six legal bases, such as consent, contract, legal obligation or legitimate interests. Choose one per purpose and say so in a privacy notice written in plain language. The notice must describe what you actually do, not what a template says.

3. Be able to answer data subject requests within one month (Articles 12 to 22)

People can ask to access, correct, delete or move their data, or object to its use. You generally have one month to respond, which can be extended by up to two further months for complex or numerous requests. Decide who receives requests, how you verify identity, and keep a log. A reply template saves time.

4. Have a breach plan that works inside 72 hours (Articles 33, 34)

If a personal data breach is likely to result in a risk to people, you must notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it. Every breach, reportable or not, must be documented. If the risk to individuals is high, you must also tell them.

The European Commission has proposed in its Digital Omnibus to extend this deadline to 96 hours and to raise the threshold to high-risk breaches. As of the latest status we found (October 2026) that proposal was still in Parliament committee, so the 72-hour rule applies. Check the current status before you rely on any change.

5. Sign data processing agreements with your vendors (Article 28)

Hosting, email, CRM, payroll and AI tools usually process personal data on your behalf. You need a written data processing agreement with each, and you should know where the data is stored and whether it leaves the EEA.

6. Apply basic security (Article 32)

Use multi-factor authentication, encrypt laptops and phones, keep tested backups, give people only the access they need and remove accounts when staff leave. Regulators look for proportionate measures, not perfection.

7. Screen new projects for high risk and run a DPIA when needed (Article 35)

A data protection impact assessment is required when processing is likely to be high risk, for example large-scale monitoring, sensitive data, profiling or new technology. Add a short screening question to every new tool or project so you catch these early.

8. Set retention periods and delete on time (Article 5)

Keep personal data no longer than you need it. Set a period per category, such as accounting records for the period your national law requires, and schedule the deletion or anonymisation.

9. Train your people

Most incidents start with a person: a wrong recipient, a lost device, a phishing click. A short yearly training, with attendance recorded, plus a one-page do and do not sheet covers the basics and shows accountability.

10. Control AI tools

Staff paste customer data into AI tools every day. Decide which tools are approved, what may never be entered and who reviews the output. Read our guide on an AI acceptable-use policy, and note that the EU AI Act adds its own transparency and AI literacy duties (see Article 50 explained).

What does non-compliance cost?

The GDPR allows fines of up to 20 million euros or 4 percent of worldwide annual turnover for the most serious infringements, and up to 10 million euros or 2 percent for others. In practice, regulators weigh size, intent and cooperation, and small businesses are more likely to meet warnings, orders and reputational damage first. Do you also need a data protection officer? Only in specific cases, such as large-scale monitoring or large-scale processing of sensitive data as a core activity.

Where to start this week

Share this article
⚠️ This article is for informational purposes only and does not constitute legal advice. For complex compliance situations, consult a qualified data protection professional. GDPR and EU AI Act requirements are subject to ongoing regulatory guidance β€” verify current obligations with your legal adviser.