On CP net The ClassicPress Commitment to Protecting Your Privacy it says:
This document is currently being updated.
And it also says
- Why does it say this page is being updated? I don’t think this page is being updated, since very long time, in fact, the last update was made 9 months ago
- What is
Once we know this I can make the necessary edits:
- remove that “being edited”
- either complete, or remove anything that somehow references to “coming soon”
- update the URLs, because impossibly we can and should have a PP page for 4 different things ( classicpress.net , petitions.classicpress.net , api.classicpress.net and docs.classicpress.net) on one website’s page.
For example, on CP net you might leave comments, on Docs however who knows one day you might leave an entire Document. We may track main website, but we should (and hopefully do not) not track on doc site.
On Petitions, you cannot do anything while on api site we actually do things related to the CMS, not to the website. Again on API site I do not see why GA should be running on it. It is … an API endpoint.
Additionally the API site is https://api-v1.classicpress.net, thus we would need to change it anyway.
I propose we have a PP for the single website if then that website needs a PP and not a catch all PP, I am not even sure that is actually “allowed” unless the single subdomains are specially explained in the document, which they are not
@timkaye I am not sure if you could quickly look over the PP page and let me know if you see anything else that is in the wrong place or words and if you agree that each domain needs its own PP or at least its own PP section (if then it needs one, which as long we have no trackers (or if we can can disable) and there is nothing to interact on the site, like on “petitions” site, I believe there is no need for a PP)
It seems common practice to gather all domains of an organisation in one domains’ page, so I am fine with that, I still think we should mention special website in a specific section (like, that GA is used only on main website and not on docs. or api.)