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

A.1.4.7 Temporary files

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

A billing service produces account statements as PDFs every month and places them briefly in a staging folder for dispatch. After dispatch they should disappear. Two years ago, an update quietly disabled the clean-up step. A server review turns up more than a hundred thousand files with names, addresses and bank details, contained in every single backup since the update. A.1.4.7 requires temporary files containing personal data to be disposed of under a documented procedure within a defined period, and regular checks to confirm that this really happens.

Temporary files are the blind spot of many deletion concepts. They appear in no record of processing, nobody regards them as a data set, and precisely for that reason they often outlive the data they came from.

What does the standard require?

The requirement is short; implementing it calls for knowing your own systems.

  • Dispose of by procedure and deadline. Temporary files that arise while personal data is processed are erased or destroyed. A documented procedure defines how this happens. A defined period, also documented, sets the latest point at which it happens.
  • Check regularly. The organization verifies at intervals whether temporary files no longer in use have gone within the period.
  • Background from the standard. Information systems create such files all the time during normal operation, for instance roll-back journals of the file system or intermediate files during database updates, depending on the system. Once the task is complete they are superfluous, yet they cannot always be removed at once, and how long they are needed is not always predictable. A clean-up procedure therefore finds the relevant files and establishes how long ago they were last used.

In practice

Record the locations. Typical candidates are system directories for intermediate files, upload and import folders, print queues, export directories, application and browser caches, memory dumps after crashes, temporary database tables and staging tables of data pipelines. On end user devices, the downloads folder and locally saved email attachments come on top.

Set period and method per location. Define for each location after how much time since last use files are deleted, and by what means: script, scheduled job, operating system setting or retention rule of the application. Record this in the system’s operating documentation or in the Records Retention Schedule.

Dispose of securely. For sensitive content, deleted means more than moved to the recycle bin. Encrypting directories for intermediate files, or keeping them in memory, has proven useful, so that remnants on the storage medium stay unreadable.

Keep memory dumps and debug logs tight. After a crash, memory dumps often contain the entire working memory, personal data included. They belong in a protected area with a short deletion period.

Look regularly. Set a review interval, for example quarterly. At each review, the listed systems are searched for files older than the period. Leftovers are deleted, and date, system and result are recorded.

Typical audit evidence

For A.1.4.7, auditors typically expect:

KPI

% of temporary files containing PII with automated deletion controls

Individual files can hardly be counted. In practice, the figure is therefore measured across the recorded locations: the share of locations where an automated clean-up job with a documented period is running. The target is 100%. Checks that uncover new locations lower the value for a while, and that is a good sign.

Supporting KPIs:

  • Age of the oldest temporary file found at the last check
  • Number of checks with findings per year
  • Share of systems with an encrypted directory for intermediate files

Storage limitation under Article 5(1)(e) GDPR applies to every copy of personal data, a temporary one included. Leftover intermediate files also easily breach data minimization under Article 5(1)(c). Article 5(1)(f) and Article 32(1) require protection against unauthorized access, and forgotten files are a typical way in. Article 25(2) calls for the storage period to be limited through the default settings already. If such files reach unauthorized people, this may be a notifiable personal data breach under Article 33 (→ GDPR General Data Protection Regulation).

A.1.4.7 extends the deletion rules to whatever arises on the side:

Sources

Frequently asked questions

What counts as a temporary file?

Any file that a system or a person creates for a single work step: intermediate files during an import, exports for a reconciliation, print jobs in the queue, memory dumps after a crash, file system and database journals. What matters is the content. As soon as personal data is in it, the file falls under the control.

How long may the period be?

The standard sets no figure; it requires a defined and documented period. Hours to a few days after last use are common, depending on the system and the protection need. What matters is that the period suits operations and is actually kept.

Is an automated clean-up job enough?

It is the most important building block, yet it only covers the locations it knows. That is why the standard also requires regular checks. They show whether the job runs and whether temporary files have appeared in new places it does not yet cover.

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.