[wp-trac] [WordPress Trac] #43602: Add to the privacy tools UX a means to erase personal data by username or email address

[WordPress Trac]

#43602: Add to the privacy tools UX a means to erase personal data by username or
email address
-------------------------------------------------+-------------------------
 Reporter:  allendav                             |       Owner:  allendav
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  4.9.6
Component:  General                              |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  gdpr needs-testing needs-patch has-  |     Focuses:
  screenshots                                    |
-------------------------------------------------+-------------------------

Comment (by allendav):

 Replying to [comment:51 mnelson4]:


 > This doesn't actually facilitate plugins adding controls that allow the
 admin to control what data gets erased, right? (If it does, I didn't see
 it mentioned in
 https://core.trac.wordpress.org/attachment/ticket/43602/ERASURE.2.md#L8).
 It just allows plugins' to hook in their own data erasers. If plugins want
 to ask admins what data to erase, it's up to plugins to present those
 options to the user. Is there a recommended way for plugins to interrupt
 the normal data erasure AJAX request to ask users about their preferences?

 That is correct - this code doesn't facilitate any plugin controls.  The
 intention for now is that plugins may choose to expose erasure controls in
 their own settings user interfaces where it makes the most contextual
 sense. Plugins don't need to interrupt the erasure AJAX request to get
 those preferences - they should be set well in advance of any erasures.
 All a plugin needs to do, when an erasure happens, is respond to the
 erasure page calls for their eraser(s) and use the settings (if any) that
 they have to decide how much / how little should be erased for a given
 item.

 A good example is a WooCommerce order. WooCommerce's settings could say
 that personal data should be retained for orders < XXX days old. The
 WooCommerce order eraser could look at that setting against each order and
 decide whether or not to remove it. If it decides not to remove it, it can
 emit a message in the AJAX to say as much to the admin (i.e. Order 1234
 was not erased because it is less than XXX days old.)

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43602#comment:56>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform