Blog / How the internet works /
GDPR basics for small websites
Somebody emails you with the word “GDPR” in capitals and a vague threat. Or a customer from Europe asks what you do with their details. Suddenly a simple website feels like a legal problem.
It mostly isn’t, if you cover the basics. This post is a plain guide, not legal advice. For anything high-stakes, ask a qualified professional in your country.
What GDPR is
The General Data Protection Regulation (GDPR) is a European Union law, in force since 2018, about how organisations handle personal data. The UK has its own version that works very similarly. Many countries have copied the same ideas into local laws.
It can apply to you even if you’re not in Europe. If your website targets people in the EU or UK, or you monitor their behaviour, you should assume the rules matter. That’s true of plenty of small sites run from places like Nigeria or Qatar that attract European visitors.
What counts as personal data
More than people think. Anything that can identify a person, directly or in combination:
- Names, emails, phone numbers and addresses.
- IP addresses and online identifiers.
- Cookie IDs and advertising IDs.
- Photos and customer account details.
- Comments people leave on your blog.
If your site has a contact form, a newsletter box, comments, a shop, analytics or ads, you’re handling personal data.
The core ideas
You don’t need to memorise the whole law. These ideas cover most small sites.
Have a reason (a lawful basis)
You need a legitimate reason for each use of personal data: the person agreed (consent), you need it to fulfil an order (contract), you’re legally required to keep it, or you have a genuine business interest that doesn’t override their rights.
Collect only what you need
A newsletter box needs an email address. It doesn’t need a phone number and date of birth. Fewer fields means less to protect.
Be open about it
Tell people what you collect, why, and how long you keep it. That lives in your privacy policy.
Keep it safe
Use HTTPS, strong passwords, updated software, backups and limited access. The security basics are the same ones that keep a site healthy in general; see website security basics: five things that stop most attacks.
Respect people’s rights
People can ask what you hold about them, ask you to correct it, ask you to delete it, or object to certain uses. You should know where the data lives so that you can actually do that.
A practical checklist for a small site
- List what you collect and where it goes. Contact form, newsletter provider, analytics, shop, comments, ad networks. One page of notes is enough.
- Write a privacy policy in plain words that matches that list. A copied one that describes things you don’t do is worse than none.
- Get consent where it’s required. Non-essential cookies (advertising, some analytics) need a clear opt-in in many places. Don’t pre-tick boxes. I explained the cookie side in cookie banners: what the law asks for and cookie banners and consent mode v2 in plain English.
- Make newsletter sign-up explicit. A separate, unticked checkbox or a clear sign-up form, not hidden in terms. Keep a record of when someone signed up.
- Sign data processing terms with your providers where they offer them (email service, analytics, hosting). Most big providers have a standard agreement you simply accept.
- Set a retention rule. Decide how long you keep enquiries, old customer records and inactive subscribers, then actually delete.
- Have a way for people to contact you about their data, and know who answers.
- Know what to do if there’s a breach. A short plan: who to tell, how to find out what leaked, how to notify people. Serious breaches can need reporting to the regulator within 72 hours. See data breaches: what to do when your email shows up for the personal side of the same problem.
Tools worth turning off or tightening
- Analytics settings: shorten data retention, anonymise IP addresses where the tool allows it, and don’t collect what you won’t use.
- Contact form plugins that store every submission forever. Delete old entries or turn storage off.
- Comment plugins and chat widgets that load third-party scripts you don’t need.
Myths
- “GDPR only applies to big companies.” It applies to organisations of any size, though small ones have lighter paperwork.
- “A cookie banner makes me compliant.” A banner is one piece. If it’s decorative and the scripts still load regardless, it doesn’t help.
- “I’m outside Europe, so it’s irrelevant.” Not if you serve European visitors or customers.
- “Fines will bankrupt a small blog.” The headline fines go to large offenders. Regulators do consider size and effort, but carelessness is still not a defence.
Key takeaways
- Know what personal data your site touches.
- Collect less, explain clearly, secure it, and delete on schedule.
- Get real consent for non-essential cookies and marketing emails.
- Keep a short record of your choices.
- Get professional advice if you handle sensitive data or operate at scale.
FAQ
Do I need a data protection officer?
Usually not for a small website. The requirement applies to certain large-scale or sensitive processing.
Is a privacy policy template enough?
It’s a start, but edit it until it matches what you really do.
Related reading
Open your site’s contact form, newsletter box and analytics settings in a row. For each one, can you say where the data ends up and when it gets deleted? Start with the one you can’t answer.