<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[EUDPR - Medium]]></title>
        <description><![CDATA[EUDPR Blog - Medium]]></description>
        <link>https://medium.com/eudpr?source=rss----50ab20c40289---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>EUDPR - Medium</title>
            <link>https://medium.com/eudpr?source=rss----50ab20c40289---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:12:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/eudpr" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[GDPR — “Oops” is not an option]]></title>
            <link>https://medium.com/eudpr/gdpr-oops-is-not-an-option-45905c1134cc?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/45905c1134cc</guid>
            <category><![CDATA[record]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[manipulation]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Mon, 13 May 2019 14:11:21 GMT</pubDate>
            <atom:updated>2019-05-13T14:11:21.697Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*62mzh-BGv_tJr5-DN_29xw.jpeg" /></figure><h3>GDPR — “Oops” is not an option</h3><p>How many times have we read or heard that data is the new gold? Startups are worth billions simply because of the information they hold on their users. Social media platforms are not only a direct access to hundreds of thousands, or even billions, of users, they can also be an access to what makes each user tick.</p><p>The magical combination of statistics, profiling, big data and artificial intelligence is providing the digital wizards with an ever increasing power to play with the people. The often sought-after “competition” among companies, is replacing the lowering of prices by a sort of “vulnerability tracking” meaning that companies are understanding ever more the best moment to offer their products to the end user and in what way.</p><p>Knowing is controlling.</p><p>Hence the GDPR.</p><p>The big idea is that it is now possible to collect data from all over the web so each piece of data needs to be protected. Any mad “digital voodouist” is now able to build your voodoo doll from digital bits and pieces he can gather from around the web. And believe it or not, without knowing it, many will dance, think or buy to their tune… So even if you have a site discussing the most boring topic you need to protect the personal information you store on your servers.</p><p>The GDPR requires that every company, association or internet site, accessing European information, know clearly what personal data it is holding, who can have access to it and for what purpose. For doing so a Record of Processing Activities (or RoPA) needs to be set up and regularly updated for keeping track of all the personal data and how they are being processed.</p><p>The GDPR is specific about what should be included in this record (<a href="https://eudpr.com/gdpr#article30">Article 30</a>):</p><ol><li>the name and contact details of the controller and, where applicable, the joint controller, the controller’s representative and the data protection officer;</li><li>the purposes of the processing;</li><li>a description of the categories of data subjects and of the categories of personal data;</li><li>the categories of recipients to whom the personal data have been or will be disclosed including recipients in third countries or international organisations;</li><li>where applicable, transfers of personal data to a third country or an international organisation, including the identification of that third country or international organisation and, in the case of transfers referred to in the second subparagraph of <a href="https://eudpr.com/gdpr#article49">Article 49</a>(1), the documentation of suitable safeguards;</li><li>where possible, the envisaged time limits for erasure of the different categories of data;</li><li>where possible, a general description of the technical and organisational security measures referred to in <a href="https://eudpr.com/gdpr#article32">Article 32</a>(1).</li></ol><p>Setting up a register needs not take a lot of time. In most instances a spreadsheet is sufficient. The trick is to organise it by defining the list of possible values for the categories of data (such as identifying data, personal life data, professional life data, financial data, internet related data…) and sensitive data (racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person’s sex life or sexual orientation), the categories of data subjects (clients, prospects, staff, subcontractor staff…) and categories of recipients (the company, subcontractors, lawyers…).</p><p>Including a GDPR review as part of your project is not only a good idea but is required by the regulation under the term “Privacy by design”. The point being that privacy should now systematically be a key part of any new project, upgrade or development. Companies are now asked to study all the possible impacts on privacy before the official project kick-off in order to deal with them or abandon the project all together. Should a Data Protection Authority come knocking on your company’s door, you will need to provide the Record and the proof that you have a Privacy by design procedure in place which is followed when launching any new idea.</p><p>Even if your company does not (yet) have European users, keeping a Record of the personal data is probably a smart idea both for your company but also, obviously, for your end users. Many countries are considering following the European steps regarding the GDPR so, by starting a RoPA you’ll be a step ahead.</p><p>GDPR should not be seen as a pain to frown upon but as a real protection against the mad voodouists waiting to take control. So lets do this right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45905c1134cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/gdpr-oops-is-not-an-option-45905c1134cc">GDPR — “Oops” is not an option</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR- Controllers and Processors]]></title>
            <link>https://medium.com/eudpr/gdpr-controllers-and-processors-9a699c1c10cc?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/9a699c1c10cc</guid>
            <category><![CDATA[contracts]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 16:25:19 GMT</pubDate>
            <atom:updated>2019-04-29T16:25:19.117Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rx9a2eNa_uB6t_vcqrOs-g.jpeg" /></figure><p>One essential notion in the GDPR which needs to be clearly understood is the difference between a Controller and a Processor.</p><p>Lets, obviously start by the definitions. Article 4 of the GDPR states:</p><p><strong>‘controller</strong>’ means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of such processing are determined by Union or Member State law, the controller or the specific criteria for its nomination may be provided for by Union or Member State law;</p><p>and…</p><p><strong>‘processor</strong>’ means a natural or legal person, public authority, agency or other body which processes personal data on behalf of the controller;</p><p>So, in a nutshell, for most companies, a controller is the one offering an added value service to its clients by processing personal data. The processor, on the other hand, is a sub contractor for processing personal data on behalf of a controller. It is interesting to note that the french translation of processor is “sous-traitant” which literally means “sub-contractor”.</p><p>Keeping in mind the fact that personal data are owned by the individuals and not the companies, the question to ask is therefore:</p><p>“Are the personal data processed by my company owned by my users or clients?” If the answer is “yes” then your company is a processor.</p><p>For example if your company is selling shoes, the personal data is processed for sending the goods to your clients. Your company is therefore a controller. If you work with another company which manages a newsletter for your company, this other company will be processing the email addresses of your company’s clients for sending out the newsletter. This other company will therefore be a processor.</p><p>In some instances the added value is provided by both parties which are therefore partners or, as the GDPR would put it, joint controllers. A good example for this is the partnership between a bank and an insurer for providing a loan. Both the bank and the insurer are providing a specific added value service and process the personal data for their joint clients.</p><p>Having said all this it is now necessary to look at why it is important to distinguish controllers from processors.</p><p>Controllers are responsible for their users’ and clients’ personal data even if it is being processed by a processor. This means that the contract binding these two parties needs to clearly define what data are being transferred to the processor, for what purpose and for how long the data will be held by the sub-contractor. The contract will also state that the controller may audit the processor in regards to the security measures that will have been agreed upon. Should a user or client wish to exercise one of their GDPR rights, the contract needs to detail how it will be dealt with by each of the two parties.</p><p>Finally a contract between a controller and a processor needs to define the process which needs to be followed in the case of a data breach. The GDPR requires that the processor inform the controller as soon as possible whereas the controller will then have 72 hours to inform the end users.</p><p>Regarding joint controllers the responsibilities are simpler to deal with in the partnership contract because each party is sole responsible for the personal data it manages.</p><p>Should you still have questions about your company’s role in regards to the processing of personal data, the best is to check with your GDPR lawyer or, if you are outside of Europe, with your European Representative.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a699c1c10cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/gdpr-controllers-and-processors-9a699c1c10cc">GDPR- Controllers and Processors</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The tell tale data]]></title>
            <link>https://medium.com/eudpr/the-tell-tale-data-acdec63d1ddf?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/acdec63d1ddf</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[statistics]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[profiling]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 16:25:11 GMT</pubDate>
            <atom:updated>2019-05-02T04:02:51.761Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rVu5_G5zGM040x66Y9_a5w.jpeg" /></figure><p>Many people do not seem to really care about the data trail they leave behind them as they browse the World Wide Web but that may be because they forget the spider.</p><p>One may wonder why there is such a fuss regarding personal data. After all, by the end of the day we are, each one of us, but one among so many others. If these companies take our data, they also do so for thousands, or even hundreds of thousands, of other similar users. Our own data is therefore diluted in an enormous stew of personal information and it can’t really harm us, right?</p><p>Some of us may nevertheless shudder at the idea that some totalitarian power may, some day, take over our country and hone in on our personal data to justify some terrible action against us. After all, are we not all at odds, in the way we think, with at least one political party?</p><p>And what about these cyber pirates which can use our personal data to hack our computers and freeze them? And that is not to mention the cyber blackmail we sometimes hear about.</p><p>Both attitudes, laxiste or paranoiac, may be somewhat extreme in most cases but, according to me, the real danger lies in the power of statistics…</p><p>A few years back I was managing a portfolio of bank related projects among which was a vast e-mailing campaign for inviting the bank’s clients to switch to digital statements instead of paper. The mail was quite strait forward, there was a short text explaining the benefits for the clients and a button for accepting the switch.</p><p>Hundreds of thousands of mails were sent out over a few months and every day we would display the figures regarding how many people actually opened the mail (commercial mails have a transparent picture called a “tracking pixel” which, when loaded, informs the sender that the mail has been opened) and how many people clicked on the button.</p><p>Once a month my project manager would send me the daily statistics, for the month, providing the percentage of clients having actually clicked on the button compared to all those having opened the mail.</p><p>And every month I was baffled by the fact that day after day the percentage was identical with a standard deviation of 0.3%. This means that the percentage remained nearly constant.</p><p>I don’t remember the exact figures but the daily percentages throughout the operation would look something like:</p><p>28.6%, 28.7%, 28.5%, 28.5%, 28.7%…</p><p>It was as if, each day, the thousands of users having opened the mail called each other to agree on who was going to open the mail. This remained true during the whole operation. It was eerie.</p><p>What I realized back then was that it is quite easy to predict someone’s behavior if you have sufficient personal data. This means that each one of us can be led into buying, voting or even believing if the sites and the media hold relevant personal data. This may not be intuitive (it was surely not to me until I was faced with the statistics above) but large and small companies are well aware of the power of profiling. Artificial intelligence and the Big Data are providing ever more handles for targeting the end users, reaching directly into their pockets or swaying the votes.</p><p>So where does that leave us? Well it tells us that our personal data is really precious and that it should not be carelessly given out. GDPR is most definitely a necessary regulation and should be requested by the end users.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=acdec63d1ddf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/the-tell-tale-data-acdec63d1ddf">The tell tale data</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR — You don’t own me]]></title>
            <link>https://medium.com/eudpr/gdpr-you-dont-own-me-99f6e0b6cf84?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/99f6e0b6cf84</guid>
            <category><![CDATA[security]]></category>
            <category><![CDATA[freedom]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[gdpr]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Mon, 15 Apr 2019 18:33:17 GMT</pubDate>
            <atom:updated>2019-04-15T18:33:17.810Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_pQHrsqxUVx5xHi9qZHX1Q.jpeg" /></figure><h3>GDPR — You don’t own me</h3><p>Many years back, when I was “so much younger than today”, a very good friend of mine lent me a Klaus Nomi record. I didn’t know this artist and was immediately fascinated by his opera rock music and his incredible voice.</p><p>Among the titles there was one which comes back to me regularly when helping companies out with their GDPR, the title is “You don’t own me”. The lyrics go on to say “You don’t own me, I’m not just one of your little toys”.</p><p>This claim has always seemed to me as the best way to coin the GDPR’s mission. Companies need to understand the power of the personal data and how, if abused, it can turn out to be a handle for manipulating their clients and users. To be even more dramatic one could say “to own their digital souls”.</p><p>Imagine that a friend of yours trusted you with the keys to his home. Would you add a label to these keys with the name and address of your friend? Would you then simply leave the keys hanging around? If you did so and that the keys were stolen, would you not be somewhat responsible? Should your friend trust you with his keys again?</p><p>In fact user names and passwords can, in some instances, turn out to be even more valuable than someone’s keys. Even if your site does not contain any sensitive information you can be sure that many of your users are using the same username and password on your site as they are on other sites which may contain precious information. So if somebody gets a hold of your users’ usernames and passwords, they will have access to many user spaces on other sites. This is the reason why it is so important for all sites to be GDPR compliant even if the only personal data you hold are user names, passwords and email addresses.</p><p>Users should understand that a GDPR compliant site accepts to declare a data breach within 72 hours. This should give time, to most of the users, to change their passwords on other sites. Declaring a data breach will not entail a fine for the site (except if the security was absent such as the “Admin/Password” login) so everybody wins with GDPR compliance. On the other hand users should really stay away from GDPR non-compliant sites.</p><p>But how can one know whether a company plays the right game or not? Well it is quite simple in fact. Look up the word GDPR within the site and see what comes up. If nothing comes up you should move away. If the word does come up look at the user rights that they declare you have (access, modification, erasure, portability…) and how you can put them into action. If the website is outside of Europe check for their European representative as it is mandatory. If they do not mention one and do not provide the contact details the best is to avoid trusting your data to this site. Finally you can write to the site to ask them about their GDPR policy.</p><p>You may think to yourself that if you are not an EU user you are not really concerned with all this GDPR business. The truth is that you probably should be, because if a site is GDPR compliant it will probably be so for all of its users and is therefore safer than a site which has not thought these matters through.</p><p>The power of data is quite mind boggling if you look into it and regulations such as the GDPR should be more than welcome in our ever more digital world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99f6e0b6cf84" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/gdpr-you-dont-own-me-99f6e0b6cf84">GDPR — You don’t own me</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR — Getting your contracts right]]></title>
            <link>https://medium.com/eudpr/gdpr-getting-your-contracts-right-72e95ca6bc7b?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/72e95ca6bc7b</guid>
            <category><![CDATA[pda]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[contracts]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Mon, 08 Apr 2019 16:32:56 GMT</pubDate>
            <atom:updated>2019-04-08T16:32:56.167Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JxY0f_x-X6bY4G5PfUQSaA.jpeg" /></figure><h3>GDPR — Getting your contracts right</h3><p>If you are lucky enough to be the sub contractor (or “processor” as the GDPR would say) for a large group based in Europe you will probably have been asked to work on the “remediation” of your existing contracts. Otherwise, if you haven’t yet looked into this subject, this is what you need to know.</p><p>GDPR related remediation boils down to bringing two modifications to your existing contracts.</p><p>The first amendment regards the privacy related clauses which now need to follow the GDPR requirements. In a nutshell the contract will need to</p><ol><li>clearly define the relationship between the different parties. This means to state whether the contractors are “shared controllers” or controllers and processors. The controllers are those who provide added value to the end users or the clients. The processors are the controllers’ sub contractors in regards to processing the personal data. When two parties are in a partnership for providing added value then they are said to be “shared controllers” (for instance a bank and an insurance are shared controllers when providing a loan). This is important because the GDPR imposes different interactions, between the contractors, in regards to this relationship. For instance, it is a compulsory for the processors to accept to be audited by the controllers.</li><li>define the rules for informing the other parties regarding a potential data breach</li><li>sometimes modify the liabilities in the case of a GDPR fine befalling the controller</li></ol><p>The second modification which will need to be applied to an existing contract will be to state</p><ul><li>the personal data being exchanged</li><li>to what purpose</li><li>what users are concerned</li><li>who will have access to this data</li><li>what type of processing is allowed</li><li>where will the data be stored</li><li>how long the data will be stored and for what reason</li></ul><p>Having said that, many companies may not be very comfortable at the idea of modifying an existing contract and this can be for at least two reasons.</p><p>The first may be that it was complicated to reach the agreement and that, by lifting up the hood again, there may be other aspects which will come back into discussion. That may not be a good idea.</p><p>The second reason can simply be because you have more than one contract signed with one of your corporate clients and modifying each contract will obviously be a hassle.</p><p>Fortunately there are different ways you can handle the remediation the first being, obviously, to modify the existing contract.</p><p>The second is to “amend” the existing contract. This means that a new contract is signed in which you simply indicate which clauses need to be modified and by what text. Doing that allows you to only focus on the privacy related clauses without displaying the whole contract.</p><p>Finally the third way to move forward is to sign a Data Privacy Agreement (DPA) which is a contract which focuses only on the privacy aspects of your contract. This agreement states that any past or future contract will abide by these new clauses. The big advantage with this DPA is that the existing contract or contracts do not need to be modified.</p><p>DPAs can also come in handy if your company works mainly with purchase orders as this unique contract can suffice to cover the GDPR requirements.</p><p>When there are more than one contract and that the categories of personal data being processed can varie from one contract to the next, an additional contract will need be prepared and signed to state what data is being processed, by whom and to what purpose.</p><p>And that is about it. Just one last word regarding your new contracts. All that has been said above obviously needs to be taken into account so it is worth having a GDPR compliant model that you can use.</p><p>To wrap things up I’ll simply add that, as it has nearly been a year since the GDPR has been rolled out, there are best practices which can be tapped into. It is therefore worth talking to your lawyers or partners such as EUDPR for getting things right.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72e95ca6bc7b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/gdpr-getting-your-contracts-right-72e95ca6bc7b">GDPR — Getting your contracts right</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR — e-Survival]]></title>
            <link>https://medium.com/eudpr/gdpr-e-survival-179852ce9ee1?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/179852ce9ee1</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[personal-data]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Thu, 04 Apr 2019 14:07:06 GMT</pubDate>
            <atom:updated>2019-04-04T14:07:06.761Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTsum-byvEjhgKy6VxfEhQ.jpeg" /></figure><h3>GDPR — e-Survival</h3><p>The GDPR is all about protecting European Citizens. The root idea is that each user owns his personal data which he can trust to companies. In turn the companies can process this data and create value both for the user and, in some instances, for all the other users. The GDPR sets the rules for avoiding abuses and accidents. One could say that “digital wise” a user exists solely by his personal data. Abuse these data, alter them or destroy them and the user’s “digital” existence is in jeopardy. So in a way the GDPR could be seen as protecting the “e-Human Rights”.</p><p>But what are these personal data that the GDPR is trying to protect? Well, in fact, any data which can be linked to a specific individual is considered as being personal data. Obviously all the identifying data, such as the first and last name, the email address, an IP address, a phone number, an identity card, a photo or even a home address, are all personal data but any data which is linked to some identifying data is also considered as being personal data. It makes sense that a date of birth or the color of one’s eyes is personal but the notion within the GDPR goes way beyond that. Any information which can be linked to a given person is within the scope. As an example, if you find a photo of a sunset on the internet and that you can trace it back to its author, or even a simple IP address, the photo is considered as personal data.</p><p>One can collect personal data without really being aware of it. Lets imagine that Ernie is botanist and that he loves taking photos of trees and flowers around the neighborhood to post it on the internet. As he is in a village he provides the address where he took each photo. For instance Ernie discovered this incredible beach tree just outside 22, slumberland road. Without knowing it Ernie would be publishing personal data because a home address can, in some cases, be linked to a single person and the beach tree can therefore be considered as personal information. This is, of course, an extreme example for the purpose of emphasis and I strongly doubt that a Data Protection Authority would have anything to say against Ernie.</p><p>This may seem to be somewhat of an overkill but is it really? I remember working on an AI project for recognizing signatures. The idea was to identify a signature whilst the user was signing. What we had discovered was that, when somebody signs, there is the signature itself but also specific movements of the pen above the paper. These movements could not be easily copied and were therefore a way for certifying the signature. The point being that we are all a lot more than meets the eye. We are each defined by the direct information relating to us but also by a lot of indirect information such as, maybe, the trees and the flowers growing around the place we live.</p><p>E-profiling has taught us how easy it has become to predict and influence behavior. The more we have information provided to these systems and the more accurate and powerful they will become. Providing access to personal information can literally turn out to be exposing our freedom. It is for this reason that regulations such as GDPR are essential. Their aim is to help users benefit from a transparent use of their personal data. Each company needs to clearly communicate on what data they need, why, how long they will be storing it and to whom they will be transferring it to. In addition to this any data breach needs to be declared within 72 hours in order to be able to act as quickly as possible. Fines are huge for companies which don’t comply. Our freedom depends on this.</p><p>Wherever we live around the world we should insist that our governments defend and protect our rights. Privacy laws will be ever more important with AI which will be feeding on any data it can get to. Users should really stay away from companies which can not prove its compliance with privacy regulation such as the GDPR. Really.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=179852ce9ee1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/gdpr-e-survival-179852ce9ee1">GDPR — e-Survival</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR — What to expect from your EU Representative]]></title>
            <link>https://medium.com/eudpr/gdpr-what-to-expect-from-your-eu-representative-e4c97119b259?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/e4c97119b259</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[representative]]></category>
            <category><![CDATA[brand-ambassadors]]></category>
            <category><![CDATA[gdpr]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Mon, 25 Mar 2019 16:05:45 GMT</pubDate>
            <atom:updated>2019-03-25T16:05:45.847Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NhOOBQCInZ46iiSBuO8FIw.jpeg" /></figure><h3>GDPR — What to expect from your EU Representative</h3><p>As many know by now, any company outside of Europe, interacting with European citizens, is entitled to have an official representative in Europe. Well “entitled” is not really the right word as it is compulsory but as it is a real opportunity, rather than a constraint, “entitled” conveys the right idea.</p><p>Since May 25th 2018 the GDPR forbids any company to do business or to collect any information regarding European citizens unless it has offices in Europe or, at least, an EU Representative. Offices will often be out of reach for non EU companies so an EU Representative will be the right choice. The question is “Which EU representative do I need?”.</p><p>If you look around on the net there are many EU DPRs meaning EU Data Protection Representatives (such as eudpr.com of course). The prices are often quite low and the proposed services quite sufficient. It is nevertheless important to understand what you are getting for your subscription fee.</p><p>The basic service provided by your EU Representative is to be your “interface” with Data Protection Authorities (DPA) and with your European users in regards to their data privacy requests. It is important to note that your EU Representative will share your company’s responsibilities and will therefore, very probably, perform a due diligence on your company before accepting the mission. Being responsible for your company, GDPR wise, should also encourage your EU Representative to be your best ally in regards to any questions you may have in regards to your compliance. This is a great advantage for companies which don’t have time to look into this regulation.</p><p>Hence rather than taking the ostrich approach by burying a company’s head in the sand and hoping not to be seen, a company can lean on an EU Representative to reach GDPR compliance and even compliance in regards to other Data Privacy laws around the world. Besides being on the right side of the law it is, obviously, also reassuring for the end users.</p><p>When choosing an EU DPR you need to figure out where your EU users are. If most of your EU users or clients are in a specific country you need to choose a DPR within that country. It both makes sense and is compulsory. If, on the other hand, your EU users are spread out in many countries, simply because you have an internet site, then you need to choose an EU DPR in one of the most populated countries in Europe (Germany, France, Spain or Italy). As your company does not have a clear majority, on the long term, in a given country you therefore need to choose a country where mechanically you will have many users.</p><p>Some countries are considered to be more strict than others in regards to the GDPR. It would seem that this is linked to the fact that these countries are quite new to the Data Privacy laws and are therefore a little more abrupt than countries which have enforced these concepts for many years. France for instance set up Data Privacy laws in 1978 and has therefore, over the last forty years, learnt to be very practical and to fine only companies who refuse to comply after different warnings. It could be, therefore, interesting to choose your EU Representative in one of the more “mature” countries in regards to the Data Privacy Regulations.</p><p>Having said this it is important to note that for non EU companies the “One stop shop” does not apply. This means that, in the case of a data breach for instance, your representative will need to inform all the Data Protection Authorities of the countries where you have clients or users. So you may, nevertheless, be exposed to a strict DPA.</p><p>Another interesting aspect to look into, when choosing your EU Representative, is the address. After all, your representative is your official presence in Europe. You are entitled to highlight this address on your website. For your European users or clients an address in a prestigious part of a European capital is a reassuring sign. This is a great advantage you should not miss.</p><p>Finally the most important, by the end of the day, is to choose a representative which actually cares about your business. He will be the one who will need to defend your interests within Europe and answer your questions. A good EU Representative could really turn out to be a precious asset for your company. So choose carefully!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4c97119b259" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/gdpr-what-to-expect-from-your-eu-representative-e4c97119b259">GDPR — What to expect from your EU Representative</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[GDPR — Brexit won’t break Britain!]]></title>
            <link>https://medium.com/eudpr/gdpr-brexit-wont-break-britain-b15f8bf6a902?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/b15f8bf6a902</guid>
            <category><![CDATA[representative]]></category>
            <category><![CDATA[article-27]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[dpr]]></category>
            <category><![CDATA[brexit]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Tue, 19 Mar 2019 14:59:52 GMT</pubDate>
            <atom:updated>2019-03-19T14:59:52.314Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OClMpo2Ab7xpp4V7J50pLg.jpeg" /></figure><h3>GDPR — Brexit won’t break Britain!</h3><p>Yet another Brexit article but this may be good news or at least reassuring, GDPR wise, for companies established in the UK.</p><p>The question is: what does a UK company need to do, post Brexit, regarding the GDPR? Answer: Very little, but this “very little” is essential.</p><p>The first important point to keep in mind is that the UK government intends to maintain the GDPR principles within its own privacy law enforced by the Information Commissioner’s Office (ICO). The Brexit will therefore have no impact in that regards. Hence companies which do not interact with the rest of Europe will still need to comply.</p><p>What about all the other companies, those which do business or simply have sites browsed by European residents of the 27 other countries? Well, the Brexit won’t be too bumpy in fact, on the contrary it should turn out to be quite smooth as there are simply a couple of formalities to see to.</p><p>Just to be quite clear, any company which has not yet taken the compliance path towards GDPR still needs to do so and that can be tedious. The “simple formalities” concern the companies which were GDPR compliant up until the Brexit.</p><p>The first point regards companies which are subcontractors, partners or controllers (meaning you have subcontractors) for third party companies based in the rest of Europe. Britain, having no GDPR deal, is now considered as a “third country”. This impacts the transfer of data to and from Europe as there are, according to the GDPR, three sets of countries. The first set are the countries within the European Economic Area (EEA), the second group are the countries which have signed an agreement with Europe after imposing sufficient privacy laws within their borders. These countries are called “adequate”. Finally, all the other countries are considered “third countries”.</p><p>Doing business with “third countries” requires specific GDPR terms which need to be added in the contracts.</p><p>The good news is that the UK companies don’t have anything to do because this obligation applies to the European companies. You simply need to know that you will probably be asked to sign a new version of the contract or at least a Data Transfer Agreement (DTA). Given the fact that these clauses are simply requiring that the UK company complies with the GDPR obligations it should have no organizational impact.</p><p>The second subject which needs to be addressed regards the GDPR article 27: “Where Article 3(2) applies, the controller or the processor shall designate in writing a representative in the Union.”</p><p>This means that the UK company will now need have an official representative in one of the other European countries. There are many companies offering to take on this responsibility. Their role will be to represent the UK company within Europe which, by the way, means that the UK company maintains an official presence in Europe. Complying with article 27 is mandatory but needs not be very expensive and can be set up on line.</p><p>And that’s it. A couple of formalities and UK companies will be back to Business as Usual.</p><p>Any GDPR compliant company in the UK has therefore very little to do to remain so. For companies which haven’t yet made the move for becoming GDPR compliant, it is worth noting that some Representatives can also help with becoming compliant whilst providing all the relevant material and advice (<a href="http://www.eudpr.com/">EUDPR</a>, for instance, offer a free coaching service in this regards).</p><p>So UK companies have nothing to fear from the Brexit… regarding the GDPR.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b15f8bf6a902" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/gdpr-brexit-wont-break-britain-b15f8bf6a902">GDPR — Brexit won’t break Britain!</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The GDPR Easter egg]]></title>
            <link>https://medium.com/eudpr/the-gdpr-easter-egg-7005bd5f44e6?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/7005bd5f44e6</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[opportunity]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Mon, 18 Mar 2019 17:26:28 GMT</pubDate>
            <atom:updated>2019-03-18T17:26:28.034Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TPdpevNyViyg4byuEPuobQ.jpeg" /></figure><p>For those who have been fighting for privacy, the GDPR came as good news but for most companies this European regulation has rather been seen as a pain in the neck and maybe even as a threat.</p><p>But there may be some hidden good news for companies outside of EU. An Easter egg of sorts…</p><p>To understand the opportunity, we first need to see what problem Europe needed to address.</p><p>The GDPR is the first European law which can entail fines for companies outside of Europe. The United States have been playing at this game for a long time with their embargo related laws or even their tax laws. But the United States are just that: United whereas the “United States of Europe” find it very difficult to agree on almost any topic.</p><p>If a company, outside of the United States, decides to go and sell goods to Iran for instance, the embargo law kicks in and the US shuts out that company from doing any further business with the United States except if they pay a massive fine. This works really well.</p><p>Now with the GDPR Europe has two problems. The first is that shutting out a company from doing business with the whole of Europe would need a next to impossible agreement and would be difficult to enforce. The second difficulty is that GDPR is meant to apply to tiny companies and not only to huge ones such as Google. So, the question is: how ever can Europe make the smaller players be part of the overall effort?</p><p>It is important to understand that the point of the GDPR is not to “make money” with the fines but to bring about a real shift in the way companies process and respect personal data. Hence it mattered to the regulators that the small companies play the game.</p><p>And this is where an Easter egg, to sweeten the deal, has been hidden. Article 27 states an “obligation” which could in fact be a hidden gift.</p><p>Article 27 says “Where <a href="https://eudpr.com/gdpr#article3">Article 3</a>(2) applies, the controller or the processor shall designate in writing a representative in the Union”.</p><p>What this means is that, from now on, if a non-EU company wants to do business, or simply interact, with European citizens, they have the obligation to name a representative in Europe.</p><p>The idea is obviously to simplify communication with the company, if needed. Solving the language issue is, in itself, a big plus.</p><p>But it also opens up a great opportunity because Europe is actually saying that any company abroad is entitled to have an official ambassador in Europe without needing to register offices or risking taxes for being in Europe. Any company can now officially reassure their clients and investors by displaying their presence in Europe.</p><p>Having a European representative costs next to nothing and authorizes a non-EU company to display their Representation address in Europe. It is a win-win situation both for Europe, which is anxious to protect the European citizens’ personal data, and for the non-EU company which has an official foot in Europe at hardly any cost at all.</p><p>This is unique and precious for non-EU companies as long as they choose reliable representatives and cash on to this opportunity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7005bd5f44e6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/the-gdpr-easter-egg-7005bd5f44e6">The GDPR Easter egg</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Must know for non-EU companies exposed to the GDPR]]></title>
            <link>https://medium.com/eudpr/must-know-for-non-eu-companies-exposed-to-the-gdpr-d86e4171631f?source=rss----50ab20c40289---4</link>
            <guid isPermaLink="false">https://medium.com/p/d86e4171631f</guid>
            <category><![CDATA[gdpr]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[article-27]]></category>
            <dc:creator><![CDATA[Remy Wilders]]></dc:creator>
            <pubDate>Mon, 04 Feb 2019 15:23:25 GMT</pubDate>
            <atom:updated>2019-02-04T15:23:25.425Z</atom:updated>
            <content:encoded><![CDATA[<p>By now it is safe to say that probably all companies within Europe and most companies outside of Europe have heard about the GDPR. Far from being just one more administrative pain to deal with this regulation turns out to be a huge shift in the way the world will be doing business from now on.</p><p>As we all know the GDPR is aimed at protecting the European citizen with one big idea: the data belongs to the users and not to the companies who handle it. There would be so much to say about this however the point of this article is to discuss one of the implications of the law, the article 27 [<a href="https://www.eudpr.com/gdpr#article27">https://www.eudpr.com/gdpr#article27</a>].</p><p>The article 27 [<a href="https://www.eudpr.com/gdpr#article27">https://www.eudpr.com/gdpr#article27</a>] applies to any company which is not based in Europe but which has European users and/or customers. What it says, in a nutshell, is that if European residents have some exposure to your company, should it be by browsing your website or by buying your products or services, then you will probably need a GDPR representative based in Europe.</p><p>So the first question is obviously: when will you not need a GDPR representative? The answer to that seems simple: you do not need a GDPR representative when you do not gather or process personal data [<a href="https://www.eudpr.com/gdpr#article4">https://www.eudpr.com/gdpr#article4</a>] on a regular basis (note that this applies to non sensitive data because handling sensitive data will always require a GDPR representative). You may think to yourself that simple internet sites with no user registrations are therefore off the hook. Well you would be mistaken because most internet sites collect the IP addresses of those who visit and IP addresses are considered personal data… and they are being collected on a regular basis. Such sites need to either stop storing IP logs or start right now implementing the correct set of actions to make their business GDPR compliant.</p><p>Getting back to the article 27, the GDPR says that you can be fined [<a href="https://www.eudpr.com/gdpr#article83">https://www.eudpr.com/gdpr#article83</a>] if you have european users whilst being outside of Europe and not having a representative.</p><p>At this stage, you may think that your company will be lost in the crowd of companies and that the GDPR “Supervisory authorities” will never notice your website or have bigger fish to fry. The thing is it will not be the Supervisory authorities who will be on the lookout, it will be your users! That means that if one of your users is data sensitive or even if he simply has a grudge against your company or your website he now has an incredible tool for getting back at you. All he needs do is to fill in a form on one of the 27 EU Supervisory authorities’ sites and you will receive a notice within a couple of days. The first obvious question will be “Who is your GDPR representative in Europe?”.</p><p>Let’s say that you do not have a representative and that one of the Supervisory authorities sends you a fine, why would you pay it? After all Europe is a long way away. That is true but… there is always a but… in addition to the fine your company will be publicly listed as being non compliant to the GDPR and many of the major providers (Amazon, Google, Facebook…) have announced that they will not host or provide services to non GDPR compliant companies (with european users). Your access to the market may hence suddenly shrink quite dramatically. In addition to this you can have a reputation issue as your users may hear that you are not GDPR compliant which means, to the european public, that you do not protect their personal data, or — even worse — you are using it against their interests. Would you feel safe on such a site?</p><p>Having a GDPR representative is not enough to say that your business is GDPR compliant but it is a first step. Nonetheless, by choosing your representative wisely, not only will he provide you the tools and the walkthrough for becoming compliant but he will be your first protection to dealing with the GDPR Supervisory authorities.</p><p>Let’s take an example. Imagine you discover that your system has been hacked into and that your users’ emails and passwords have been accessed. This could be a real problem as most people use the same passwords on different websites. Even if your site does not hold sensitive data the pirates may be able to use the emails and passwords to access other sites which could hold private data or enable the pirate to act as if he were the user. The GDPR demands that each relevant Supervisory authority be informed, in its own language, within 72 hours and be told what you will do about the data breach (for example, in this case, you would inform the users and advise them to change their passwords on the other sites). Having your system hacked is not a cause for being fined — except if your security turns out to have been obviously flawed — but lacking to advise the Supervisory authorities in time will necessarily entail a fine.</p><p>That is where your GDPR representative is your best ally (if he is reliable). He will ask you all the relevant questions regarding the data breach and inform each Supervisory authority, in the local tongue, according to where your users are located. So what could have turned out to be a nightmare can end up as a set of formalities.</p><p>Choosing the right GDPR representative is key. You need to find one who cares and who is really your partner both in helping you become compliant and in times of GDPR trouble. At the same time you may never turn out having a serious GDPR issue and some solutions may be an overkill and obviously costly.</p><p>Being based in Europe and having been a GDPR consultant for both very large and small companies, I believe we have set up an efficient answer for the needs of small to medium-sized enterprises. Should this be of any interest to you, further information can be found on our website eudpr.com [<a href="https://www.eudpr.com/">https://www.eudpr.com</a>].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zN0o3Q5A5bILuPAlVXywQw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d86e4171631f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eudpr/must-know-for-non-eu-companies-exposed-to-the-gdpr-d86e4171631f">Must know for non-EU companies exposed to the GDPR</a> was originally published in <a href="https://medium.com/eudpr">EUDPR</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>