Let’s look at the steps you need to consider to get your Google Analytics account and website ready for GDPR compliance. We’ll also talk about how to decide if you need a cookie consent popup. And download our Google Analytics GDPR compliance Resources [GDPR segments and cookie consent decision map].
For the past several years, we’ve moved toward a more secure web by strongly advocating that sites adopt HTTPS encryption. And within the last year, we’ve also helped users understand that HTTP sites are not secure by gradually marking a larger subset of HTTP pages as “not secure”. Beginning in July 2018 with the release of Chrome 68, Chrome will mark all HTTP sites as “not secure”.
Soon every mistake you’ve ever made online will not only be available to your internet service provider (ISP) — it will be available to any corporation or foreign government who wants to see those mistakes. Thanks to last week’s US Senate decision and yesterday’s House decision, ISPs can sell your entire web browsing history to literally anyone without your permission. The only rules that prevented this are all being repealed, and won’t be reinstated any time soon (it would take an act of Congress).
Let’s get prepared.First, a couple definitions. When I use the term “attacker” I mean anyone trying to access your data whom you haven’t given express permission to — whether it’s a hacker, a corporation, or even a government.And when I use the terms “private” or “secure”, I mean reasonably so. The reality is that — as long as humans are involved — no system will ever be 100% private or 100% secure.As long as your phone, computers, and accounts are sufficiently protected, their contents will remain an “e