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

[WordPress Trac]

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

Comment (by paapst):

 The Consent API primarily wants to enable the communication between the
 different consent management plugins and all the plugins, themes etc that
 make use of a cookie, local storage etc.   Adding sub-consent types and a
 nested hierarchy will only add extra complexity to the API and to core .
 You only have to look at the complexity that is caused by IAB with their
 TCF framework to understand that this is not desirable.

 The only use case that is being mentioned here (the offering of a
 newsletter) will actually not make use of the Consent API.  That
 particular form of consent is usually not being handled by consent
 management systems but is being registered in the database when you use a
 newsletter plugin or a contact form, where consent for receiving the
 newsletter is being asked.
 All the other use cases I can think of, all make use of the 5 initial
 purposes.

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