Pro free for 30 days.No card.Start free →

GDPR basics for a small business serving EU customers

A plain-English introduction to GDPR for small businesses that sell to people in the EU: when the law applies, the key principles, lawful bases, customer rights, the 72-hour breach clock and a practical checklist.

By WorkBOS Content Desk8 min read
European Union flags on flagpoles outside a government building (Photo by Dusan_Cvetanovic on Pixabay)
Photo: Dusan_Cvetanovic / Pixabay

If you sell to people in Europe, even occasionally, a European privacy law may apply to you no matter where your business is based. The General Data Protection Regulation, usually shortened to GDPR, is the rule set that governs how organisations collect, use and keep information about people in the European Union. Many owners hear about it only when a customer asks for their data to be deleted, which is a stressful moment to start learning.

This guide explains the basics for a small business: when GDPR applies, the handful of ideas that matter most, what customers can ask of you, and a practical checklist to work through. It is general information, not legal advice. Rules differ by country and situation, so talk to a qualified privacy lawyer about your own case.

Does GDPR apply to your business?

The European Commission says a company established outside the EU is covered if it offers goods or services to individuals in the EU or monitors their behaviour. Free services count as well as paid ones. Its example of a non-EU provider that is not covered is one that serves only customers outside the EU, some of whom happen to use the service while travelling in Europe.

Signs you are probably in scope

  • Your website sells to EU countries, ships there or accepts euros.
  • Your site or marketing is written in an EU language or aimed at EU buyers.
  • You track visitors from the EU with analytics, ad pixels or similar tools.
  • You employ, contract or market to people who live in the EU.

Signs you probably are not

  • You serve only a local US market and people merely visit from abroad.
  • You do not target EU residents and do not monitor their behaviour.

Size helps a little but does not remove the duty. The Commission notes that a small business covered by the law must generally comply, though some obligations, such as appointing a data protection officer, may not apply when handling personal data is not a core part of what you do and the activity does not create risks for individuals.

The key terms in plain English

  • Personal data: information that relates to an identified or identifiable living person. Names, emails, addresses, phone numbers, IP addresses and customer IDs all count.
  • Controller: the organisation that decides why and how personal data is used. That is usually you.
  • Processor: a company that handles data on your behalf, following your instructions. A payroll provider or email platform is a typical example.
  • Data subject: the person the data is about.
  • Processing: almost anything you do with the data, including collecting, storing, using, sharing and deleting it.

Data that has been pseudonymised, such as replacing names with codes, is still personal data if someone could link it back. Only truly anonymous data falls outside the rules.

The principles you are expected to follow

The Commission describes the principles as: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; and integrity and confidentiality, with accountability alongside. In everyday terms:

  1. Be open. Tell people what you collect, why and how long you keep it, in clear language.
  2. Use data only for the reason you gave. Do not collect for one purpose and quietly reuse it for another.
  3. Collect the minimum. If you do not need a date of birth to sell a candle, do not ask for one.
  4. Keep it accurate. Correct mistakes when you learn about them.
  5. Do not hold it forever. Keep data only as long as you need it for the stated purpose. Our guide on data retention and deletion helps you set periods.
  6. Protect it. Use sensible technical and organisational safeguards. See our cybersecurity basics.
  7. Be able to show your work. Keep simple records of what you do and why.

You need a lawful reason to use personal data

Before you use personal data you need a lawful basis, and you should write it down. The UK regulator's guide lists the original six bases that mirror the EU's: consent, contract, legal obligation, vital interests, public task and legitimate interests. The guide stresses that none is inherently better than the others and that most require the processing to be necessary, not merely useful.

For a small business the common ones are:

| Situation | Likely basis | Note | |---|---|---| | Fulfilling an order or running a paid service | Contract | Covers data needed to deliver what the customer bought | | Keeping invoices for tax | Legal obligation | Retention follows the legal rule | | Marketing emails to people who signed up | Consent | You must be able to prove it and honour withdrawal | | Basic fraud prevention or security | Legitimate interests | Write down your balancing reasoning |

