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

A.1.3.7 Access, correction or erasure

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

A recruitment agency receives a request from a former applicant to delete all data about him. HR removes the profile from the applicant tracking system and confirms the deletion. Four weeks later, the man receives a newsletter with job offers: his address was still in the mailing tool, his CV in a ticket and in a spreadsheet on the shared drive. A.1.3.7 requires rules, procedures and technical routes that let data subjects see, correct and erase their data, promptly and in every system.

Access, correction and erasure are the rights data subjects use most often. Most failures happen while hunting down the individual copies of the data.

What does the standard require?

The control describes the path from the request to implementation in every system.

  • Rules, procedures, mechanisms. The organization puts in place what is needed for data subjects to obtain access to their data and have it corrected and erased, on request and without undue delay.
  • Set a response time. There is a defined deadline, and requests are handled within it.
  • Pass changes on. Corrections and erasures reach all affected systems and authorized users and are forwarded to third parties to whom the data was transferred (A.1.3.8). The records under A.1.5.4 help to find those recipients.
  • Handle disputes. There is a procedure for cases where the accuracy of the data or a correction is contested. The person learns what was changed and, where a correction is not possible, why.
  • Know the restrictions. Some jurisdictions limit when and how correction or erasure can be requested. The organization identifies these limits and keeps its knowledge of them current.

In practice

Fix the procedure. Receipt, identity check, search, decision, implementation, passing on and reply form the steps. For each step, it is clear who is responsible and how long it takes. The identity check stays proportionate; a copy of an ID is usually unnecessary when the request comes from a known email address.

Keep a search list per group of people. Use the record of processing activities and the asset register to decide in which systems the data of customers, employees or applicants is held. Mailboxes, ticket systems, shared drives, exports and departmental tools belong on it too.

Check the limits of erasure. Retention duties under commercial and tax law, pending proceedings or legal claims can stand in the way of erasure. The data is then blocked for all other purposes and deleted when the period expires. Keep the state of the law for each jurisdiction up to date in the legal register.

Include backups. Record how deletions are handled in backups. Letting data expire with the rotation cycle, combined with a deletion list in case of a restore, is common practice.

Handle disputes cleanly. If a person contests accuracy, processing is restricted during the review. The outcome goes to the person with reasons, and the file shows which changes were made or refused.

Typical audit evidence

For A.1.3.7, auditors typically expect:

  • Procedure description for access, correction and erasure with deadlines and responsibilities
  • Request log with receipt, identity check, decision, reply and deadline compliance
  • Search list of systems per group of people (→ Asset Register)
  • Proof of deletion for completed requests (→ Deletion Evidence Log)
  • Retention periods that may stand in the way of erasure (→ Records Retention Schedule)

KPI

% of data subject access, correction and erasure requests fulfilled within deadline

Within deadline means: answered and implemented within the defined response time and at the latest within the statutory deadline. The target is 100%. A request only counts as fulfilled once it has also been passed on to recipients.

Supporting KPIs:

  • Average handling time per type of request
  • Share of erasure requests for which the full search list was worked through
  • Number of disputes with documented reasons

A.1.3.7 bundles several GDPR rights: access under Article 15, rectification under Article 16, erasure under Article 17 and restriction under Article 18. Article 17(1) lists the grounds for erasure and paragraph 3 the exceptions, among them statutory retention duties and legal claims. Article 19 requires recipients to be informed of rectifications, erasures and restrictions. Under Article 12(3), the deadline is one month, extendable by two further months, and Article 12(4) requires reasons if the organization does not take action. The underlying principle is accuracy under Article 5(1)(d). In Germany, section 35 of the Federal Data Protection Act supplements the erasure duty, and retention periods follow from commercial and tax law, among others (→ HGB & AO German Commercial Code and Tax Code, GDPR General Data Protection Regulation).

Annex D of the standard also maps A.1.3.7 to Article 13(2)(b) and Article 14(2)(c): the information given at collection already points to the rights of access, rectification and erasure.

Putting the rights into practice touches many controls:

Sources

Frequently asked questions

What happens to data in backups?

Individual records often cannot be removed from backups in a targeted way. A common approach is therefore to let the data expire with the regular rotation cycle and to keep a deletion list that is applied again after every restore. Until then the backups are used for no other purpose, and the person is told how they are handled.

May erasure be refused because of retention duties?

Where a law requires retention, for example for invoices under commercial and tax law, the exception in Article 17(3)(b) GDPR applies. The data is then blocked for all other purposes and deleted once the period ends. The person learns which data remains and why.

How do I handle a disputed correction?

If the person contests the accuracy of their data, they can ask under Article 18(1)(a) GDPR for processing to be restricted during the review. Afterwards, you tell them what was changed or why a correction is not possible. Both belong in the request file.

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.