MediaLAB Amsterdam is now the Digital Society School! You are viewing an archive of MediaLAB projects. Content on this website may be outdated, and is without guarantee.

AIM

Just another MediaLAB Amsterdam Sites site

Team

Commissioner:

Description

Help! the avg/gdpr is coming!

Here at mediaLAB/DSS, it’s our teams aim to create new digital interactive esport concepts that stay at the edge of innovation through a data-driven business model. This to the benefit of the users and the stakeholders who make the service possible. But how will the GDPR affect data-driven business models and does it apply to student research project? Spoiler: it applies to everyone. 

Casper attended a workshop hosted by Media Perspectives to gain a better understanding of how we may use data under the new European General Data Protection Regulation (GDPR) better known as ” the new (super) privacy law” that will go in to effect on the 25th of may.

media perspectives - gdpr workshop

What is the GDPR?

laymen’s terms: It protects the data of EU citizens/residents and keeps any individual or company from harvesting data without sufficient legal ground. Power to the people.

Not laymen’s terms: The General Data Protection Regulation is an EU law on the protection of data and privacy for all individuals that reside within the European Union. It addresses what (personal) data is, when you may ask for it, if you may process it, how you must process it, if you may store it, how you must store, how your company must act on it, how you as an individual must act on it and that citizens/residents of the EU always stay in control. 

Why should I care?

It either protects you from any company or individual knowing everything about you through a world-spanning harvesting network and building a comprehensive profile on your every working.

Or

It keeps you as a person/student/freelancer/company from randomly harvesting all the data you can just use for your own gain. With fines up to 20 million euro or 4% of your annual profit. As specified in article 83.

The workshop

Initially, the GDPR law was incomprehensible to us and many others even in its most basic practical sense. Questions we had were: What do I need to do? What information, provided by a wide range of institutions and lawmakers can I hold on too? What happens if my company doesn’t comply with the GDPR by the time it put in to force?  Sheevani Bharatsingh of The law factor provided a presentation about the new GDPR and a workshop to answer all our questions. Sheevani Bharatsingh is specialised in corporate law, general contract law and has studied the GDPR extensively.

At the start of the workshop, we held a quiz about our knowledge of the GDPR to get some feeling of what we knew. After this Sheevani gave a general introduction to the main lines of the GPDR followed by a more in-depth crash course of what you need to look out for, what action you need to take and in what order.

After the general introduction, we went to work and made a basic structured analysis of the data and data flows within our company. We completed the session by giving a presentation of our findings, what should be done within our company and how to comply with the GDPR.

But what should u yourself do? To analyse your company and make the first steps to become GDPR ready I recommend the following action plan.

What you need to do for the GDPR:

  1. Map the information flows within your company and what flows out of the company.
    1. What kind of data do you handle?
    2. To what goal is this information processed?
    3. What is your legal ground for collecting and processing this data?
    4. With whom do you share the data and why?
  2. What role does your company have regarding the processing of the procured data?
  3. Structure and document the way you process data and log every time you process data and to what end.
  4. Make an analysis of the risk of processing and storing the data you collect.
    1. Create a systematic description of your intended way of processing data and to what end
    2. Assess the necessity and interests of the data being processed
    3. Assess the vulnerabilities of the way you process data, your hardware and software
    4. Assess the privacy risks
    5. What precautions are you taking?
  5. Create a protocol for data leaks
    1. You need to contact the authorities (AP)
    2. You need to contact the people implicated by the data leak, those who the data regards.
    3. Notify them within 72 hours after knowledge of the leak
    4. Register the data leak in a log
  6. Create a (new) privacy statement containing:
    1. The contact information of your company
    2. The contact information of the authorities
    3. The goal and to what and you process data
      1. What data you process
    4. With whom is the data shared and to what end
    5. Storage period expiration
    6. Rights of those involved
    7. Justified interest
    8. Consent of user
  7. Appoint a dedicated employee for data and privacy protection
  8. Asses to what authorities you report in the case you’re an international business

Credit to Sheevani Bharatsingh and The law factor for the action plan

What happens if I don’t comply with the GDPR by the 25th of may?

As long as you show the authorities that you are working on complying within the first year you will not be sought out and fined actively. Someone can, however, sue you if their personal data gets leaked, misused etc. So make the GDPR your priority because it’s both in the best interest of you and your clients.

 

 

Post a Comment

Your email is never shared. Required fields are marked *

*
*
To use reCAPTCHA you must get an API key from https://www.google.com/recaptcha/admin/create