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

A.1.4.8 Retention

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

A mid-sized engineering company deletes nothing as a matter of principle. HR keeps the files of every former employee since the company was founded, sick notes and warnings included. The CRM still lists contacts at customers who have not ordered anything for fifteen years. The reason given is always the same: some period or other might still apply. A.1.4.8 requires personal data to be kept no longer than its purpose needs, and this to be laid down in maintained retention schedules that weigh legal, regulatory and business requirements against each other.

Without a retention schedule, deletion has no trigger. The control lays the foundation on which every later deletion rests.

What does the standard require?

The control consists of a principle and a tool.

  • The principle. Personal data is kept only for as long as the purpose of its processing requires.
  • The tool: retention schedules. The organization draws up schedules for the information it keeps and keeps them current. The principle of the shortest possible retention feeds into these schedules.
  • Three sources of periods. The schedules take legal, regulatory and business requirements into account.
  • Decide and document conflicts. If these requirements contradict each other, the organization takes a business decision based on a risk assessment and records it in the relevant schedule.

In practice

Record the data categories. Application documents, personnel files, payroll records, customer master data, contracts, invoices, support cases, video recordings, logs: each category gets a row in the schedule. Useful columns are purpose, period, starting event, reason for the period, responsible person, systems affected and deletion method.

Identify legal periods. Commercial and tax law require certain documents to be kept for several years (→ HGB & AO German Commercial Code and Tax Code). Sector-specific rules come on top. Record the sources in the Legal Compliance Register so that changes get noticed.

Name business reasons. Defending against possible claims can also justify retention, as long as such claims are realistic. A reason of this kind is named specifically and given a time limit.

Separate the components. A customer record consists of parts with different periods. The invoice stays as long as tax law requires, the marketing consent until it is withdrawn, the support ticket only a few months after closure. Deletion happens per part.

Record conflicts. If sales wants to keep the customer history longer than the purpose supports, the risk is assessed and a decision taken. Justification, outcome and approval go into the schedule. In Germany, DIN 66398 has become established as a method for deriving periods and deletion rules.

Review regularly. An annual review of the schedule has proven useful, plus a review whenever laws or processing activities change.

Typical audit evidence

For A.1.4.8, auditors typically expect:

KPI

% of PII datasets with defined and enforced retention periods

Dataset here means a data collection or data category. Defined means: the period is in the schedule with its starting event and justification. Enforced means: a deletion job or a scheduled task makes sure the period is kept. The target is 100%.

Supporting KPIs:

  • Number of data collections past their period
  • Share of periods with a documented legal basis or business justification
  • Date of the last complete review of the schedule

A.1.4.8 puts storage limitation under Article 5(1)(e) GDPR into practice. Articles 13(2)(a) and 14(2)(a) require data subjects to be told the storage period or the criteria used to set it, which is hardly possible without a schedule. Article 30(1)(f) provides for the envisaged time limits for erasure in the record of processing activities, where possible. Legal retention obligations support retention through Article 6(1)(c) and limit the right to erasure under Article 17(3)(b) (→ GDPR General Data Protection Regulation).

A.1.4.8 supplies the periods that other controls put into effect:

Sources

Frequently asked questions

May I keep data longer than the purpose requires if a law demands it?

Yes, the legal obligation then becomes the reason for retention in its own right. For that period, the data serves only the obligation and is blocked for other uses. Once the period expires, it is deleted.

How do I handle records to which different periods apply?

Split the record into its components. A customer's invoices are subject to different periods than their marketing consent or their support requests. The retention schedule states the period per component, and deletion follows these partial periods.

What if a business unit and the privacy function want different periods?

This is exactly the case the standard addresses: the organization takes a business decision based on a risk assessment and records it in the retention schedule. The conflicting requirements, the assessment, the outcome and who decided are documented.

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.