Rigsrevisionen โ€“ No Violation (Denmark, 2023)

No Violation
Datatilsynet (Norway)14 November 2023Denmark
final
ePrivacy
No Violation

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.

Rigsrevisionen was investigated by the Danish DPA but found not to have violated any data protection rules. This is significant because it shows that organizations can operate within legal frameworks while handling personal data responsibly.

What happened

The Danish DPA investigated Rigsrevisionen's data processing practices but found no violations.

Who was affected

Rigsrevisionen, which processes personal data as part of its auditing functions.

What the authority found

The Danish DPA concluded that Rigsrevisionen's data processing was necessary for its public duties and complied with data protection rules.

Why this matters

This case illustrates that proper data handling can lead to positive outcomes in regulatory reviews. Organizations should ensure their practices align with legal requirements to avoid issues.

GDPR Articles Cited

AI-verified

Art. 5(1)(c) GDPR
Art. 6(1)(e) GDPR
View original scraped data
Art. 5(1)(c) GDPR
Art. 6(1)(e) GDPR
Art. 9(2)(g) GDPR

Original data from scraper before AI verification against source document.

National Law Articles

AI-identified

ยง 12(1) Danish Auditor General Act
Source verified 11 April 2026
articles corrected
national law identified
authority corrected
Full Legal Summary
Detailed

On 29 August 2023, the Danish DPA started a probe into Rigsrevisionen's data processing practices. Rigsrevisionen is an independent institution placed under the Danish parliament conducting audits to determine whether the public accounts are correct and whether government-funded agencies and enterprises comply with current laws and regulations. Because of this function, the DPA considered Rigsrevisionen to be a processor. The DPA aimed to assess the legal basis of the data processing under Article 6 GDPR and how the processor ensures compliance with the principle of data minimisation of Article 5(1)(c) GDPR. The processor stated that its tasks follow the Danish Auditor General Act and special legislation, which also gives it authorisation to obtain material containing personal data by terminal access to the audited authority's systems. It emphasised that its processing is considered necessary for the performance of a task carried out in the public interest or the exercise of official authority under Article 6(1)(e) GDPR and Article 9(2)(g) GDPR. Although the processor further stated that it is not always relevant and necessary for its auditing activities to obtain personal data, its employees are instructed to justify and document if personal data is to be collected. Following the report, the Danish DPA asked the processor to clarify its utilisation of terminal access to access personal data. The processor explained that, in practice, terminal access is primarily used in connection with financial audits and that this system allows it to search for specific accounting documents and data, avoiding retrieving entire cases. It clarified that that it does not have unlimited terminal access to all the auditee's systems or cases, as the audited authority decides whether terminal access should be made available to the processor and there needs to be an agreement. For example, an agreement is in place with the Danish Agency for Public Finance and Management. From the agreeme

Outcome

No Violation

The DPA investigated and found no violation.

Related Enforcement Actions (0)

No other enforcement actions found for Rigsrevisionen in DK

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

Details

Decision Date

14 November 2023

Authority

Datatilsynet (Norway)

GDPRhub ID

gdprhub-6568

About this data

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

Cite as: Cookie Fines. Rigsrevisionen - Denmark (2023). Retrieved from cookiefines.eu

Report Inaccuracy

Last updated: