Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Security · Explainer

GDPR Compliance for WordPress: What Applies to Your Site

Short answer

The GDPR applies to most WordPress sites that collect personal data from people in the EU, including names, emails, and IP addresses from comments, forms, accounts, and analytics. You need a lawful basis for each use of that data, a clear privacy notice, a way to answer visitor requests within one month, and consent before non-essential cookies. WordPress includes built-in privacy tools for export and erasure requests, but no plugin alone makes a site compliant, and this guide is general information, not legal advice.

Key takeaways

  • The GDPR has applied since 25 May 2018 to any site handling personal data of people in the EU, wherever the site owner sits.
  • Every processing purpose needs one of six lawful bases, and consent is only one of them.
  • Visitors can ask for a copy of their data or its deletion, and you must usually answer within one month.
  • Non-essential cookies need clear consent first, and withdrawing consent must be as easy as giving it.
  • WordPress 4.9.6 added built-in tools for privacy policies, personal data export, and erasure requests.
  • A personal data breach must be reported to the supervisory authority within 72 hours where feasible.

What is the GDPR?

The GDPR is the European Union law that sets the rules for how personal data is collected, stored, and used.

Its full name is the General Data Protection Regulation, Regulation (EU) 2016/679, and it has applied since 25 May 2018, as the EUR-Lex summary states.

The law replaced the 1995 Data Protection Directive with one set of rules that applies directly in every EU member state. It also gives people clear rights over their own data. This guide gives general information only, not legal advice, so check with a qualified adviser for your own situation.

The regulation rests on 7 principles in Article 5:

  • Lawfulness, fairness, and transparency
  • Purpose limitation
  • Data minimisation
  • Accuracy
  • Storage limitation
  • Integrity and confidentiality
  • Accountability

Fines can reach 20 million euros or 4% of total worldwide annual turnover for the most serious breaches, and 10 million euros or 2% for other breaches, as of November 2026. Regulators can also order you to stop processing or to fix the problem.

Does the GDPR apply to your WordPress site?

The GDPR applies to your site if you handle personal data of people in the EU, even if your business sits outside the EU.

Your Europe, the EU help service, states that the rules cover EU-based organisations and non-EU organisations that offer goods or services to people in the EU or monitor their behaviour there. A blog with EU readers, a shop with EU buyers, or a form that collects EU visitor emails can all fall inside that scope.

If your business has no EU base but the rules still reach you, you must appoint a representative in the EU. The Irish Data Protection Commission notes the same test in its FAQ on business coverage: targeting people in the European Economic Area is enough, even when no payment is involved.

The rules do not apply to purely personal activity, to data about a legal person such as a company, or to data of a person who has died. A personal site that never collects visitor data sits outside the rules, but most WordPress sites collect at least some data.

Do small sites need a data protection officer?

Most small sites do not need one. Your Europe states that a data protection officer is required for public authorities and for businesses whose core work involves large-scale monitoring or large-scale processing of special categories of data.

If you do appoint one, that person monitors your data handling, advises staff, and acts as the contact point for your supervisory authority and for visitors.

When do you need a data protection impact assessment?

A data protection impact assessment is mandatory when planned processing is likely to pose a high risk to people's rights, such as using new technology at scale. Your Europe lists this as a core duty, and the assessment must happen before the processing starts.

What counts as personal data on a WordPress site?

Personal data is any information that relates to an identified or identifiable living person.

Names, email addresses, IP addresses, device identifiers, location data, and online identifiers all count. A comment with a name and email, a contact form entry, a user account, and an analytics cookie can each hold personal data.

Where data appearsWhat it collectsExample
CommentsName, email, IP addressA reader leaves a comment on a post
User accountsUsername, email, profile detailsA member registers on the site
Contact formsName, email, messageA visitor asks a question
AnalyticsIP address, device data, pages viewedA visit is logged by a stats tool
BackupsCopies of all the aboveA daily backup stores the database

Some data gets extra care, such as health details, religious beliefs, and political views. Most small sites never collect these, but a health survey or a membership form could, so check your own forms before you assume they do not.

What are the six lawful bases for processing data?

You need at least one of six lawful bases from Article 6 before you process personal data.

Consent is only one of the six, and it is often the wrong pick for things you must do to run the site. Pick the basis that fits each purpose, record it, and tell visitors about it in your privacy notice.

Lawful basisWhen it fits a WordPress siteExample
ConsentThe visitor agrees to a specific useNewsletter signup, non-essential cookies
ContractNeeded to deliver what the visitor asked forProcessing an order, creating an account
Legal obligationThe law requires itKeeping invoices for tax
Vital interestsNeeded to protect a lifeRare on most sites
Public taskNeeded for a public authority taskRare on most sites
Legitimate interestsNeeded for your aims, balanced against visitor rightsSecurity logs, fraud checks

Legitimate interests is the most flexible basis, but it needs a balance check against visitor rights. Security logging and fraud checks often fit here, while marketing emails and analytics cookies usually need consent instead.

If you use analytics, compare your options in our Google Analytics vs privacy-friendly analytics for WordPress guide before you pick a tool.

What records should you keep?

Keep a record of what data you collect, why you collect it, where it goes, and how long you keep it. Small and medium businesses can skip formal records unless the processing is regular, risky, or involves sensitive data, as the EUR-Lex summary notes.

What rights do visitors have over their data?

Visitors can ask what data you hold, ask for a copy, and ask you to fix or delete it.

Articles 12 to 22 of the GDPR give visitors these rights:

  • The right to be informed about collection and use of their data
  • The right of access to their data
  • The right to rectification of inaccurate or incomplete data
  • The right to erasure, often called the right to be forgotten
  • The right to restrict processing
  • The right to data portability in a machine-readable format
  • The right to object to processing
  • Rights on automated decision-making

