Aarhus municipality – Violation Found (Denmark, 2022)

Violation Found
Datatilsynet (Norway)8 September 2022Denmark
final
Violation Found

General GDPR enforcement action

This case relates to broader data protection obligations, not specifically to cookie or consent banner compliance. It is not included in cookie statistics or the Risk Calculator.

Aarhus municipality in Denmark was found to have potential high-risk data processing activities using Google products. The Danish Data Protection Authority ordered them to make changes to their data processing agreements and improve their data protection practices. This highlights the importance of assessing and documenting data processing risks, especially when using third-party services.

What happened

Aarhus municipality's use of Google products posed high risks to personal data, prompting the Danish DPA to demand changes to their data processing agreements.

Who was affected

Students and staff whose personal data was processed using Google Chromebooks and Google Workspace for Education.

What the authority found

The Danish DPA found that Aarhus municipality's data processing setup with Google products involved high risks that were not adequately mitigated, requiring corrective actions.

Why this matters

This case underscores the need for municipalities and businesses to thoroughly assess data processing risks and ensure compliance with GDPR when using third-party services. It serves as a reminder to regularly update data protection impact assessments and consult authorities when risks cannot be mitigated.

GDPR Articles Cited

Art. 36 GDPR
Art. 28(3)(a) GDPR
Art. 36(1) GDPR
Art. 36(2) GDPR
Art. 58(2)(d) GDPR
Full Legal Summary
Detailed

Following the Danish DPA's (Datatilsynet) decisions (from September 2021 as well as July and August 2022) related to Helsingor municipality's processing of personal data using Google products and services, Aarhus municipality reassessed their risk assessment during August 2022. On 1 September, they sent the DPA a request for consultation as per Article 36 GDPR along with the relevant documentation, as they were using the same processing setup (Google, Google Chromebooks, Google Workspace for Education). Based on the documentation submitted, the DPA found that the processing activities entailed a high risk for the data subjects' rights and freedoms that could not be mitigated, and referred to Article 36(1) GDPR and Article 36(2) GDPR. The DPA ordered the municipality to: * Change the data processing agreement with Google so that the DPA's remarks in their 14 July and 18 August decisions to Helsingor municipality, are implemented. This includes, at a minimum, a clarification of where and if Google acts as a sole controller and any uncertainties that may entail that Google acts beyond their role as a processor, see Article 28(3)(a) GDPR. * Document that all transfers of personal data to insecure third countries, are in line with the GDPR. * Describe all data flows and identify the personal data that are shared with the vendor, and clarify when the vendor acts as a sole or joint controller. This documentation must include the whole technology stack used by the municipality (for this processing activity). * Update their data protection impact assessment based on all identified risks. * Consult the DPA if the DPIA shows any high risks the municipality is not able to mitigate. * If any processing activities are still not in line with the GDPR before the DPA's deadline 3 November 2022, present a final plan for bringing them in line with the GDPR.

Outcome

Violation Found

The DPA found a violation but did not impose a fine.

Related Enforcement Actions (0)

No other enforcement actions found for Aarhus municipality in DK

This is the only recorded action for this entity in this jurisdiction.

Details

Decision Date

8 September 2022

Authority

Datatilsynet (Norway)

GDPRhub ID

gdprhub-5244

About this data

Data: GDPRhub (noyb.eu)
Licensed under CC BY-NC-SA 4.0
AI-verified and classified

Cite as: Cookie Fines. Aarhus municipality - Denmark (2022). Retrieved from cookiefines.eu

Report Inaccuracy

Last updated: