<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: yolaris</title>
    <description>The latest articles on DEV Community by yolaris (@yolaris).</description>
    <link>https://dev.to/yolaris</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F227154%2F6519e387-4c22-4785-b4d3-fd7b32850a91.jpg</url>
      <title>DEV Community: yolaris</title>
      <link>https://dev.to/yolaris</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/yolaris"/>
    <language>en</language>
    <item>
      <title>How to quickly check cookies for compliance with GDPR 🍪</title>
      <dc:creator>yolaris</dc:creator>
      <pubDate>Tue, 10 Sep 2019 16:21:27 +0000</pubDate>
      <link>https://dev.to/yolaris/how-to-quickly-check-cookies-for-compliance-with-gdpr-4jia</link>
      <guid>https://dev.to/yolaris/how-to-quickly-check-cookies-for-compliance-with-gdpr-4jia</guid>
      <description>&lt;p&gt;After setting up my small blog I already had a base solution to make cookies GDPR compliant, but it was a quite expensive for me.&lt;br&gt;
I was not that happy, so I decided to explore GDPR requirements.&lt;/p&gt;

&lt;p&gt;In general, if your website is visited by EU consumers, you must comply with the GDPR even when you don't collect any personal data.&lt;br&gt;
Since site visitors can be tracked by third parties through cookies, you should always keep an eye on the cookies that are set when your site loads.&lt;/p&gt;

&lt;h2&gt;
  
  
  GDPR compliant cookies 🥮
&lt;/h2&gt;

&lt;p&gt;You comply with the GDPR if you set cookies after obtaining prior consent. The consent banner should block cookies until the user clicks the allow button.&lt;/p&gt;

&lt;p&gt;You also comply with the GDPR if you do not set any cookies at all or set strictly necessary cookies without prior consent obtaining.&lt;br&gt;
The European Commission &lt;a href="https://ec.europa.eu/ipg/basics/legal/cookies/index_en.htm"&gt;gives&lt;/a&gt; examples of such strictly necessary cookies:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;user input cookies, for the duration of a session&lt;/li&gt;
&lt;li&gt;authentication cookies, for the duration of a session&lt;/li&gt;
&lt;li&gt;user centric security cookies, used to detect authentication abuses and linked to the functionality explicitly requested by the user, for a limited persistent duration&lt;/li&gt;
&lt;li&gt;multimedia content player session cookies, for the duration of a session&lt;/li&gt;
&lt;li&gt;load balancing session cookies, for the duration of session&lt;/li&gt;
&lt;li&gt;user interface customisation cookies, for a browser session or a few hours&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What about Google Analytics
&lt;/h2&gt;

&lt;p&gt;Any statistical, advertising or similar cookies aren't strictly necessary and cannot be set without prior consent obtaining.&lt;br&gt;
If you use Google Analytics, Google Adsense or DoubleClick you should to get user's consent. By the way, Google &lt;a href="https://www.google.com/about/company/user-consent-policy/"&gt;warns&lt;/a&gt; about this.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to quickly check your cookies
&lt;/h2&gt;

&lt;p&gt;To check website cookies for GDPR compliance you can use &lt;a href="https://2gdpr.com"&gt;2GDPR&lt;/a&gt;&lt;br&gt;
It takes about a minute to scan.&lt;br&gt;
If violations are found, it will take longer to analyze the results.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>beginners</category>
      <category>tutorial</category>
      <category>gdpr</category>
    </item>
  </channel>
</rss>
