Privacy component

A weekly office hours is held for the Privacy component every Thursday @ 18:00 UTC.

The meeting is held in the #core-privacy room on WordPress.org Slack.

Roadmap: https://make.wordpress.org/core/roadmap/privacy/

Maintainers listed on this page are all active maintainers, and you are welcome to reach out to any of them regarding the component. In addition to the active maintainers, you can seek background knowledge and guidance from any of the emeriti maintainers:

Recent posts on the make/coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blogblog (versus network, site)

View all posts tagged privacy.

102 open tickets in the Privacy component

102 open tickets defect (bug) enhancement feature request
7.1 5 3 0
Awaiting Review 14 21 2
Future Release 12 41 4

102 open tickets. Last 7 days: +0 tickets

1 ticketticket Created for both bug reports and feature development on the bug tracker. that has no replies

View list on Trac

  • #59479  'Erase Personal Data' simply doesn't work

8 tickets slated for 7.1

View list in Trac

  • #44498  Make `_wp_personal_data_cleanup_requests()` run on cron
  • #53611  Font size inconsistency in the data erasure inline notice for 'additionalMessages' list items ui css
  • #56694  Uncached database read for logged in users when Privacy Policy Page is deleted administration performance privacy
  • #57639  Don't reveal and show adminadmin (and super admin) email address in "changed email address" template to low permission user roles – Privacy issue
  • #58969  Privacy setting > The ''Copied'' text also shows, When double-clicking on the 'Copy suggested policy text to clipboard' option,
  • #63467  function do_robots() should use admin_url() administration privacy
  • #64748  Privacy: get_the_privacy_policy_link() should strip HTMLHTML HyperText Markup Language. The semantic scripting language primarily used for outputting content in web browsers. tags and return plain text
  • #65025  Privacy Shield is declared invalidinvalid A resolution on the bug tracker (and generally common in software development, sometimes also notabug) that indicates the ticket is not a bug, is a support request, or is generally invalid. privacy

102 open tickets

Open enhancements: 65 View list on Trac
Open tasks: 0 View list on Trac
Open feature requests: 6 View list on Trac
Open defects: 31 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 triagetriage The act of evaluating and sorting bug reports, in order to decide priority, severity, and other factors. 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: