The primary concern of GDPR is related to tracking cookies. As long as the session cookie itself does not consist of personally identifiable information (PII) such as an email address, name, or IP address, it does not violate the new GDPR regulations. These cookies are not the focus of GDPR because logging into a website already implies that the user accepts that this information is being collected. For example, session cookies are used to track when a user is logged in to a website. The aim of GDPR isn’t to regulate each and every cookie that a website uses. “Of course this website uses cookies – every website uses cookies!” However, if you attempt to block all cookies in your browser, then you’ll soon find that you’re unable to stay logged into your favorite websites, your preferences aren’t being saved, and so on. The most visible manifestation of GDPR compliance on the web is the appearance of “cookie consent pop-ups.” If you’re like me, you’ve probably found these to be an unnecessary annoyance. Those questions can generally only be confidently answered by a site owner’s legal counsel (and yes, that absolutely means that this blog post is informative, rather than authoritative.) What GDPR Means Numerous articles have been published about GDPR and what it means for site owners and developers, but there isn’t a single definitive, authoritative source to know whether a website needs to comply with GDPR, and if it does, what specifically needs to be done to become compliant. The deadline for implementing compliance with the EU’s General Data Protection Regulation (GDPR) is this Friday, May 25th, 2018. Let’s make sure you’re covering your bases. If you are a site owner or a web developer, GDPR and this week’s compliance deadline has surely been on your mind.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |