Right of access under Art. 15 GDPR: what the CJEU ruling means

The Court of Justice of the EU ruled on 5 November 2026 that people can claim the right of access under Art. 15 GDPR from a data protection authority too. The reasoning applies to any organisation that handles access requests, including those with complaint files and AI tools.

Klaus Bauer4 min read

Illustration: A filing cabinet with an open drawer and a magnifying glass, with a mirror reflecting the drawer back, symbolising access rights against the regul

Does the right of access apply to the regulator too?

The question reached the court from a Bavarian case, reported by Dr. Datenschutz. A journalist had filed a complaint with the Bavarian state office for data protection supervision, known as the BayLDA. The office opened proceedings against a third party and later said it had found violations.

The complainant then asked for full access under Art. 15 GDPR, including a copy of his personal data from the complaint file. The office refused and relied on Art. 20(2) of the Bavarian data protection act, which excludes rights of access to the files of supervisory authorities. The administrative court in Ansbach referred the matter to the CJEU, which answered that the right of access applies.

Why a supervisory authority can be a controller

Under Art. 4 No. 7 GDPR, a controller is a body that decides on the purposes and means of processing personal data. The court read this definition broadly, because the aim is effective and comprehensive protection of the people concerned. A supervisory authority must handle complaints under Art. 57(1)(f) GDPR, and in doing so it records, stores, queries and uses the complainant's data.

That is processing within the meaning of Art. 4 No. 2 GDPR. According to the court, the purposes and means follow largely from the EU rules that govern the authority's work, so the authority is the controller for this processing. Otherwise the complainant would lose rights under Chapter III of the GDPR, including access.

The authority had argued that the GDPR assumes a strict separation between supervisor and controller. The court did not accept this and held that a dual role is possible. It added that an authority can organise itself so that another unit inside it independently reviews its own actions as a controller.

Why a blanket exclusion does not hold

Art. 23 GDPR lets member states restrict data subject rights by law. Such a restriction must serve one of the listed aims, respect the essence of fundamental rights and be necessary and proportionate. The court found that a rule excluding Art. 15 access entirely does not meet these conditions.

The protection of third parties was accepted as a legitimate concern, since files may name employees, contacts and others. It does not justify a complete exclusion, because redaction or anonymisation can reconcile the interests. Public security would need a real and sufficiently serious threat to a fundamental interest of society, which the file did not show. The independence and functioning of the authority are legitimate aims, but a general exclusion is disproportionate for them.

Administrative effort does not carry the argument either. Member states must equip their authorities with sufficient staff, technology and funding. Against manifestly unfounded or excessive requests, Art. 12(5) GDPR already allows a fee or a refusal.

What companies can take from the ruling

The decision directly concerns authorities, but the court restated principles that apply to private companies as well. Art. 15 GDPR gives no general right to inspect all documents. Where records also contain data of third parties, the controller cannot simply refuse everything and must check whether partial access is possible. Redaction or anonymisation can protect others without ending the right of access.

Companies can check the following points in their own process, ideally together with their GDPR-compliant AI setup:

  • Whether internal rules refuse access in full whenever a file mentions other people.
  • Whether someone can redact or anonymise documents before they are handed over.
  • Whether complaint files, HR records and e-mail archives can be searched for one person.
  • Whether requests that look excessive are assessed individually under Art. 12(5) GDPR rather than rejected by default.
  • Whether the data protection officer and the works council (Betriebsrat) know who handles requests.

This is general orientation and not legal advice for a specific case. Firms that use AI tools should also know which of those tools store prompts, documents or outputs about individuals, since such data can fall within an access request.

Handling access requests across documents and AI

Answering an access request means finding every place where a person's data sits, across file servers, mailboxes and collaboration tools. An AI platform can help with the search. It needs to work with the existing permissions and show where each answer comes from. souveraen.ai answers questions from connected sources and cites the document, version and page, so a reviewer can check the result.

The platform connects sources such as SharePoint, file servers and Exchange read-only and respects existing permissions. Agents prepare tasks, and anything that writes to a system waits for approval by a person. It runs On Demand, hosted in Germany, or on-premise in your own network, using the same software.

Sources

More articles

All articles

GitLab 19.6 adds an audit log for AI agents

GitLab 19.6 records what AI agents do through its MCP server. A Ruby flaw is patched, but several NGINX flaws remain open, so admins who run GitLab themselves have settings to enable and a workaround to apply.

Models4 min

Transcribe audio locally with faster-whisper in Python

faster-whisper turns recordings such as meetings or dictations into text with a few lines of Python, running on your own hardware. Companies that do not want audio files to reach a cloud service can use it as a practical starting point.

Tutorial4 min

How to Add AI Tools to Your Record of Processing

Art. 30 GDPR requires most companies to keep a record of processing activities, and every AI tool that touches personal data belongs in it. Dr. Datenschutz published a guide to the record in November 2026, which gives you a reason to check how your AI tools are documented.

Data protection4 min

Test it with your own documents.

Free for 3 days, then from €24.90 per user per month. Cancellable monthly.

Free for 3 days, then from €24.90 per user per month.Free for 3 days
Try free for 3 days