GDPR and personal data protection
EU regulation that sets how businesses may process personal data
What is GDPR and personal data protection?
GDPR (General Data Protection Regulation) is European Union Regulation 2016/679, which since 25 May 2018 has set how companies, public bodies and sole traders may collect, use, store and delete people's personal data. Personal data is any information about an identifiable person: a name, email address, phone number, IP address, an identifier stored in a cookie or an order history. The regulation applies directly in every EU member state, so the core rules are the same across the EU. It gives people rights over their data and requires organisations to be able to show why and how they handle it.
Why It Matters
Practically every business with a website processes personal data: contact forms, e-shop orders, newsletters, CRM and analytics. Breaching GDPR can lead to a fine from the supervisory authority, compensation claims and lost customer trust, typically after a data leak or a complaint from someone receiving unwanted emails. Well-designed processes are more than a legal duty: the business knows what data it holds, where it sits and who can access it, which makes running the website, marketing and automations safer.
Real-World Examples
- 1A contact form collects only a name, email and message and links to the privacy notice next to the submit button.
- 2The newsletter goes only to people who subscribed or to existing customers, and every email contains an unsubscribe link.
- 3The business has a data processing agreement with its hosting provider, email marketing tool and CRM.
- 4A customer asks for a copy of their data and the business sends it within one month.
- 5After a customer database leak, the business reports the incident to the supervisory authority within 72 hours.
What the GDPR abbreviation means and which laws apply
GDPR stands for General Data Protection Regulation. Officially it is Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016, which has applied since 25 May 2018. It replaced the older Directive 95/46/EC and the national laws based on it.
Because it is a regulation, it applies directly without being transposed into national law. Member states only adopted supplementary acts, for example on the age at which a child can consent to online services (16 by default, 15 in Czechia under Act No. 110/2019 Coll., 16 in Slovakia under Act No. 18/2018 Coll.). Each country has its own supervisory authority, such as the Czech ÚOOÚ or the Slovak Office for Personal Data Protection.
The UK applies its own UK GDPR after Brexit; this entry covers the EU regulation.
Who GDPR applies to
GDPR applies to anyone who processes personal data in the course of business or an organisation's activities, regardless of size. That includes a sole trader with a simple website, an e-shop, an association or a municipality. The only exception is processing for purely personal or household purposes, such as private contacts on your phone.
Location matters too: GDPR covers organisations established in the EU and also organisations outside the EU that offer goods or services to people in the EU or monitor their behaviour (Article 3).
In practice there are two roles:
- Controller decides why and how data is processed. Typically your business, which runs the website and receives enquiries.
- Processor processes data on the controller's behalf and instructions. Typically hosting, an email tool, a CRM, an accountant or an agency maintaining the website.
A controller may only use processors that provide sufficient guarantees and must have a contract or terms with them under Article 28.
Principles and lawful bases for processing
All processing must meet the principles in Article 5: lawfulness and transparency, purpose limitation, data minimisation, accuracy, storage limitation, security and accountability (the business must be able to demonstrate compliance).
You also need one of the six lawful bases in Article 6:
- Consent – for example a newsletter sign-up.
- Contract or steps before entering into one – fulfilling an order, replying to an enquiry.
- Legal obligation – for example keeping invoices under accounting rules.
- Vital interests – rare in ordinary business.
- Public task – mainly public authorities.
- Legitimate interests – for example protecting the website from abuse or reasonable marketing to existing customers.
So consent is not needed for everything. A common mistake is asking for consent where a contract is enough and then not knowing what to do when someone withdraws it.
Which rights GDPR gives people
Everyone whose data you process has the right to be informed, to access their data and get a copy, to rectification, to erasure (the 'right to be forgotten'), to restriction of processing, to data portability and to object, for example to direct marketing.
You must respond without undue delay and within one month at the latest. For complex or numerous requests the deadline can be extended by two further months, but you must tell the person about the extension within the first month.
GDPR on your website: what to handle in practice
The business website is where GDPR and marketing meet most often. Check these points:
- Privacy notice: a separate page stating who the controller is, what data you collect, for what purpose, on which lawful basis, for how long, who receives it and what rights people have (Article 13). Link it in the footer and next to forms.
- Contact and enquiry forms: collect only what you need to reply. Handling an enquiry does not require consent; informing people is enough. A pre-ticked consent box is not valid consent.
- Newsletter: marketing emails generally need prior consent, with a narrow exception for existing customers and similar products under national e-privacy rules, and every message must offer an easy unsubscribe. More in our email marketing guide.
- Cookies and analytics: analytics and advertising cookies and the cookie banner are governed mainly by e-privacy law, but the data they collect falls under GDPR. Google Consent Mode, which passes the banner choice to Google tools, and your Google Analytics 4 setup belong here too.
- Security: an encrypted SSL / HTTPS connection, an up-to-date CMS and plugins, strong passwords and two-factor login to the admin, regular backups. Store sensitive data encrypted (see data encryption).
- Processors and tools: map where website data flows (hosting, email tool, CRM system, payment gateway) and check the processing agreements. For US services, check certification under the EU-US Data Privacy Framework, which the Commission approved on 10 July 2023 and the EU General Court upheld in September 2025.
- AI tools: put customer personal data only into tools covered by a business data processing agreement, not free consumer versions. The same applies to AI assistants and chatbots on your website.
- Records: keep an overview of the data you process (records of processing activities, Article 30). The exemption for organisations under 250 employees does not apply when processing is not occasional, which is usual for customer data.
The technical side (forms, banner, security, tool integrations) is handled by whoever takes care of website maintenance or builds your site; in our website development projects we cover it from the start. Legal documents and risk assessments belong with a lawyer or data protection officer; this entry is not legal advice.
Data breaches, DPOs and fines
If a personal data breach occurs (a leaked database, a lost laptop, data sent to the wrong recipient) and it poses a risk to people, you must report it to the supervisory authority within 72 hours of becoming aware of it (Article 33). If the risk is high, you must also inform the people affected. Phishing is a frequent trigger of breaches.
A data protection officer (DPO) is mandatory for public authorities and for organisations whose core activities involve large-scale systematic monitoring of people or large-scale processing of sensitive data. A typical small business with a website does not have to appoint one.
Fines under Article 83 have two tiers: up to €10 million or 2% of worldwide annual turnover, and for more serious breaches (principles, lawful bases, people's rights) up to €20 million or 4% of turnover, whichever is higher. Authorities take into account severity, intent and the organisation's cooperation.
Upcoming changes: Digital Omnibus
In November 2025 the European Commission proposed simplifying parts of the GDPR and cookie rules in its Digital Omnibus package. The Council of the EU adopted its negotiating mandate on 21 October 2026, including a longer deadline for breach notifications and fewer obligations for low-risk processing. The changes still have to be negotiated with the European Parliament, so the current rules described above apply until they are adopted and take effect.
Frequently asked questions
What is GDPR in simple terms?
GDPR is the EU's data protection regulation, which since 25 May 2018 has set how businesses and organisations may collect, use and delete data about people. It requires every processing activity to have a purpose and lawful basis, to be secure, and to let people check, correct or delete their data.
Who does GDPR apply to?
GDPR applies to anyone who processes personal data in the course of business or an organisation's activities, including sole traders, small e-shops, associations and municipalities. It also applies to non-EU businesses offering services to people in the EU. Only purely personal use, such as private phone contacts, is excluded.
Do I need consent for a website contact form?
No, if you use the data only to reply to the question or enquiry. The lawful basis is taking steps towards a contract, so linking to your privacy notice next to the form is enough. You need consent if you want to use the same data for another purpose, such as sending a newsletter to people who are not your customers.
What are the fines for breaching GDPR?
The maximum fine is €20 million or 4% of worldwide annual turnover for serious breaches and €10 million or 2% for others. The actual amount depends on severity, duration, the number of people affected and the organisation's cooperation with the authority. Small businesses usually face lower penalties or corrective orders.
Does a small business need a data protection officer?
Usually not. A DPO is mandatory for public authorities and for organisations whose core activities involve large-scale systematic monitoring of people or large-scale processing of sensitive data, such as health data. Other businesses may appoint one voluntarily, but they always remain responsible for GDPR compliance themselves.