How to Handle a WordPress Personal-Data Export or Erasure Request
How should a WordPress site respond to a valid request to export or erase a user’s personal data?
Register the requester in the appropriate WordPress personal-data tool, send the confirmation request and wait for confirmation before processing. For an export, process the confirmed request and check the intended recipient and observed result. For erasure, run the confirmed request and inspect the result for information a plugin reports as retained. Before closing either branch, verify which plugins and connected services were covered, investigate notification problems through the approved mail process, and assign every unresolved exception to an owner.
- WP Statistics says that enabling Record User Page Views records user IDs, which it describes as personal data.
- Compliant with WordPress Data Export and Erasure - WP Statistics · As of 2026-10-21
- WooCommerce describes a WordPress Tools → Erase Personal Data page that can send a confirmation request to the customer’s email or via their username.
- Right to Erasure Requests for GDPR with WooCommerce · As of 2026-10-21
- LifterLMS states that, once confirmed, a site administrator processes the request and an export concludes with an email to the user containing an attached ZIP file of their personal information.
- Handling User Data Export and Erasure Requests | LifterLMS · As of 2026-10-21
- WooCommerce says that information a plugin needs to retain is displayed at the end of the erasure process.
- Right to Erasure Requests for GDPR with WooCommerce · As of 2026-10-21
- WordPress documents a filter for the recipient of the personal-data export email notification.
- Privacy Related Options, Hooks and Capabilities – Plugin Handbook | Developer.WordPress.org · As of 2026-10-21
Identify what the site stores about the requester
WP Statistics says that it does not collect personal data by default. That product-specific default can begin a configuration review, but it does not prove that another plugin, an enabled option or a connected service is data-free. List every component that may receive, create or retain information linked to the requester, and assign an owner to each unresolved coverage question.
Sources: Compliant with WordPress Data Export and Erasure - WP Statistics.
WP Statistics says that enabling Record User Page Views records user IDs, which it describes as personal data. Check live settings, integrations and storage locations because an optional feature can change the data that must be considered for a request.
Sources: Compliant with WordPress Data Export and Erasure - WP Statistics.
- List the WordPress features, plugins and connected services that may hold requester-linked information.
- Review enabled settings as well as defaults.
- Record verified coverage, unknowns and the owner of each component.
Register the request and obtain confirmation
WooCommerce describes a WordPress Tools → Erase Personal Data page that can send a confirmation request to the customer’s email or via their username. Register the request through the appropriate WordPress privacy tool, keep its status visible to the responsible operator and use the confirmation workflow before processing it. This operational process does not establish every identity-verification requirement, legal exemption or response deadline, so obtain appropriate advice where those issues matter.
Sources: Right to Erasure Requests for GDPR with WooCommerce.
Record the requester identifier, request type, date received, confirmation status, components in scope and person responsible for the next action.
- Create the request in the relevant WordPress privacy tool.
- Send the confirmation request and preserve the existing request record.
- Do not release or erase information from an unconfirmed email alone.
Complete an export through WordPress and participating plugins
LifterLMS states that, once confirmed, a site administrator processes the request and an export concludes with an email to the user containing an attached ZIP file of their personal information. For a confirmed export, process the request in WordPress and check the relevant components, intended recipient and observed outcome before recording completion. Confirm current provider prerequisites in each component’s documentation before taking an irreversible or service-affecting action.
Sources: Handling User Data Export and Erasure Requests | LifterLMS.
WP Statistics says it exports or erases its relevant data when WordPress tools are used. Treat participation as component-specific: document which plugins were checked and escalate any plugin or external service whose contribution cannot be verified.
Sources: Compliant with WordPress Data Export and Erasure - WP Statistics.
- Process only the confirmed export request.
- Check which participating components contribute requester-linked information.
- Verify the intended recipient and preserve an outcome record.
Run erasure and review what was retained
WooCommerce says that WordPress, WooCommerce and many extensions work together to erase a person’s personal data. Run erasure as a coordinated check of participating components, while recognising that the vendor statement does not prove every installed plugin or connected service is included. Keep the result with the request record and avoid declaring completion until every exception has an owner and documented decision.
Sources: Right to Erasure Requests for GDPR with WooCommerce.
WooCommerce says that information a plugin needs to retain is displayed at the end of the erasure process. Record the exact displayed outcome, responsible component and reviewer, then seek appropriate operational or legal advice instead of automatically accepting or deleting the retained information.
Sources: Right to Erasure Requests for GDPR with WooCommerce.
- Run erasure only through the confirmed workflow.
- Read the completion output rather than assuming all information was removed.
- Escalate retained-data results for appropriate review.
Verify notifications and close the request record
WordPress documents a filter for the recipient of the personal-data export email notification. Ask a developer or site maintainer to inspect the intended export-notification recipient where routing is uncertain, then record the observed message outcome. A configurable recipient control is not evidence that an email was delivered, so investigate delivery through the site’s approved operational process.
Sources: Privacy Related Options, Hooks and Capabilities – Plugin Handbook | Developer.WordPress.org.
WordPress documents a filter for the recipient of the data-request confirmation notification. Close the request only when its action, component-coverage review, notification check and retained-data decision are recorded, or when an unresolved item has been formally assigned to an owner.
Sources: Privacy Related Options, Hooks and Capabilities – Plugin Handbook | Developer.WordPress.org.
WordPress documents a filter for the subject of the email sent when a personal-data export request is completed. Use the expected subject as one diagnostic detail alongside the intended recipient, observed outcome, next owner and closure decision.
Sources: Privacy Related Options, Hooks and Capabilities – Plugin Handbook | Developer.WordPress.org.
- Check intended routing for confirmation and export notifications.
- Record the message outcome separately from the privacy-tool action.
- Keep unresolved delivery or retention issues open with a named owner.
WordPress export-or-erasure response checklist
Use this branching checklist to control a WordPress personal-data request from initial scope review through export or erasure and closure. It is an operational aid, not a complete legal procedure.
| Workflow stage | Operator action | Check before moving on | Request-log entry |
|---|---|---|---|
| Scope requester-linked data | Identify relevant WordPress features, plugins and connected services. | Active settings and unknown coverage have been reviewed. | Components checked; coverage status; owner; open questions. |
| Register and confirm | Create the appropriate WordPress privacy request and send confirmation. | The existing request record shows confirmation is complete. | Requester identifier; request type; date received; confirmation status; next owner. |
| Export branch | Process the confirmed export through participating components. | Intended recipient and observed export outcome have been checked. | Components included; recipient; notification outcome; exceptions; owner. |
| Erasure branch | Process confirmed erasure and read the completion output. | Any retained-data result has a responsible reviewer. | Components included; retained result; reviewer; next action. |
| Close or hold | Review routing, outstanding exceptions and the closure decision. | No coverage, delivery or retention issue remains unassigned. | Status; closure or hold decision; date; owner; unresolved item. |
Record the actual component and observed outcome for the request. Uncertain plugin coverage, a retained-data result or uncertain email delivery puts the request on hold for investigation rather than proving completion.
Related guidance
Editorial position
Treat a valid personal-data request as a controlled WordPress workflow: identify requester-linked data, register and confirm the request, complete the export or erasure branch, review any retained-data result, and document notification and closure. WordPress tools can coordinate participating components, but they do not prove that every plugin or connected service is covered.
What follow-up questions matter most?
- Should I act on an emailed request immediately?
- Register the request in the appropriate WordPress privacy tool and use its confirmation process before exporting or erasing information. Preserve the request record and its current status while confirmation is outstanding.
- Does WordPress automatically cover every plugin?
- No. Review the active configuration and current documentation for every relevant plugin and connected service. A plugin may have privacy-friendly defaults while an enabled option changes the data it records or whether WordPress can export or erase it.
- What if erasure reports retained information?
- Treat a retained-data notice as an exception requiring review. Record the displayed outcome, responsible component, reviewer and next action before deciding whether the request can be closed.
- Can I verify notification routing in WordPress?
- WordPress documents controls for confirmation and export-notification recipients and for the completed-export email subject. A maintainer can inspect those controls when diagnosing routing, but their presence does not prove that a message was delivered.
What steps does this workflow follow?
Handle a WordPress personal-data export or erasure request
- Identify relevant data: List the WordPress features, plugins and connected services that may hold information linked to the requester. Review active settings rather than relying on default descriptions.
- Register and confirm: Create the request in the relevant WordPress privacy tool and send its confirmation request. Preserve the request record while confirmation is outstanding.
- Choose the correct branch: For an export, process the confirmed request through participating components. For erasure, confirm current provider prerequisites before running an irreversible action.
- Review the outcome: Check the export or erasure result, including any information a plugin reports as retained. Do not treat a partial or uncertain result as automatic closure.
- Verify and close: Check intended notification routing and record the action, observed outcome, outstanding exception, next owner and closure decision.