You must answer most requests within one month. You can extend that by 2 more months for requests that are complex or numerous, as long as you tell the person why within the first month.

Visitors can also complain to their supervisory authority if they think you handled their data badly. WordPress has built-in tools for export and erasure requests, covered later in this guide.

You need consent before setting cookies that are not strictly necessary, such as analytics and marketing cookies.

Consent must be freely given, specific, informed, and unambiguous, and it needs a clear affirmative action. Silence, scrolling, and pre-ticked boxes do not count as consent, as Recital 32 of the GDPR states.

Withdrawing consent must be as easy as giving it, and you must be able to show that consent was given. Keep a record of when and how each visitor agreed, and put a clear cookie settings link on every page.

Cookies that are strictly necessary for the site to work, such as a login session cookie, do not need consent. You should still name them in your privacy or cookie notice and say what they do.

Do not block access to your content until visitors accept cookies. A banner with no reject option fails the freely given test, so offer a clear reject choice next to accept.

GDPR.eu explains that consent is only valid when the visitor makes a real choice, and that visitors who refuse some cookies should still be able to use the service.

How do WordPress privacy tools help with GDPR requests?

WordPress has built-in tools for privacy policy pages, personal data export, and personal data erasure.

The tools arrived in WordPress 4.9.6, according to the Plugin Handbook privacy page. They sit under Tools in the dashboard, and the policy guide sits under Settings then Privacy.

ToolWhere to find itWhat it does
Privacy Policy guideSettings then PrivacyHelps you build a policy page
Export Personal DataTools then Export Personal DataCreates a zip file of a user's data
Erase Personal DataTools then Erase Personal DataDeletes a user's personal data after checks

Both request tools use email checks. The visitor confirms the request by email, and an admin must approve it before data is sent or deleted. The developer docs note that export files expire after 3 days by default.

These tools only gather data from WordPress and plugins that take part, so they miss data held by outside services such as analytics and newsletter tools. The WordPress Privacy documentation states this limit plainly.

Erasure also leaves backup copies alone and does not delete the user account itself, so plan for those gaps. Newsletter data lives outside these tools, so check how your email tool handles requests in our Mailchimp vs WordPress newsletter plugins guide.

What happens after a data breach?

If personal data is breached, you must tell your supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it.

The 72-hour clock starts when you become aware of the breach, not when the incident first happened. If you miss the deadline, you must give reasons for the delay, and you must keep a written record of every breach, its effects, and what you did about it.

If a processor such as your host or email service finds the breach first, it must tell you, the controller, without undue delay. Your written contract with each processor should spell out that duty, as Article 28 requires.

Tell the affected people directly, without undue delay, when a breach is likely to put their rights at high risk. Use plain language, say what happened, and say what they can do next. The EUR-Lex summary covers these duties.

Good security lowers breach risk. Keep WordPress, themes, and plugins updated, use strong passwords, and serve the site over HTTPS. Our Cloudflare SSL settings for WordPress guide covers the HTTPS setup.

What mistakes should you avoid?

The most common mistakes are collecting data without a lawful basis, hiding the privacy notice, and assuming a plugin alone makes the site compliant.

  • Collecting data with no lawful basis, such as adding every form entry to a marketing list without consent.
  • Using pre-ticked newsletter boxes or a banner with no reject option.
  • Assuming a consent plugin alone makes the site compliant. The plugin is a tool, and your policy, cookies, and data handling still matter.
  • Forgetting backups. Erasure tools do not clean backup copies, so set a retention limit and check it in our cPanel backup vs plugin backup guide.
  • Keeping data forever. Set retention periods and delete what you no longer need.
  • Collecting form data you never use. Cut unneeded fields, and use spam protection settings for your forms in our WPForms spam protection settings guide.

Frequently asked questions

Does the GDPR apply to my small WordPress blog?

It applies if your blog collects personal data from people in the EU, and most blogs do through comments, contact forms, user accounts, analytics, or server logs. IP addresses count as personal data. If your site truly collects nothing and has no EU visitors, it likely falls outside the rules, but check what your site and plugins store before you assume that.

Do I need a cookie banner on my WordPress site?

You need consent before setting cookies that are not strictly necessary, such as analytics and marketing cookies. If your site only uses strictly necessary cookies, such as a login session cookie, you do not need a banner for them, but you should still explain them in your notice. Any banner you use must offer a real reject choice next to accept.

Can a plugin make my WordPress site GDPR compliant?

No. A plugin can add a banner, consent checkboxes, and request forms, but compliance also depends on your privacy policy, your lawful bases, your contracts with processors, and how you handle data in practice. WordPress core tools help with export and erasure requests, but they do not cover data held by third-party services such as analytics and newsletter tools.

How long do I have to answer a data request?

You must answer most requests within one month. You can extend that by 2 more months for requests that are complex or numerous, as long as you tell the person why within the first month. Use the built-in tools under Tools in the WordPress dashboard to handle export and erasure requests, and keep a note of when each request arrived.

Do I need a data protection officer for a small site?

Usually not. A data protection officer is required for public authorities and for businesses whose core work involves large-scale monitoring of people or large-scale processing of special categories of data. A small blog or shop rarely meets that test, but you can still name a contact person for privacy questions on your site.

Sources

  1. General data protection regulation (GDPR) EUR-Lex
  2. Data protection under GDPR Your Europe
  3. WordPress Privacy WordPress.org
  4. Privacy Related Options, Hooks and Capabilities WordPress Developer Resources
  5. Is my business covered by the GDPR? Data Protection Commission Ireland
  6. GDPR.eu GDPR.eu

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test