Zum Hauptinhalt springen
ISO/IEC 27701:2025 · Annex A, Table A.1 · Control for PII controllers

A.1.3.9 Providing copy of PII processed

Updated on 5 min Reviewed by: Cenedril Editorial
ISO/IEC 27701:2025GDPR

A car-sharing provider receives a customer’s request for a copy of his data. Support pulls a 40 MB database export with no explanations and table names like “trp_evt_raw”. It also contains the names of fellow passengers and internal fraud scores of other customers. The customer cannot open the file, had actually wanted to take it to a competitor, and reports the third-party data he found to the supervisory authority. A.1.3.9 requires the organization to be able to give data subjects a copy of their processed data on request: readable, limited to the person and, where required, portable.

The copy is the most tangible part of the right of access. Whoever can deliver it quickly and cleanly proves at the same time that they have their data under control.

What does the standard require?

The control describes the form, content and limits of the copy.

  • Copy on request. The organization is able to provide a data subject with a copy of the data processed about them.
  • Structured and common. The copy comes in a structured, widely used format the person can open.
  • Portability where required. Some jurisdictions require, in certain cases, a form that can be transferred to the person or to another controller, typically machine-readable.
  • Only their own data. The copy contains exclusively data relating to the person asking.
  • Already deleted. If the data has already been removed under the retention and disposal rule (A.1.4.8), the person is told that it has been deleted.
  • No re-linking just for the request. If the organization can no longer identify the person, for example after de-identification, it does not restore the link only to satisfy this control. In some jurisdictions, though, a legitimate request may require asking the person for additional details.
  • Direct transfer. Where technically feasible, a copy can be sent directly to another organization at the person’s request.

In practice

Prepare exports per system. For each system holding personal data, decide how one person’s data can be exported and in which format. Whoever only starts looking for a route when the first request arrives quickly runs out of time.

Remove other people’s data. Before sending, a second person checks the copy for data about others: fellow passengers, contacts in tickets, internal notes about third parties. These details are redacted or removed. Sending a copy that contains other people’s data is a data breach in itself.

Name deleted data honestly. If data has already been deleted under the retention schedule, the reply says so explicitly. A template for this message saves time and keeps employees from pulling deleted data back out of backups.

Set the rule for unlinkable data in advance. Under time pressure, the temptation to search de-identified data sets after all is strong. Write down beforehand that the reply in such cases points out the missing link and, where the law provides for it, asks the person for additional details.

Transmit securely. The copy only goes out once identity has been checked, preferably as an encrypted download with limited validity. For direct transfer to another organization, interfaces or agreed file formats work, provided the recipient can accept them.

Typical audit evidence

For A.1.3.9, auditors typically expect:

  • Procedure description for copies and data portability with deadlines and responsibilities
  • Export functions per system with the format stated
  • Check before sending with a four-eyes review for other people’s data
  • Reply templates for deleted and unlinkable data (→ Deletion Evidence Log)
  • Dispatch records with a secure transmission route (→ Information Transfer Policy)

KPI

% of PII copy requests fulfilled in structured, machine-readable format

Every answered request for a copy delivered in a structured and machine-readable format counts, set against all copy requests. The target is 100%. The readable overview comes on top and does not replace the machine-readable file.

Supporting KPIs:

  • Share of copies with a documented check for other people’s data
  • Average time from request to delivery
  • Share of systems with a prepared per-person export

The right to a copy is set out in Article 15(3) GDPR. The first copy is free, and where the request is made electronically, it is provided in a commonly used electronic form. Article 15(4) protects the rights of others. In 2023, the Court of Justice ruled that the copy must be a faithful and intelligible reproduction of all the data, including extracts from documents where necessary (C-487/21). Data portability is governed by Article 20: structured, commonly used and machine-readable, with direct transmission where technically feasible. Article 11(2) covers cases in which the organization cannot identify the person, and Article 12(6) the verification of identity (→ GDPR General Data Protection Regulation).

The copy draws on retention, deletion and the request process:

Sources

Frequently asked questions

How do a copy and data portability differ?

The copy under Article 15(3) GDPR covers all data processed about the person and has to be readable for them. Portability under Article 20 concerns only data the person provided, where processing is automated and based on consent or contract, and requires a machine-readable format. Many organizations serve both with one package of a readable overview and a machine-readable file.

May a fee be charged for the copy?

The first copy is free of charge under Article 15(3) GDPR. For further copies, a reasonable fee based on administrative costs may be charged. For manifestly unfounded or excessive requests, Article 12(5) allows a fee or a refusal, which the organization then has to justify.

What about data that can no longer be linked to a person?

If the organization can no longer link the data to anyone, the standard says it does not restore the link just for the request. If the person supplies details that allow identification under Article 11(2) GDPR, the right applies again. Fully anonymized data is no longer personal data and falls outside the right to a copy.

No Cookies!

This wiki collects nothing, bakes nothing and leaves nothing behind. There's nothing to consent to. Privacy doesn't get better than this.