Consent deserves care. It must be a real choice, and the ICO points out that if someone withdraws consent you generally cannot switch to a different basis for the same processing. Choose consent only when you are willing to stop if asked.

What customers can ask of you

The Commission lists the rights as being informed, access, rectification, erasure, restriction of processing, data portability, objection, and rights relating to automated decision-making. Two come up most for small businesses.

Access requests

A person can ask what you hold about them. The ICO's small business guidance says you have one calendar month to respond, and in complex cases you can take up to two more months if you tell the person before the first month ends. You should avoid asking for formal ID unless it is necessary and proportionate, and you can check identity with questions only the requester could answer. Your reply should include their data and information about why you hold it, who you share it with and how long you keep it. Redact details about other people.

Erasure and objection requests

People can ask you to delete data you no longer need or to stop using it for marketing. Plan a routine for finding the person across your tools, deciding whether a legal duty requires you to keep anything (such as invoices), and confirming the outcome in writing.

A practical GDPR checklist

  1. Map where personal data lives: email, spreadsheets, accounting, CRM, shared drives, forms, backups.
  2. List why you use each type and write down the lawful basis.
  3. Publish a clear privacy notice that covers what you collect, why, who receives it and how long you keep it.
  4. Check every supplier that touches customer data and make sure a written agreement covers it.
  5. Set retention periods and a deletion routine.
  6. Decide who handles access and erasure requests and how fast.
  7. Set a simple breach plan. Our guide to responding to a data breach walks through it.
  8. Review cookies and trackers. See cookie consent basics.
  9. Train anyone who handles customer data, and limit access to those who need it.
  10. Write down these decisions and review them yearly.

Data breaches and the 72-hour clock

If a breach is likely to put people's rights and freedoms at risk, the European Commission says you must tell the supervisory authority within 72 hours of becoming aware of it, and tell the individuals affected when the risk is high. Encryption can reduce the risk and may remove the need to notify individuals. Processors must tell the controller about every breach.

Common mistakes

  • Assuming you are too small. Size is not an exemption; targeting EU residents is what matters.
  • Pre-ticked boxes and bundled consent. Consent must be specific and freely given.
  • Collecting everything "just in case". Excess data is excess risk.
  • No record of why you hold data. Without it, you cannot answer a request or a regulator.
  • Ignoring suppliers. If a vendor mishandles your customers' data, you still have questions to answer.
  • Treating a privacy policy as a one-off. Update it when your practices change.
  • Missing the deadline on requests. Put a date on the calendar the day a request arrives.

Where WorkBOS fits

GDPR compliance is about your decisions and habits, and no software makes a business compliant on its own. That said, it is easier to answer a request when customer records live in one place instead of five inboxes. WorkBOS keeps contacts, deals, invoices, projects and files together, uses roles and permissions to limit who sees what, and keeps an audit log of who did what, which supports the "be able to show your work" principle. The Free plan covers up to five users. Our docs and Academy explain how to set up roles, and the guide on who should see what is a good companion.

Frequently asked questions

Q: Does GDPR apply to a US business with no office in Europe? A: It can. The European Commission says non-EU organisations are covered if they offer goods or services to people in the EU or monitor their behaviour. Serving only non-EU customers who happen to travel in Europe does not trigger it.

Q: Do I always need a data protection officer? A: No. Some small businesses are not required to appoint one when handling personal data is not a core activity and creates little risk for individuals, but a firm whose main work involves personal data may not qualify for that relief. Ask a professional.

Q: How long do I have to answer a request for someone's data? A: Under the UK regulator's guidance, one calendar month from receipt, with a possible two-month extension for complex requests if you notify the person in time. Check your national authority's guidance for the exact EU rule, and treat one month as a safe working deadline.

Q: Can I keep customer data forever? A: Generally no. Data should be kept only as long as needed for the purpose you stated, unless a law requires longer, such as tax records.

Q: Is an email list covered? A: Yes. Email addresses relating to identifiable people are personal data, and marketing to them usually needs a lawful basis such as consent.

This is general information and not legal advice. Sources are linked in the text above: European Commission (who GDPR applies to, data protection explained) and the UK Information Commissioner's Office (lawful basis, handling requests).

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →