If you are a smart phone user, you may have wondered why so many new privacy policies have recently rolled out. The reason? The General Data Protection Regulation (“GDPR”) became effective May 25, 2018, and applies to all organizations that handle European Union citizens’ data. Businesses throughout the world, including in the US, are figuring out how to best navigate through what some have called one of the most important corporate compliance events in years, with several controversial provisions. GDPR will substantially increase statutory obligations regarding the processing of personal data placed on data controllers and data processors both inside and outside the European Union. A controller is the entity that determines the purposes, conditions and means of the processing of personal data, while the processor is an entity which processes personal data on behalf of the controller.
Most startling of the new provisions are the severe maximum fines for violations; up to 20M Euro (currently about US$23.3M), or four percent of the total worldwide revenue, whichever is greater. Notably, the regulation applies to organizations based outside the EU (i.e., the US) if they collect or process data of individuals inside the EU. GDPR has its own website designed to answer many questions, www.eugdpr.org. The following is a very general description of some of the GDPR highlights. The regulations are vast in scope, and the need for compliance is critical.
As a general proposition, the GDPR aims to return control of personal data to citizens and residents and to simplify regulations, replacing the 23 year old Data Protection Directive.
Personal data must be processed in a manner that ensures appropriate security of personal data, including protection against unauthorized or unlawful processing, protection against accidental loss, destruction or damages, and use of appropriate technical and organizational methods. A data controller is responsible for and must be able to demonstrate compliance.
What do data controllers and data processors have to do? In short, they have to implement appropriate technical and organizational measures, depending on a variety of factors. This includes, as examples, pseudonymization and encryption of personal data, the ability to ensure confidentiality, integrity, availability and resilience of the processing systems, the ability to restore the availability and access to personal data in a timely manner in the event there is a physical or technical incident, and a process for regular testing. Controllers and processors must also maintain a record of the technical and organizational security measures and must comply with a Code of Conduct. Data controllers must conduct appropriate due diligence when selecting data processors and sub processors and enter into written contracts with processors regarding the scope of data uses and protection of personal data.
In the event of a personal data breach, controllers must document the facts, its effects, any remedial action taken, and must enable the Supervisory Authority to verify compliance. Controllers must also notify the Supervisory Authority within 72 hours of identifying an incident, and if unable to do so must provide a reason. A key exception is if the Controller can demonstrate that the breach is unlikely to result in a risk to the rights and freedoms of individuals. Notification to the affected individuals is required only if the breach is likely to result in a high-risk to the rights and freedom of the individuals, with certain stated exceptions, and with no undue delay.
Finally, GDPR prohibits data from being held in a format that permits personal identification longer than necessary.
In short, these laws are complex and many companies are struggling with ensuring compliance. If you need more detailed analysis or compliance advice, please contact us for guidance.
Other AALRR Blogs
- California Supreme Court Rings In The New Year With A Blast To Employers’ Past
- Privacy Law Update: New California Privacy Rights Act Further Expands California’s Privacy Law Amid the Evolving Privacy Landscape
- Employment Arbitration Agreements & PAGA — Choose Your Words Carefully
- Ninth Circuit’s Ruling In Frlekin v. Apple, Inc. Is A Cautionary Tale For Employers
- Further Developments Under COVID-19 and Its Continued Impact On Commercial Lease Payment Obligations
- A Postjudgment, Independent Action To Enforce Alter Ego Liability On A Contract Is Considered An Action On The Contract
- Part 5: Data Privacy in California: Responding to Consumer Requests and Enforcement by the Attorney General Begins
- The Appellate Court Takes a Bite Out of Meal and Rest Break Claims
- Los Angeles County Obtains Approval to Move Further into Stage 2; Restaurants May Resume In-Person Dining and Hair Salons and Barbershops May Reopen
- Better Luck Next Time—Supreme Court Unanimously Rejects Defense Preclusion in Lucky Brand Trademark Row
- Christopher S. Andre
- Cindy Strom Arellano
- Dan J. Bulfer
- Eduardo A. Carvajal
- Danielle C. Cepeda
- Michele L. Collender
- Scott K. Dauscher
- Evan J. Gautier
- Carol A. Gefis
- Amber S. Healy
- Edward C. Ho
- John E. James
- Jonathan Judge
- David Kang
- Joseph K. Lee
- Lana Milojevic, CIPP/US
- Michael J. Morphew
- Shawn M. Ogle
- Jon M. Setoguchi
- Brian M. Wheeler
- Lisa C. Zaradich
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- June 2019
- May 2019
- April 2019
- March 2019