Skip to content

New core sensor: GDPR privacy export & erasure request lifecycle #9

Description

@trueqap

WordPress core's personal data export/erase tooling (Tools → Export/Erase Personal Data) is not logged at all, although it is exactly the kind of action compliance audits ask about.

Proposal

Code Event Hook
4200 Privacy export request created `wp_user_request_created` (filter by type)
4201 Privacy erasure request created same, type `remove_personal_data`
4202 Personal data export file generated `wp_privacy_personal_data_export_file`
4203 Personal data erased / request completed `wp_user_request_action_confirmed` / completion hooks

Severity: HIGH. Metadata: request ID, requester email/user, admin who actioned it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions