[wp-trac] [WordPress Trac] #43715: Popup notification for Privacy Policy page
WordPress Trac
noreply at wordpress.org
Tue Apr 17 19:47:39 UTC 2018
#43715: Popup notification for Privacy Policy page
-------------------------+------------------------------
Reporter: xkon | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: General | Version:
Severity: normal | Resolution:
Keywords: gdpr | Focuses: ui
-------------------------+------------------------------
Comment (by xkon):
Okay before we get lost in translation again I think it's a good time to
make a division as we did on `what is personal data` between what a site
has to offer in the front-end.
To my knowledge as some stuff already exist today a website 'should' have:
- Privacy Policy ( what we are helping with as a tool )
- Terms of Use ( of the website and I don't know if that could be the same
with the PP )
- Cookie information ( It might as well be bundled with the PP )
- Copyright notice ( that's admin/website dependent so it doesn't have to
do with us at all )
- Cookie & general 'consents'
---
As far as the `Privacy Policy` that we are helping to be authored via our
Tools, I suggest a simple link on the bundled themes footer as I said
above, that could/should include all the 'Cookie' information as well in
my opinion whether there's an extra 'Consent' popup or not. That
information should be accessible always to the user.
I've had some chats with the #themereview team and even the small change
we made on the comment form with the extra label is going to cause a bit
of trouble even though it's a really small footprint.
I can't imagine at the moment what a complete popup would do to themes. So
my 'original' point of view when I opened this ticket changed pretty fast
between chats :D
Having a built-in shortcode for example [privacy-policy-page] that
generates a link to the created PP page etc would be a good thing as well
and will probably help people even more to add it on various places if
they want ( widgets, custom areas, custom code etc ).
This link has nothing to do with the actual Consent process that has to
take place and needs a LOT of talk of how it should/could be implemented
as there is nothing final afaic for the time being.
I'll change my tone a bit but: The web works with cookies whether the GDPR
likes it or not. If the GDPR needs consents before dropping cookies (
entering a website ) well they will hit a really big wall as websites will
probably go into a lockdown as we normally see with Age verification
sites. A full blank page with just 1 small box stating the cookies to
first accept them and then enter the website. That will seriously kill
websites and I don't think that this will be eventually done as it's
counter-productive and really really not user-friendly. I don't yet see
any cookie consents when entering google / amazon or any other major
player out there either even though everybody updated their Terms/ Privacy
policies.
--
As I said in the chat at some point the company that I work is dealing
with the whole cookie/consent matter as a single 'consent / statement' in
the meaning of 'We need and gather this information and use these cookies.
If you don't accept this we will redirect you to google.' so if you hit no
you are just booted off the website, and that's with lawyers behind this
idea.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/43715#comment:13>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list