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

WooCommerce · Guide

WooCommerce and GDPR: What to Set Up

Short answer

WooCommerce is not GDPR compliant on its own: it ships the settings and tools, and you must set them up. Publish a privacy policy, set retention periods under WooCommerce, then Settings, then Accounts and Privacy, add a cookie consent banner, and answer export and erasure requests with the WordPress privacy tools. This guide is setup help, not legal advice.

Key takeaways

  • WooCommerce ships GDPR tools, but the store is not compliant until you set them up.
  • GDPR has applied since 25 May 2018 to any store selling to people in the EU.
  • EU fines reach 20 million euros or 4% of worldwide annual turnover for the most serious breaches.
  • Set retention periods under WooCommerce, then Settings, then Accounts and Privacy.
  • WordPress tools under Tools handle export and erasure requests, but they do not reach backups.

What does GDPR require from a WooCommerce store?

GDPR requires your store to collect only the data it needs, tell customers why, keep it only as long as needed, and answer their requests about it.

The law has applied since 25 May 2018 to any store that sells to people in the EU. The UK has its own version, UK GDPR, with the same shape.

The ICO, the UK regulator, lists seven data protection principles: lawfulness, fairness and transparency; purpose limitation; data minimisation; accuracy; storage limitation; integrity and confidentiality; and accountability. See A guide to the data protection principles.

Fines can be high. Article 83(5) of the EU GDPR allows fines of up to 20 million euros or 4% of worldwide annual turnover, whichever is higher. See Article 83 of the GDPR.

The ICO states the same top tier for UK GDPR as up to 17.5 million pounds or 4% of worldwide annual turnover. The same ICO guide states this figure.

Integrity and confidentiality is one of the seven principles, which is why store security matters for GDPR too. See Is WordPress Secure? What the Vulnerability Data Shows

This guide is setup help, not legal advice. Rules differ by country and by business, so check your setup with a data protection lawyer or your national regulator.

What do you need before you start?

You need admin access, a list of every plugin and service that touches customer data, and a draft privacy policy.

WooCommerce's docs for Subscriptions list the data a store records, including IP address, browser user agent, billing and shipping addresses, phone number, email address, and payment gateway tokens. See Subscriptions and the GDPR.

WooCommerce's developer guide for extensions asks developers to list the personal data they collect and to assess and document any third-party sharing. The same list helps store owners. See GDPR compliance guidelines for WooCommerce extensions.

List every third party that receives data: your payment gateway, shipping provider, email tool, analytics tool, and any plugin that sends data elsewhere.

Note how long you keep each type of data. Tax rules often set the floor for order records, so ask your accountant before you pick a short period.

Data your store holdsWhere it livesWhy you hold it
Name, email, addressWooCommerce ordersFulfilment and tax records
Phone numberWooCommerce ordersDelivery contact
IP address, browser typeOrder records, logsFraud checks and security
Payment tokensPayment gatewayRepeat payments and refunds
Account detailsWordPress user profilesLogin and order history

How do you publish and assign a privacy policy?

Publish a privacy policy page, then assign it under Settings, then Privacy, so WooCommerce can link to it from checkout.

  1. In WordPress, go to Settings, then Privacy, and click Create to build a new page, or pick an existing page from the list.
  2. Click Use This Page to assign it as your privacy policy.
  3. Edit the page to describe what you collect, why, how long you keep it, and who else receives it.
  4. Publish the page and check that it opens from your site footer or menu.

WordPress includes a privacy policy guide that suggests text for the page, and WooCommerce adds its own suggested text about store data. WordPress.org's privacy docs describe the guide. See WordPress Privacy.

WooCommerce's Accounts and Privacy settings let you add a [privacy_policy] shortcode to the registration and checkout notices, which becomes a link to the page. See Accounts and Privacy Settings.

The policy must name the third parties that receive data, such as your payment gateway and shipping provider. A policy that omits them does not match what the store does.

How do you set data retention in WooCommerce?

Set retention periods under WooCommerce, then Settings, then Accounts and Privacy, in the Personal data retention section.

  1. Go to WooCommerce, then Settings, then Accounts and Privacy.
  2. Scroll to Personal data retention.
  3. Set a period for each item: retain inactive accounts, pending orders, failed orders, cancelled orders, refunded orders, and completed orders.
  4. Click Save changes, then write the same periods into your privacy policy.

For each option, enter a number and pick days, weeks, months, or years, and leave an option blank to keep that data indefinitely. WooCommerce's Accounts and Privacy doc states this rule. See Accounts and Privacy Settings.

WooCommerce deletes inactive accounts after the period you set, and anonymises personal data in old orders. Inactive means the account has not logged in or ordered for that long. The same doc explains this.

WooCommerce's own docs warn to state your retention periods in your privacy policy and to make sure they fit the law that applies to you. The same doc states this.

If you run Subscriptions, ended subscriptions have their own setting, Retain ended subscriptions, under the same section. WooCommerce's Subscriptions GDPR doc gives the path. See Subscriptions and the GDPR.

How do you handle export and erasure requests?

