What is Storage Limitation?

Storage Limitation - definition

Storage limitation is the European Union (EU) General Data Protection Regulation (GDPR) principle requiring personal data to be kept in a form that permits identification of individuals for no longer than necessary for the purpose for which the data is processed. It is set out in Article 5(1)(e) of Regulation (EU) 2016/679, applicable from May 25, 2018.

The principle does not establish one fixed retention period for all video or image files. Instead, an organization must define and document a retention period that is justified by the specific processing purpose. It must also define what happens when that period ends, such as secure deletion, irreversible anonymization, or transfer to an archive where a lawful archival purpose applies.

For video anonymization, storage limitation applies to original recordings, extracted frames, face detection results, license plate detection results, manually edited files, temporary processing files, backups, and anonymized output. A retention schedule should distinguish these data sets because they do not have the same privacy risk or operational purpose.

Storage limitation for image and video anonymization

Raw footage can identify people through visible faces, license plates, clothing, location, time, and contextual details. It is therefore usually personal data under the GDPR when an individual can be identified directly or indirectly. An organization should not retain original footage simply because it may be useful in the future.

When footage is processed to blur faces and license plates, the retention design should define the purpose and lifecycle of each file type. A common lifecycle includes the following stages.

  1. Collection: The organization receives or records source video or images for a defined purpose, such as preparing material for publication, analysis, training, or controlled sharing.
  2. Temporary processing: Face detection and license plate detection identify areas that require masking. Processing may create temporary frames, preview files, detection coordinates, and edited versions.
  3. Quality review: An authorized reviewer checks whether faces and license plates were blurred correctly and applies manual masking where necessary.
  4. Delivery or approved use: The organization retains the anonymized or masked output for the documented business, research, or publication purpose.
  5. End of retention: The organization securely deletes, anonymizes, or otherwise handles the source files according to its retention schedule and any applicable legal obligation.

Face blurring does not always make footage anonymous. If other details in the footage can reasonably re-identify a person, the output may remain personal data. Recital 26 of the GDPR states that anonymous information is information that does not relate to an identified or identifiable natural person. Organizations should assess the full image or video context, not only whether a face is obscured.

Retention schedule for source footage and derived files

A retention schedule should state the maximum period for each category of footage and derived data. It should also identify the deletion method, responsible role, storage location, and any exception process. The schedule must be applied in practice, not only documented in a policy.

Data category

Typical purpose

Storage limitation question

End-of-period action

Original video or image

Source material for anonymization

How long is the identifiable source needed for processing and verification?

Secure deletion or documented preservation where a separate legal basis applies

Temporary frames and previews

Detection, rendering, and quality control

Can the files be deleted immediately after export or review?

Automated deletion after the processing job or review window

Detection coordinates and edit metadata

Applying and reviewing masks

Can the metadata identify a person when linked to the source file?

Delete with the source file unless a justified operational need remains

Blurred output

Approved publication, sharing, or analysis

Is the output effectively anonymous, or does it remain identifiable through context?

Retain only for the stated purpose and review periodically

Backup copies

Business continuity and recovery

Does the backup retention period exceed the production retention period?

Delete or overwrite according to the backup lifecycle and restore controls

Key parameters and controls

Storage limitation needs measurable operational controls. A retention policy should include dates, triggers, and accountable roles rather than broad statements such as “retain as necessary.” The following parameters support evidence of compliance.

  • Retention trigger: The event that starts the retention period, such as upload date, completion of anonymization, publication date, or closure of an investigation.
  • Maximum retention period: The approved period for each file category, expressed in days, months, or years where justified by the processing purpose.
  • Deletion service-level objective: The maximum allowed time between the retention deadline and deletion from active systems.
  • Backup expiration: The point at which a deleted source file can no longer be restored from backup media.
  • Review interval: A scheduled check to confirm that the purpose, retention period, and access permissions remain valid.
  • Deletion evidence: Records showing the deletion request, completion status, affected storage location, and responsible system or person. These records should not contain unnecessary personal data.

Source files, anonymization, and deletion

Source files require particular attention because they normally contain the clearest identifiers. If an organization needs original footage only to create and verify a blurred version, it should delete the source file after that work is complete unless another documented purpose or legal obligation requires retention.

Where an organization uses Gallio PRO for offline image or video anonymization, it should define the retention period for imported source files, exported blurred files, and any local working copies. Gallio PRO automatically detects faces and license plates for blurring. It does not automatically detect logos, tattoos, name badges, documents, or content displayed on monitors. These elements may require manual masking in the built-in editor and may affect whether the resulting footage remains identifiable.

A legal claim, regulatory inquiry, or other preservation obligation can justify pausing routine deletion for relevant footage. Such an exception should be limited to the specific files, documented purpose, and required period. It should not become a reason to retain all footage indefinitely.

Storage limitation is a core GDPR principle. Article 5(2) also requires the controller to be able to demonstrate compliance with Article 5(1)(e). Article 25 requires data protection by design and by default, which includes limiting the period of storage. Article 28(3)(g) requires a processor contract to address deletion or return of personal data after processing services end.

US equivalent

The United States has no general federal storage limitation principle equivalent to GDPR Article 5(1)(e). Retention duties are sectoral and state-specific. For example, the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), requires businesses to disclose retention periods or criteria for determining them, while other rules may require preservation for litigation, public records, health care, or education records.

See also