RT Cunningham


The EU General Data Protection Regulation (GDPR) and My Website

GDPR The EU GDPR is causing both businesses and individuals to scramble all over the world at almost the last minute. The regulation goes into effect on May 25, 2018, and a lot of them are still not complying. I’m sure it’s due to a lot of confusion more than anything else.

I’m not going to try to explain the GDPR. I don’t even completely understand it.

My Website and GDPR Issues

I don’t store data at this website, other than the server logs. The big issue is personal data collection. The third-party services I’ve used, Google Analytics and Google AdSense, can collect personal data. I don’t have control over their data retention policies.

According to Google, since my website is pure AMP and I use amp-ads instead of desktop ads, I only need to do one thing. In the AdSense UI, I have to select “non-personalized ads” on the new “EU user consent” tab. The relevant text:

If your AMP ad tags do not use Real Time Config (RTC), you may simply enable non-personalized ad serving in the DoubleClick for Publishers or AdSense UIs, and no further changes to your AMP pages are needed.

I’ve already done it and I wish it was that easy with Google Analytics. I’ve replaced the Google Analytics code with the amp-pixel tracking code and updated my privacy policy.

GDPR Compliance

As far as I can tell, I’m in full compliance already. The only thing that could possibly trip me up is AdSense. I have to trust that Google is telling me the truth. The part that irritates me the most is that I rarely make money online from EU member countries.

Since I’m running a static website without any local forms, I shouldn’t have any issues in the future. Perhaps my decision to go completely static has helped me avoid what a lot of dynamic websites have had to go through and are still going through.

Share: Facebook | Twitter

By RT Cunningham
May 12, 2018
Web Development