Answer export and erasure requests with the WordPress tools under Tools, then Export Personal Data and Tools, then Erase Personal Data.

  1. A customer asks for a copy of their data. Open Tools, then Export Personal Data, enter their email, and send the confirmation.
  2. Once they confirm by email, generate the export and send them the zip file WordPress builds.
  3. For erasure, open Tools, then Erase Personal Data, enter their email, and follow the same confirmation flow.
  4. Confirm the erasure. Deleted data is removed from the database and cannot be undone.

WordPress.org's privacy docs say the export tool gathers data from WordPress and participating plugins only, so third-party services need separate handling. See WordPress Privacy.

The same docs say erasure does not remove data from backups or archive files, and does not delete the registered user account on its own. The same WordPress.org page states this.

WooCommerce adds its own data to the exporter and eraser, and lets you remove personal data from orders on request. WooCommerce's Accounts and Privacy doc explains the setting. See Accounts and Privacy Settings.

You can also remove personal data from orders in bulk: open WooCommerce, then Orders, pick orders, choose Remove personal data from Bulk actions, and click Apply. WooCommerce's doc on removing personal data gives these steps. See Removing personal data from orders.

Add a cookie consent banner that blocks tracking cookies until the visitor agrees, since consent must come before tracking.

Add the banner before any tracking runs, not after. A banner that loads after the tracking script has already set cookies does not give real choice.

WordPress.org's privacy docs note that WooCommerce records products viewed, IP address, browser type, and shipping address, plus cookies that track cart contents. See WordPress Privacy.

For the setup steps, see How to Add a Cookie Consent Banner to WordPress

List every cookie the store sets in your privacy policy, including those from analytics, payment, and chat tools.

How do you check the setup worked?

Walk through the store as a customer: register, check out, and ask for your own data.

  1. Open the checkout page and confirm the privacy notice and policy link appear.
  2. Register a test account, place a test order, then ask for an export from Tools, then Export Personal Data.
  3. Open the export file and confirm it lists the order, address, and account details.
  4. Run an erasure on the test account and confirm the personal data is gone from the order.
  5. Open the site in a private window and confirm the cookie banner appears before tracking loads.

Check retention too: open WooCommerce, then Settings, then Accounts and Privacy, and confirm every period matches your privacy policy.

WooCommerce also offers a Data Privacy Manager that adds a customer privacy centre under My Account, then Data Privacy, for exports, erasure, and corrections. Its export download links stay available for 3 days by default. See Data Privacy Manager.

For the wider WordPress side of this setup, see GDPR Compliance for WordPress: What Applies to Your Site

What mistakes should you avoid?

The most common mistake is treating a plugin install as compliance, when the settings, policy, and request process still need doing by hand.

  • Install a consent banner and stop there. Retention, erasure, and the privacy policy still need setting up.
  • Keep data forever. Set a retention period for every type of order and account, and write it in your policy.
  • Ignore third-party tools. Your payment gateway, email tool, and analytics provider each hold customer data too.
  • Erase data on request without checking tax rules. Some order records must be kept for tax, even after an erasure request.
  • Forget the backups. Erasure does not reach backup files, so your backup retention period is part of your answer.

Review the setup every year, or whenever you add a plugin, a payment method, or a new market. A store's data map goes out of date fast.

Integrity and confidentiality is one of the seven principles, so lock the store down too. See How to Add Security Headers to WordPress

Frequently asked questions

Does installing WooCommerce make my store GDPR compliant?

No. WooCommerce ships the settings and tools, but the store is not compliant until you set them up. You must publish a privacy policy, set retention periods, add cookie consent, and answer export and erasure requests. A consent plugin alone does not cover retention, erasure, or the policy, so work through each part of this guide.

How long should I keep WooCommerce order data?

It depends on your tax law, which often sets the floor for order records. Pick a period for each type of order under WooCommerce, then Settings, then Accounts and Privacy, and write the same periods in your privacy policy. Leaving a retention option blank keeps that data indefinitely, which is rarely the right choice.

Do I need a cookie banner for WooCommerce?

Yes, if your store uses tracking or analytics cookies, which most WooCommerce stores do. The banner must appear before tracking loads, and it must let visitors refuse. WooCommerce sets cookies that track cart contents, so list them in your privacy policy along with cookies from analytics, payment, and chat tools.

Can a customer ask me to delete their order?

Yes, a customer can ask you to erase their personal data, and you should use Tools, then Erase Personal Data to do it. Tax rules may still require you to keep some order records, so check with your accountant first. Erasure also does not remove data from backups, so your backup retention period is part of your answer.

What happens if I ignore a data request?

Ignoring a data request can lead to a complaint to your national regulator, and fines can be high. Article 83(5) of the EU GDPR allows fines of up to 20 million euros or 4% of worldwide annual turnover for the most serious breaches. Answer requests on time, keep a record of what you did, and ask a lawyer if a request is unclear.

Sources

  1. A guide to the data protection principles ICO
  2. Art. 83 GDPR - General conditions for imposing administrative fines GDPR.eu
  3. WordPress Privacy WordPress.org
  4. Accounts and Privacy Settings WooCommerce
  5. Removing personal data from orders WooCommerce
  6. GDPR compliance guidelines for WooCommerce extensions WooCommerce Developer Docs
  7. Subscriptions and the GDPR WooCommerce
  8. Data Privacy Manager WooCommerce

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