[wp-trac] [WordPress Trac] #51188: Create a structure for consent-related user meta value

WordPress Trac noreply at wordpress.org
Thu Sep 3 17:19:30 UTC 2020


#51188: Create a structure for consent-related user meta value
----------------------------------+---------------------
 Reporter:  carike                |       Owner:  (none)
     Type:  feature request       |      Status:  new
 Priority:  normal                |   Milestone:  5.6
Component:  Privacy               |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  needs-privacy-review  |     Focuses:
----------------------------------+---------------------

Comment (by carike):

 Replying to [comment:8 azaozz]:
 > Thinking there is still some misunderstanding here, still not cleared
 out from the initial discussions about "user consent" two years ago:
 >
 > 1. Who are the users that need to give consent?
 > 2. Who are the admins (or other users?) who have to ask for consent?
 >
 > Could you please define the above two groups of people (in WordPress
 terms).

 Just for clarification:
 The Disclosures Tab deals with site-level privacy (by helping site owners
 / admins understand their privacy risk profile).
 The Consent API deals with individual website visitor consent.

 Users who need to give consent can be registered users who are logged in,
 registered users who are not logged in, or website visitors who are not
 registered.
 All three of these groups need to be able to manage their consent
 preferences - but will do so in different ways.
 (The Consent API could conceivably serve the needs of the repos as well,
 in which case the site admins would be the ones denying consent, but that
 would be a secondary, complementary purpose.)

 Those who need to ask for consent are effectively the plugin developers,
 on behalf of the site owners / admins, when their code performs a function
 which collects and / or stores user information / communicates with the
 user / shares the user's info.

 > Also seems a bit weird to have a trac component "Privacy" and a ticket
 focus of "privacy"? One too many? :)

 I'm okay with removing the focus :) Just had it there so it would be easy
 to find when filtering.

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


More information about the wp-trac mailing list