GDPR for small businesses is not a lighter version of the law; the same rules apply to a three-person studio and a multinational, and what changes with size is mostly how much paperwork you can reasonably be asked to produce and how likely a regulator is to care.
That sentence disappoints two groups. The first group believes the GDPR is only for giants, because they heard that Meta and Amazon got the big fines, and they carry on collecting emails in a spreadsheet shared with six freelancers. The second group is terrified, buys a 90-page policy template, and still cannot say where their customer data actually lives. Both are in the same position. Neither has done the one useful thing, which is to find out what personal data they hold, why, and who else touches it.
This guide to GDPR for small businesses is written for owners and founders, not privacy specialists. It covers whether the GDPR applies to you at all (including if you are outside the EU), what you must actually do, which exemptions help and which do not, how fines work and what has happened to small firms, what the Digital Omnibus proposals would change, and a plan you can finish in a month. A short section covers India’s new data protection law for readers who run businesses there. There are ten FAQs at the end.
Does GDPR for small businesses apply to you?
Size is not the test. Location and activity are. Article 3 of the General Data Protection Regulation covers three situations:
- You are established in the EU (a company, branch or office there) and you process personal data in the context of that establishment. It does not matter where the servers are.
- You are outside the EU but you offer goods or services to people in the EU, whether or not they pay.
- You are outside the EU but you monitor the behaviour of people in the EU, as far as that behaviour takes place in the EU. Tracking visitors across your site with analytics and ad pixels can count.
For the second situation, the recitals say that a website being reachable from the EU is not enough. Signs that you are targeting EU customers include using an EU language or currency that you would not otherwise use, shipping to EU countries, EU phone numbers, a “.eu” or country domain, marketing aimed at EU residents, or mentioning EU customers. The European Data Protection Board (EDPB) published guidelines on this territorial scope, and they are the document to read if you are borderline. That is my summary of the guidance from general knowledge, not a quote, so check the EDPB text if you are on the line.
Three things people get wrong:
- “We are B2B.” Business contact details are personal data when they relate to a named person. An email like priya.sharma@company.com is personal data. Your sales list is covered.
- “We are too small.” There is no small-business exemption from the Regulation. There are limited reliefs, covered below.
- “We are in the UK.” The UK has its own version, the UK GDPR, with the Data Protection Act 2018, now amended by the Data (Use and Access) Act 2025, and its own regulator, the ICO. The rules are close but they are not the same law.
If you are outside the EU and caught by the second or third situation, Article 27 generally requires you to appoint a representative in an EU country where your customers are, with exceptions for occasional processing that is low risk and does not involve large-scale sensitive data. I describe this from the text as I know it. Confirm it for your case.
GDPR for small businesses: the vocabulary in four lines
- Personal data: anything that relates to an identifiable person. Names, emails, phone numbers, IP addresses, device IDs, photos, order history.
- Controller: whoever decides why and how personal data is used. That is you, for your customers and staff.
- Processor: a vendor that handles data on your instructions: your email tool, payroll provider, cloud host, accountant.
- Special category data: health, biometrics, race, religion, sexual orientation, trade union membership, political opinions, genetic data. Handled under stricter rules.
What GDPR for small businesses actually requires
Here is the real list, with the article numbers so you can check.
1. Know what data you hold
Before any policy, map it. For each system (CRM, email platform, payroll, website forms, CCTV, accounting), note what data is in it, whose, where it came from, why you have it, who sees it, where it is stored, and how long you keep it. This map is the foundation for everything below. It takes an afternoon for a small firm and nobody can comply without it.
2. Have a lawful basis for each use (Article 6)
Every use of personal data needs one of six lawful bases: consent, contract, legal obligation, vital interests, public task, or legitimate interests. Consent is the one everyone reaches for and usually the worst fit, because it can be withdrawn at any time and must be freely given, specific, informed and unambiguous.
| What you are doing | Usually the right basis |
|---|---|
| Delivering an order you were paid for | Contract |
| Keeping invoices for tax | Legal obligation |
| Paying staff | Contract and legal obligation |
| Sending marketing emails to people who signed up | Consent (EU e-privacy rules also apply) |
| Fraud checks on your own checkout | Legitimate interests |
| Analytics and advertising cookies | Consent, under the cookie rules |
| Emailing existing customers about similar products | Often e-privacy “soft opt-in” rules, which vary by country |
Where you use legitimate interests, write a short assessment: what you want, why you need this data for it, and why it does not override the person’s rights. Three paragraphs is fine. Keep it.
3. Tell people what you do (Articles 13 and 14)
In GDPR for small businesses the privacy notice is the visible part, so get it right. It should say who you are, what data you collect, why, on what basis, who you share it with, whether it goes outside the EU, how long you keep it, and what rights people have, including how to complain to a regulator. It must be easy to find and in plain language. Put the link where you collect data: forms, checkout, sign-up.
4. Handle people’s rights (Articles 12 to 22)
Individuals can ask to see their data, correct it, erase it, restrict it, take it with them, or object to some uses. You generally have one month to respond, which can be extended by up to two further months for complex or numerous requests, with notice to the requester. Set up a simple route: a named person, a mailbox, a log with dates, and a rule for checking who is asking. Most requests from customers are routine. The trouble comes from not recognising a request when it arrives in a Facebook message or a reply to a newsletter.
5. Records of processing (Article 30), and the 250-employee point
Article 30 asks controllers and processors to keep a record of processing activities. Article 30(5) says the obligation does not apply to organisations with fewer than 250 employees, unless the processing is likely to result in a risk to people’s rights, is not occasional, or includes special categories or criminal-offence data.
In practice, for GDPR for small businesses that “unless” swallows most of the exemption. If you process payroll every month, the processing is not occasional, so a small employer usually needs a record anyway. This is the common reading among practitioners, and I have not found a regulator statement that says otherwise, but get advice on your case. The easy fix: the data map from step 1 is nearly your record already. Add purposes, categories of data and people, recipients, transfers, retention and a general description of security measures.
6. Security (Article 32)
You must use measures appropriate to the risk: access controls, multi-factor authentication, encryption on laptops and phones, backups, patching, and staff who know not to forward customer spreadsheets to personal email. The ICO says that weak security is one of the most common reasons it fines small organisations. A lost unencrypted laptop with customer files is the classic example.
7. Contracts with your vendors (Article 28)
In GDPR for small businesses, vendors are where the quiet risk sits. If a supplier processes personal data for you, you need a written agreement that covers the points in Article 28: instructions, confidentiality, security, sub-processors, help with rights requests and breaches, deletion or return at the end. Most big SaaS vendors have a data processing addendum you accept online. Make sure you have accepted it, and keep a list of processors. For freelancers and small agencies who touch your data, put the clause in the contract. Our guides on the MSA vs SOW, the indemnification clause and the limitation of liability clause explain where those clauses fit.
8. Breaches (Articles 33 and 34)
For GDPR for small businesses the practical rule is: log everything. A personal data breach is not only hacking. Sending an email to the wrong list, losing a phone or leaving a database open all count. If a 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. If the risk is high, you must also tell the individuals. You must record every breach, including the ones you decide not to report (Article 33(5)). The 72 hours starts when you become aware, which regulators read as when you have a reasonable degree of certainty that a breach has happened. I am recalling that from EDPB guidance rather than reading it today, so verify it.
9. Data Protection Officer (Article 37)
Under GDPR for small businesses, most firms do not need one. A DPO is mandatory for public bodies, and for organisations whose core activities involve large-scale regular and systematic monitoring of individuals, or large-scale processing of special category or criminal data. A clinic with thousands of patient records or an ad-tech business might. A shop with a mailing list does not. If you appoint one voluntarily, the legal duties of the role still attach, so choose carefully. National laws, such as Germany’s, add their own DPO thresholds.
10. Impact assessments (Article 35)
A data protection impact assessment is required where processing is likely to result in a high risk, such as large-scale profiling, large-scale sensitive data, or systematic monitoring of public areas. Regulators publish lists of processing that needs one. In GDPR for small businesses it rarely arises, but note that new tools using AI on customer data can trigger it.
11. Transfers outside the EU (Chapter V)
Under GDPR for small businesses, using a US email tool or an Indian support team means data may leave the EU. You need a transfer tool: an adequacy decision for the destination, standard contractual clauses, or another mechanism. Large vendors usually build this into their addendum. For your own overseas staff and contractors, you will need it yourself.
12. Cookies and marketing
These sit under the e-privacy rules, not only the GDPR. In general, non-essential cookies and trackers need prior opt-in consent, and an accurate banner with a “reject” button as easy as “accept”. Direct email and SMS marketing is governed by national laws implementing the e-privacy rules. If you run a website with analytics and ads, this is where most complaints about small businesses start.
GDPR for small businesses: real fines and what happens in practice
The headline numbers are in Article 83. There are two tiers:
- up to €10 million or 2% of worldwide annual turnover, whichever is higher, for breaches of obligations such as security, records, breach notification, processor contracts and DPO duties;
- up to €20 million or 4%, whichever is higher, for breaches of the basic principles, lawful basis and consent, individuals’ rights and international transfers.
Those are ceilings. Regulators must set fines that are effective, proportionate and dissuasive and consider factors in Article 83(2): how serious and how long the infringement was, whether it was intentional or negligent, the steps taken to limit damage, past history, cooperation, and the type of data involved.
What happens in practice under GDPR for small businesses? Fines do reach small controllers. As one example from the public enforcement tracker, the Slovenian data protection authority fined a sole trader €5,000 on 6 January 2026 for sending personal data to unauthorised recipients, a breach of the data-minimisation principle in Article 5(1)(c). The ICO says its focus with small and medium organisations is on supporting compliance, “and not on fines”, and lists the situations that most often lead to fines: weak security, treating compliance as a one-off exercise, electronic marketing breaches (mostly under the PECR rules in the UK) and a reactive approach, as well as non-payment of the data protection fee.
Fines are not the only exposure in GDPR for small businesses. Article 82 allows individuals to claim compensation for damage, regulators have corrective powers other than fines, such as warnings, reprimands and orders to stop processing (Article 58), and customers and enterprise buyers increasingly ask for proof of compliance in procurement. My own experience is that for small firms, a warning or order is more common than a fine, but I do not have a statistic for that, and you should not rely on it.
Digital Omnibus: what changes for GDPR for small businesses (and why not to wait)
The EU has proposed changes, and there is a lot of noise about them. The honest position in November 2026 is that they are proposals.
- The package. The European Commission published the Digital Omnibus on 19 November 2025. Among its GDPR changes, per a White & Case summary, are: a contextual definition of personal data (information would not be personal data for an entity that cannot identify the person using means reasonably likely to be used), breach notification to authorities only for high-risk breaches with the deadline extended from 72 to 96 hours and a single reporting entry point, the right to refuse or charge for access requests that abuse the right, and a new route to rely on legitimate interests for AI development.
- Pushback. The EDPB and the European Data Protection Supervisor adopted Joint Opinion 2/2026 on 10 February 2026. They strongly urged the legislators not to adopt the new personal-data definition, which they said would narrow the GDPR beyond simplification. They did support the breach-notification reform. The opinion is advisory.
- Timing. The proposal goes through the Council and Parliament. Sources I read give estimates of adoption around mid-2027 or late 2026 to the first half of 2027, plus a transition period before changes apply. Those are forecasts, not dates. A summary from a compliance firm also says the Parliament and Council reached agreement on the AI part of the package in May 2026, with formal adoption pending.
- Small-company record-keeping. A separate simplification proposal, the fourth Omnibus of 21 May 2025, would raise the employee threshold in the Article 30 derogation from 250 to 750 and limit mandatory record-keeping to high-risk processing, and extend codes of conduct and certification to “small mid-cap” companies. A law-firm summary describes it as a proposal. I could not confirm whether it has been adopted, so check the official EU position before you rely on it.
Practical advice for GDPR for small businesses: comply with the law as it stands. Nothing above is in force, and a data map, a privacy notice and a breach log will survive any version of the final text.
GDPR for small businesses in India
India’s Digital Personal Data Protection Act, 2023 has its Rules, notified on 14 November 2025. Per India Briefing, the Data Protection Board was set up immediately, the consent manager rules apply after 12 months, and the core obligations on businesses (consent notices, purpose limitation, children’s data, retention and erasure, security safeguards) apply after 18 months, which puts them around May 2027. Penalties can reach ₹250 crore per breach depending on the violation, with a graded structure intended to protect MSMEs. Breach reporting runs to the Board and affected individuals, with a detailed report to the Board within 72 hours.
So an Indian business that sells to EU customers, uses EU data or has EU visitors may need to meet both regimes. The good news for GDPR for small businesses and the Indian law alike is that the same data map, notice and vendor discipline serves both. For the wider legal checklist for founders, see our legal checklist for Indian startups.
GDPR for small businesses: a ten-minute self-test
Answer these honestly. Every “no” is a task.
- Can you list every tool that holds customer or staff personal data?
- Do you know which lawful basis covers each use?
- Does your privacy notice match what you really do, and is it linked from every form?
- Have you accepted or signed a data processing agreement with each vendor?
- Do you know where your data goes outside the EU?
- Could someone in your team recognise a rights request and know who to pass it to?
- Do you have a breach log and a person who decides within hours whether to report?
- Do you delete things on a schedule?
Enterprise buyers now ask about these points in supplier questionnaires, so GDPR for small businesses is increasingly a sales issue and not only a legal one.
A 30-day plan for a small business
Here is a month-by-month way to get GDPR for small businesses done without hiring anyone.
Week 1: find out what you have. List your systems, the data in each and the vendors. Decide who is responsible for privacy, even if it is the founder. Note any special category data and any data of children.
Week 2: fix the basics. Choose a lawful basis for each activity and write it down. Rewrite the privacy notice to match what you actually do, and link it from every form. Turn off non-essential cookies until consent.
Week 3: lock down vendors and security. Accept or sign data processing agreements, check where data is transferred, switch on multi-factor authentication, encrypt devices, and cull accounts for people who have left.
Week 4: build the habits. Create a one-page rights-request procedure and a breach log with a “who to call” list. Write a retention schedule (how long you keep customer, job applicant and employee data) and delete what you do not need. Brief staff for thirty minutes.
Then calendar a review every six months, and every time you add a new tool or a new use for data.
Common mistakes in GDPR for small businesses
- Treating consent as the answer to everything.
- Believing a B2B list is outside the Regulation.
- Copying another company’s privacy policy that describes things you do not do.
- Pre-ticked boxes, or “by using this site you consent”.
- Using vendors with no processing agreement.
- Keeping everything forever “just in case”.
- Sending customer data to the wrong person by email, and not logging it as a breach.
- Having no way to recognise a rights request.
- Assuming a fine is the only risk.
Most failures of GDPR for small businesses come from skipping the data map, not from exotic legal points.
For terms used in this guide, our contract law glossary is a short reference, and if you need help with a privacy notice, a vendor agreement or a breach, contact us or see the startup legal section.
Frequently asked questions
1. Does the GDPR apply to small businesses?
Yes. There is no general exemption for small businesses. GDPR for small businesses works the same way as for large ones: the Regulation applies if you are established in the EU, or if you offer goods or services to people in the EU or monitor their behaviour. Size affects how much you are expected to document, not whether the rules apply.
2. Does GDPR for small businesses reach companies outside the EU?
GDPR for small businesses can reach you from abroad. Under Article 3, a business outside the EU is caught if it offers goods or services to people in the EU or monitors their behaviour there. A website that is merely reachable from the EU is not enough. Shipping to EU countries, pricing in euros or targeting EU customers is the kind of thing that tips it.
3. Does GDPR for small businesses require a Data Protection Officer?
Usually not. Under GDPR for small businesses a DPO is mandatory for public bodies and for organisations whose core activities involve large-scale regular and systematic monitoring or large-scale special category or criminal data. A small firm with a customer list and payroll data does not meet that test. National laws can add their own thresholds.
4. Does GDPR for small businesses exempt firms under 250 employees from record-keeping?
Only partly. Article 30(5) exempts them unless the processing is likely to risk people’s rights, is not occasional, or includes special category or criminal data. Regular payroll processing is not occasional, so many small employers still need a record. A 2025 proposal would raise the threshold to 750 employees, but I could not confirm that it has been adopted.
5. What are the fines under GDPR for small businesses?
The ceilings in GDPR for small businesses are €10 million or 2% of worldwide turnover for the lower tier and €20 million or 4% for the higher tier, whichever is higher. Actual fines on small firms are far lower. A Slovenian sole trader was fined €5,000 in January 2026 for sending data to unauthorised recipients, for example.
6. Do I need consent to email my customers?
Not always for the GDPR, but the e-privacy rules in each country matter more here. Marketing to people who signed up usually relies on consent. For existing customers, many countries allow a “soft opt-in” for similar products if you offered an easy opt-out, but the rules vary. Check the law of the country where the recipient is.
7. What should I do if I have a data breach?
For GDPR for small businesses the first hour matters: contain it, find out what happened, and record it. If it is likely to risk people’s rights, notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware. If the risk is high, tell the affected people as well. Log every breach, including ones you do not report.
8. How long do I have to answer a subject access request?
In GDPR for small businesses the clock is generally one month from receiving it, extendable by up to two more months for complex or numerous requests, with notice to the person. Verify their identity, but do not use that as a way to delay. The Digital Omnibus would let controllers refuse or charge for abusive requests, but it is only a proposal.
9. Does GDPR for small businesses require a cookie banner?
If your site uses non-essential cookies or trackers such as ad pixels and some analytics, then under GDPR for small businesses and the e-privacy rules you generally need prior opt-in consent and an easy way to refuse. Strictly necessary cookies do not need consent. The cookie rules sit mainly in the e-privacy law, not only the GDPR.
10. Will the Digital Omnibus make GDPR for small businesses easier?
It might, in places, such as breach reporting thresholds and record-keeping, but it is not law. The EDPB and EDPS have opposed its new definition of personal data. Estimates put adoption in 2027 with a transition period afterwards. Comply with the current rules and review when the text is final.
This article is general information, not legal advice. Data protection law differs by country and is changing, so check the current rules or get advice on your own situation.

