Privacy component

A weekly meeting for the Privacy component is held every Wednesday @ 15:00 UTC.

A bug scrub for the component is held every Monday at 15:00 UTC.

 

98 open tickets in the Privacy component

98 open tickets defect (bug) enhancement feature request
4.9.8 14 15 0
Awaiting Review 12 31 2
Future Release 2 15 1
5.0 0 6 0

98 open tickets. Last 7 days: -5 tickets

9 tickets that have no replies

View list on Trac

  • #44161  Expired session tokens need to be removed from database because GDPR
  • #44378  Add privacy prompt(s) to the embeds whitelist documentation in the core handbook
  • #44414  Granular erasure, alteration or anonymization of data
  • #44464  Guide to write privacy policy: inexact point? docs administration privacy
  • #44500  Mark data requests failed when an expired link is clicked
  • #44538  WordPress does not offer a way to show WHAT changed when it nags me about a change to the suggested privacy policy text. administration
  • #44539  Notify the admin when no personal data is found for a user administration
  • #44550  The confirmaction page should also be in the user language administration
  • #44588  Denote the Copy action is complete by updating the Copy button to state 'Copied' privacy

6 tickets slated for 5.0

View list in Trac

  • #43437  Add way for registered users to request deletion or anonymization of their private data
  • #43738  Make the personal data Export/Delete functionality available in network-wide for super admins multisite
  • #43854  Add cards to the Tools page for personal data tools administration
  • #43856  Include submitter IP details in password reset emails?
  • #43895  Organize privacy functions into logical files and classes
  • #44145  Rework Privacy settings page to use the Settings API administration

98 open tickets

Open bugs: 28. View list on Trac

Help maintain this component

Component maintainers:

Many contributors help maintain one or more components. These maintainers are vital to keeping WordPress development running as smoothly as possible. They triage new tickets, look after existing ones, spearhead or mentor tasks, pitch new ideas, curate roadmaps, and provide feedback to other contributors. Longtime maintainers with a deep understanding of particular areas of core are always seeking to mentor others to impart their knowledge.

Want to help? Start following this component! Adjust your notifications here. Feel free to dig into any ticket.

Contributors following this component: