[wp-trac] [WordPress Trac] #51092: Create a JSON schema for Privacy and Other Related Disclosures

[WordPress Trac]

#51092: Create a JSON schema for Privacy and Other Related Disclosures
----------------------------------------------+-----------------------
 Reporter:  carike                            |       Owner:  (none)
     Type:  feature request                   |      Status:  new
 Priority:  normal                            |   Milestone:  5.6
Component:  Privacy                           |     Version:  trunk
 Severity:  normal                            |  Resolution:
 Keywords:  needs-privacy-review 2nd-opinion  |     Focuses:  rest-api
----------------------------------------------+-----------------------

Comment (by carike):

 Since yesterday, I have thought a lot about your questions, @azaozz :)

 This ticket wasn't initially meant to outline a needs-analysis-of-sorts.
 We kind of took that for granted after previous tickets, I think. This is
 not ideal and it is something we could fix here, or elsewhere.

 So, let's look at why the Privacy Policy initiative was not as successful
 as it could have been.
 Please keep in mind that these are my opinions, influenced by others on
 the Privacy Team (and with particular acknowledgement of xkon).

 wpdirectory.net shows that wp_add_privacy_policy_content() is being used
 in 243 plugin extensions.
 There are currently 57,243 plugins in the repository.

 **So why was the uptake for this not higher?**

 **UI**

 - Well, currently the privacy policies are hidden. So the first issue is
 that there is no (website admin) user-side UI, either in Core or in the
 Repo;
 - Furthermore, the privacy policies are walls of text that are not really
 useful to site owners / admins / those managing the repositories.

 **Content**

 - The content is free-form, which would make it hard to compare if all the
 necessary info had been included;
 - However, because it is aimed at providing legalese, in practice, there
 is likely very little difference between the content for a SEO plugin and
 one that changes the appearance of the admin screen.

 **So, what do we need to do?**

 - Create a standardized template for plugin, theme authors and Core to
 use;
 - Have this template focus on practical concerns (mostly those that will
 be directly relevant to data mapping and inventory techniques), instead of
 on legalese;
 - Make the information visible to site owners and admins in order to
 assess their privacy risk profiles. This would include an admin UI
 (perhaps with tabs / expandable and collapsible sections that would make
 it easier for the average admin to read), as well as a repo tab (which
 would require a meta ticket after we have finalized the format).

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