{"id":1151,"date":"2021-09-22T22:13:52","date_gmt":"2021-09-22T20:13:52","guid":{"rendered":"http:\/\/blog.eprivacy.eu\/?p=1151"},"modified":"2021-09-22T22:13:52","modified_gmt":"2021-09-22T20:13:52","slug":"high-fines-for-data-protection-breaches","status":"publish","type":"post","link":"https:\/\/blog.eprivacy.eu\/?p=1151","title":{"rendered":"High fines for data protection breaches"},"content":{"rendered":"\n<p>Where do the authorities currently focus their audits? What should you look for if you want to avoid fines? Much can be learned from the decisions of the data protection authorities and the fines currently imposed!<br>\u00a0<br>In this newsletter we report again on interesting cases during the summer months.<\/p>\n\n\n\n<p><strong>Highest fine ever imposed since the implementation of the GDPR<\/strong><\/p>\n\n\n\n<p>\u00a0<br><strong>Company:<\/strong>\u00a0Amazon Europe Core S.\u00e0.r.l<br><strong>Possible data protection breach:\u00a0<\/strong>Proceedings initiated by the French civil rights organisation \u201cLe Quadrature du Net\u201d on the subject of advertising targeting &#8211; personalised advertising and disclosure of data to third parties<br><strong>The Authority:<\/strong>\u00a0CNPD (Luxembourg Data Protection Authority)<br><strong>Amount of the fine:\u00a0<\/strong>EUR 746.000.000<br>\u00a0<\/p>\n\n\n\n<p><strong>Second highest fine in the history of the GDPR<\/strong><\/p>\n\n\n\n<p><strong>&nbsp;<\/strong><strong><br>Company:&nbsp;<\/strong>WhatsApp<br><strong>Possible data protection breach:&nbsp;<\/strong>The proceedings concerned breaches of the transparency requirements from art. 12 &#8211; 14 of the GDPR. The complaint was that the data was forwarded within the Facebook group without being transparent for the user.<br><strong>Authority<\/strong>: DPC (Irish Data Protection Regulator) and EDPB.<br><strong>Amount of the fine:&nbsp;<\/strong>EUR 225.000.000<br>&nbsp;<\/p>\n\n\n\n<p><strong>Further examples from the past two months<\/strong><\/p>\n\n\n\n<p>\u00a0<br><strong>Company:<\/strong>\u00a0AG2R LA MONDIALE (insurance sector) esp. SGAM AG2R LA MONDIALE.<br><strong>Data protection breach:\u00a0<\/strong>art. 5(1)(e) GDPR, art. 13 GDPR, art. 14 GDPR: Violation of storage limitation for more than 2 million customer and prospect data incl. health data. In addition, advertising calls were not carried out properly. The data subjects were neither sufficiently informed about the data processing in accordance with art. 13 of the GDPR, nor were they informed about their right to object.<br><strong>The Authority:\u00a0<\/strong>CNIL (French Data Protection Authority)<br><strong>Fine:\u00a0<\/strong>EUR 1.750.000<\/p>\n\n\n\n<p><strong>Company:\u00a0<\/strong>MERCADONA, S.A.<br><strong>Data protection breach:\u00a0<\/strong>A facial recognition system installed in 40 supermarkets was used, among other things, to track down convicted persons. As all persons were scanned when entering the stores, this included, among others, minors. This means a violation of the principle of data minimisation, a violation of the duty to inform according to art. 13 GDPR, and at the same time a lack of a data protection impact assessment (art. 5(1)(c) GDPR, art. 6 GDPR, art. 9 GDPR, art. 12 GDPR, art. 13 GDPR, art. 25(1) GDPR, art. 35 GDPR)<br><strong>Authority:\u00a0<\/strong>AEPD (Spanish Data Protection Agency)<br><strong>Fine:<\/strong>\u00a0EUR 2.520.000<br>\u00a0<br><strong>Unknown company<\/strong><br><strong>Data protection breach:<\/strong>\u00a0Lack of involvement and independence of the DPO, which prevented him from providing proper and independent advice. For example: lack of involvement in the relevant processes of the processing of personal data, lack of a standardised control plan for compliance with the GDPR and lack of communication to the highest management level. In addition, the DPO was not able to demonstrate sufficient knowledge of data protection law, which could have been deepened with sufficient training (art. 38(1) and (3) GDPR, art. 39(1)(a) and (b) GDPR).<br><strong>The Authority:\u00a0<\/strong>CNPD (Luxembourg Data Protection Authority)<br><strong>Fine:<\/strong>\u00a0EUR 15.000<br>\u00a0<br><strong>Company:<\/strong>\u00a0BANCO BILBAO VIZCAYA ARGENTARIA, S.A.<br><strong>Data protection breach:<\/strong>\u00a0In an automated telephone information service provided by the bank, it was sufficient to provide the ID number of a customer in order to access their account transactions. The authority criticised the breach of the obligation to implement sufficient TOMs (technical and organisational measures) to protect the data (art. 32 GDPR).<br><strong>Authority:\u00a0<\/strong>Agencia Espa\u00f1ola Protecci\u00f3n Datos (AEPD)<br><strong>Fine:<\/strong>\u00a0EUR 120.000<br>\u00a0<br><strong>Company:\u00a0<\/strong>Yes Consumer Solutions Ltd (YCSL) Telecommunications company<br><strong>Data protection breach:<\/strong>\u00a0approximately 200,000 unauthorised advertising calls despite objection. Ironically, the calls were intended to advertise a call protection product marketed by YCSL, which was supposed to enable the blocking of unwanted calls.<br>In addition, all telephone numbers were recorded in the British TPS register. The entry in this register serves to protect against unsolicited calls (art. 55A DPA, art. 21 PECR).<br><strong>Authority:<\/strong>\u00a0Information Commissioner&#8217;s Office (ICO)<br><strong>Fine:\u00a0<\/strong>EUR 199.812 (GBP 170.000)<br>\u00a0<br><strong>Company:<\/strong>\u00a0Vodafone Espa\u00f1a, S.A.U.<br><strong>Data protection breach:<\/strong>\u00a0breach of the obligation to delete data. The right to erasure according to art. 17 GDPR is one of the essential data subjects rights in data protection. Here, companies must respond to the data subjects request within the required deadlines. This requires good deletion concepts (art. 6(1) GDPR, art. 17(1) GDPR).<br><strong>Authority<\/strong>: Agencia Espa\u00f1ola Protecci\u00f3n Datos (AEPD).<br><strong>Fine:\u00a0<\/strong>EUR 96.000<br>\u00a0<br><strong>Company:\u00a0<\/strong>Operator of Aeroporto Guglielmo Marconi di Bologna S.p.a.<br><strong>Data protection breach:<\/strong>\u00a0use of a whistleblowing application without sufficient technical and organisational measures (neither a secure network protocol, nor encryption of the data of the reporter, the reported information or the attached documents was provided). The manufacturer of the whistleblowing software, aiComply S.r.l., was also fined. Here, among other things, the necessary conclusion of processing agreements was missing (art. 5(1)(f) GDPR, art. 25 GDPR, art. 28 GDPR, art. 32 GDPR, art. 35 GDPR).<br><strong>Authority:\u00a0<\/strong>Garante per la protezione dei dati personali (GPDP).<br><strong>Total fine:<\/strong>\u00a0EUR 60.000<\/p>\n\n\n\n<p>Your contact to ePrivacy:<\/p>\n\n\n\n<p><a href=\"https:\/\/t5baa4d95.emailsys1a.net\/c\/107\/4167051\/4225\/0\/11201553\/447\/263283\/9df8a6ddcf.html\">https:\/\/t5baa4d95.emailsys1a.net\/c\/107\/4167051\/4225\/0\/11201553\/447\/263283\/9df8a6ddcf.html<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Where do the authorities currently focus their audits? What should you look for if you want to avoid fines? Much can be<\/p>\n<p class=\"link-more\"><a class=\"myButt \" href=\"https:\/\/blog.eprivacy.eu\/?p=1151\">Read More<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/1151"}],"collection":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1151"}],"version-history":[{"count":1,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/1151\/revisions"}],"predecessor-version":[{"id":1152,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=\/wp\/v2\/posts\/1151\/revisions\/1152"}],"wp:attachment":[{"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1151"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1151"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.eprivacy.eu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1151"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}