Skip to content

How the EU’s General Data Protection Regulation is Working After the First Year

After years of talk about individual data privacy, and years of enacting regional laws, the European Union’s flagship individual privacy law, the General Data Protection Regulation went into effect a year ago in May. Suddenly, if your organization does business inside EU member states, you will be under stringent regulation concerning individual data privacy.

Today, we will look at the GDPR and what has changed in the year it has been law.

The General Data Protection Regulation

Prior to the ratification of the GDPR, individual data privacy was the responsibility of the individual. Outside of the EU, it largely still is. However, when the GDPR went into effect it opened people’s eyes to just how many of the corporations they come into contact with were misusing their personal data.

The GDPR, which grew from individual privacy laws enacted by individual EU states, provides individuals with recourse if they do not approve of the way their data is being used by corporations. Information such as names, physical addresses, phone numbers, email addresses, and medical and financial information was being shared by technology companies.

Somewhere in the lengthy terms of service agreement, companies would have language that allowed them to package individual data and effectively use it as an alternative revenue stream. Consumers in the know don’t see this as fair.

This level of data privacy has been roundly rejected in the United States up until recently. Those who do want to see a GDPR-like law on the books in the U.S. may not want to hold their breath. Before the GDPR was in the news, not many organizations were thinking about how data breaches could negatively affect anyone but themselves. This has led to a wholesale change in the way businesses view data management, the training of their staff, and security investments as a whole.

After One Year

In the first eight months, over 59,000 personal data breaches have been reported to GDPR regulators. This may be less than you may have liked to see. However, it is twice as many as there were in 2017; and, of course, 59,000+ more than anyone wants.

The fines levied by GDPR regulators are hefty (up to €20 million, or up to 4 percent of total revenue from the previous year, whichever is larger). Thus, you are seeing an increase in an aligned and strategic approach to keeping data secure. Additionally, reporting any data breaches that do happen quickly. If you would like to see how the GDPR has fared in its first eight months, download the DLA Piper GDPR data breach survey, here.

The results of the GDPR don’t speak to its effectiveness thus far. However, in future reports, it will become evident that the law is working to keep individual data secure. Or, at the very least, keeping companies honest. Under the GDPR, companies that sustain data breaches have 72 hours to notify the people whose information has been exposed. This strict deadline eliminates the possibility that companies can manipulate public perception about how they are faring with data security. As you’ve seen numerous times over the past two decades.

Unfortunately, the huge teeth that the GDPR was built with haven’t been used to bite non-compliant companies thus far. Fines that add up to €55,955,871 have been levied against the companies responsible for the 59,000 and change-reported data breaches. This is an admittedly modest amount. Especially when you consider that around 90 percent of that sum was the fine levied against a single company. U.S.-based tech giant Google.

A French GDPR regulator stated that they consider the small amount as a result of it being a transition year. Rather than some type of long-term ineffectiveness of the law. It remains to be seen just how effective the law can be. It depends if regulators actively enforce it in a manner that affects the business operations of those at fault.

The Wider View of the General Data Protection Regulation

Over the past year since GDPR went into effect, a lot has happened in the U.S. Especially on the individual data privacy front. Not only has the GDPR lit fire under the seats of lawmakers. It also has major tech firm CEOs, such as Apple’s Tim Cook, calling individual data privacy a “fundamental human right”.

While American tech company leaders largely oppose the GDPR (as demonstrated by the €50 million fine against Google), Mr. Cook’s support represents a step in the right direction. One place where data privacy was a priority is in the state of California. Not long after the GDPR went into effect, the Golden State passed its own sweeping (and rather hastily designed) data privacy law. The California Consumer Privacy Act. We designed the CCP to protect California residents from corporate overreach. Colorado, Massachusetts, and Ohio lawmakers followed suit with their own privacy laws shortly after California’s CPA was ratified.

This is good news for individual data privacy in the U.S. It’s a far cry from only a few short years ago when some of the most reputable companies in the world could regularly lose a person’s sensitive data with no pushback. These situations resulted in some pretty damning situations for online consumers. Federal lawmakers have balked at making waves of their own in regard to data privacy. However, if history is any indication, when states begin passing laws that are outside the norm, the U.S. Congress typically acts to fill the breach.

If you would like more information about the GDPR, subscribe to our blog. Or call one of our knowledgeable IT professionals at (877) 771-2384.

wheel house it logo

Let's Start a Conversation

Fill out the form below and a member of our team will contact you within 10 minutes. (Mon-Fri 8am-6pm EST)

"*" indicates required fields

Name*
This field is for validation purposes and should be left unchanged.

Let's Start a Conversation

Rory from wheel house IT

Call (954) 474-2204, option 2 to speak with a representative.

Send us an email at sales@wheelhouseit.com

Or contact us by form below:

"*" indicates required fields

Name*
This field is for validation purposes and should be left unchanged.