Data Science Community and Legal Hackers join forces to untangle the GDPR mystery and to propose a workable and easy to use framework to allow each datascientist to stay inside the legal boundaries.
At first sight, it may not look so, but lawyers and data scientist have things in common. One of those things is the struggle with the implementation of the General Data Protection Regulation (“GDRP”). Each looks at it from a different perspective. Often they have the same goal: support the business in handling and using (personal) data “responsably”, like a “good head of the family”, in line with the state-of-the-art and the law.
This is one of the conclusion we made from the “data science and ethics” event in June.
So let’s try something. Let’s join forces and exchange best practices in a “questions and answers” session on GDPR implementation.
The idea
The idea is the enter the meeting with questions… and to come out of it with (some) answers.
As for the questions, please, do one on of the following:
- raise them in the comment section
- if you want, prepare a short presentation to give some context or an overview
- keep a little notebook for them and bring it to the meetup
- …
The questions can be legal, technical, organisational, practical,… We hope to gather all types of skills in the room to find the answers. Note that this also means that you don’t per se have to (already) be involved in the implementation at your company at present. The questions of people a bit further from a practical implementation may shed a fresh light on things.
As for the answers. They could be:
- a clear view on the theory,
- potential tooling,
- templates or (anonymised) examples,
- …
The approach
ASSEMBLY – Depending on the size of the group of attendees and the interests, we could go over all the questions in a single group or break up in sub-groups. In the latter case, we would assemble at the beginning (for an introduction) and at the end of the session (for a short report on each sub-group).
CONFIDENTIALITY – For people to open up in the meeting, we emphasize the commitment to confidentiality of all the attendees. Everything shared in the context of the event (prior to it, during and afterwards) should be kept confidential. So be careful when tweeting, taking photographs, making (video) recordings,… The practical information received can at best only be used anonymously (without reference to the source) and obfuscated (commingled amongst other sources). If you are not sure, explicitly ask the source if and how to use the info or material.
INFORMALITY – The approach is rather informal. This also means that any answers etc. are not advice and just a best effort nudge in a (good) direction. We don’t want anybody to worry about being called on for being open or offering an opinion during the meeting.
The joint forces
This organisation is a joint effort of (at least) two communities in Brussels:
- the Belgian data scientists:
- the Brussels legal hackers:
What if it works?
If this seems to work out fine, we are considering organising this once every month or every two weeks.
Like this:
Like Loading...
We are now 4 weeks away from the Annual Conference of the #DataScience Community – JUNE 27 – Université libre de Bruxelles
