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

A.2.4.3 Return, transfer or disposal of PII

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

A small sports club manages its members in online software. The stored credit card expires, the invoice stays unpaid, and the contract ends automatically. The next morning, all member data is gone, without warning and without any chance to export. At the same time, another customer of the same provider asks for confirmation that its data was deleted after termination. The provider cannot give it, because nobody knows what happened to backups, exports and the support system. A.2.4.3 requires that you can hand personal data back, pass it on or destroy it securely, and to share with the customer the policy under which this happens.

The end of an assignment is a risky moment. Data the customer still needs can be lost, or data can linger somewhere long after its purpose has been served. A clear rule prevents both.

What does the standard require?

A.2.4.3 combines a technical capability with a policy the customer can see.

  • Capability for secure return, transfer and disposal. You can hand data back to the customer, transfer it to another organization or controller, for example after a merger, delete or destroy it, de-identify it or archive it. This capability is managed securely.
  • Assurance for the customer. The customer should be able to rely on data from the contract being erased as soon as it is no longer needed for their purposes. This applies at your end and at your subcontractors, at every storage location, explicitly including backups and business continuity storage.
  • Disposal policy. You write a policy on disposing of personal data, put it into practice and give it to the customer on request.
  • Protection against accidental loss. The policy states how long data is kept after the contract ends before disposal begins. This way the customer does not lose their data if a contract lapses by mistake.
  • Link to retention. The standard points out that the control also matters for the retention principle in A.1.4.8.

In practice

Enable export and handover. Offer a complete export in a documented, common format. For a switch to another provider, a described handover with secured transfer and confirmation that the data arrived in full will help.

Set and announce a grace period. Decide how long data remains after the contract ends, and inform the customer before deletion starts. With contracts that end automatically in particular, a reminder protects against data loss.

Prove deletion across all locations. Delete along the storage location catalogue and confirm each location individually. Have every subcontractor confirm deletion. For rolling backups, state the date on which the last affected backup expires.

Name exceptions openly. If a legal duty forces you to keep data, record which data is affected, on what basis and until when. Everything else is deleted.

Issue a deletion confirmation. Once finished, give the customer a confirmation with date, scope, storage locations and, where relevant, the expiry date of the backups. It is their evidence towards their own auditors.

Typical audit evidence

For A.2.4.3, auditors typically expect:

  • Disposal policy with the grace period after the contract ends, storage locations and procedures, available to customers on request (→ Data Deletion, Masking & Leakage Prevention Policy)
  • Storage location catalogue per service, including backups and subcontractors
  • Deletion confirmations to customers with date, scope and backup expiry (→ Deletion Evidence Log)
  • Confirmations from subcontractors that deletion has taken place
  • Retention periods for data under a legal duty to store (→ Records Retention Schedule)

KPI

% of PII return/disposal requests completed per contractual terms

What counts are all requests for return, handover or deletion and every contract end. Completed means: done within the agreed period, across all storage locations including subcontractors, with confirmation to the customer. The target is 100%.

Supporting KPIs:

  • Share of contract ends where the customer was reminded before deletion began
  • Share of deletions with confirmation from every subcontractor
  • Average time from contract end to complete deletion including backups

Under Article 28(3)(g) GDPR, the processor deletes or returns all personal data after the end of the services, at the controller’s choice, and deletes existing copies unless Union or Member State law requires them to be stored. Behind this stands the principle of storage limitation in Article 5(1)(e). The envisaged time limits for erasure belong in the controller’s record under Article 30(1)(f) where possible. Your policy gives the controller the details for this (→ GDPR General Data Protection Regulation).

A.2.4.3 governs the end of every processing assignment:

Sources

Frequently asked questions

How do I deal with backups from which individual customers cannot be deleted?

Describe openly how your backups work: how long they are kept, how they are protected and when the last backup containing the customer's data expires. The customer then receives a date on which the data has disappeared everywhere. Until then, it is used only for restoration.

How long should the grace period after the end of the contract be?

The standard gives no figure. A few weeks in which the customer can still export their data before deletion starts are common. What matters is that the period is in the contract and that the customer is reminded before it expires.

May I keep data after the contract ends because a law requires it?

Yes, if a legal duty to store applies to you. This exception must be named specifically, and the data may then only be kept for that purpose. General reasons such as possible later disputes are not enough.

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.