DASTRA
English
English
  • What is Dastra
  • 🇪🇺USEFUL REMINDERS
    • What is GDPR ?
    • GDPR key concepts
      • Personal data
      • Record of processing activities (ROPA)
      • Privacy impact assessment
      • Data retention period
      • Data Subject Rights (DSR)
      • Privacy by design and by default
      • Security measures
      • Data breach notifications
    • Risk management
      • Definition of risks
      • Risk assessment
      • Vendor risk management
  • 🧑‍🎓GETTING STARTED
    • Setting up
      • Create and set up a workspace
      • Create and set up organizational units
      • Appointing a DPO
      • Add a lead authority
      • Invite users
      • Managing roles and permissions
      • Create and assign teams
      • Frequently asked questions
    • Tutorial
      • Step 1: Setting up
      • Step 2: Map your personal data processing and draw up a register
      • Step 3: Managing risks
      • Step 4: Prioritize actions
      • Step 5: Implement internal processes
      • Step 6: Document compliance
    • Support
      • The dastronaut's assistant
      • Online help
      • Request support
      • The customer support process
  • ⚙️Features
    • Dashboard
    • General
      • Advanced Filters
      • Import your data (Excel, Csv)
      • Tag management
      • Custom fields
      • AI Assistant
      • Email templates
    • Data Mapping
    • Record of processing activities
      • "Data controller" record
      • "Data processor" record
      • Establish your record
      • Export / import the record
      • Use a processing activity template
      • Declare a processing activity
      • Complete a data processing activity
        • General information
        • Stakeholders
        • Purposes
        • Dataset
        • Assets
        • Data subjects
        • Data subjects rights (DSR)
        • Recipients
          • Data transfers outside the EU
        • Security measures
        • Impact analysis
        • Documentation
      • Create relationships between processing activities
      • Processing freshness
      • Share the record of processing
      • Data visualization
        • View the treatment tree
        • View the record data map
        • View the transfers map
      • Frequently asked questions
    • Audits and DPIA
      • Create or modify an audit template or DPIA
      • Scheduling an audit or a PIA
      • Share an audit report or PIA
      • FAQ
    • Privacy hubs
      • Create a Privacy hub
      • Configure your Privacy hub
        • Homepage and general configuration
        • Questionnaires
        • Data subject requests
        • Record of processing activities
        • Attachments
        • Organizational chart
        • Contacts
        • Security
        • Appearance and design
      • Preview and share your privacy hub
      • Collecting data processing projects from a Privacy hub.
    • Contracts
      • Declare a Contract
      • Structure of a contract
      • Documents
      • Assets
      • Signers
      • Linked users
      • Sign the contract
      • Docusign integration
      • Contract versions
      • Contract templates
    • Risk management
      • Glossary of terms
      • Risk management process
        • 1. Identification
        • 2. Assess
        • 3. Monitor
        • 4. Control
        • Let's recap
      • Dastra / eBios RM comparison
      • Attach a risk to a processing activity
      • FAQ
    • Planning
      • Create your action plan
      • Create or modify a project or an iteration
      • Monitor, screen or export your tasks
      • Customise the task workflow
      • Share as calendar
      • Customise the task workflow
      • Go further with planning
      • FAQ
    • Data subject right request
      • Manage data subject right requests
      • Set up a data subject right request widget
      • Technical integration
      • API integration
    • Manage data breach notifications
      • Report a data breach
      • Export your data breach notifications
    • Manage cookies consent
      • Widget configuration
        • Preliminary study
        • Cookies scanning
        • Classify cookies by consent categories
        • The purposes of cookies
        • Implement a cookie consent widget
        • Collect proof of cookie consent
        • Go further on cookie consent
        • In case of unavailability
      • Technical integration
        • Functioning of the widget
        • Quick start
          • Wordpress
        • Language management
        • Test the integration of a widget
        • Blocking cookies
          • Blocking iframes (twitter/youtube...)
          • Google Tag Manager
        • Advanced Design
        • Manage consent programmatically
        • User identification
        • Mobile applications
          • Hybrid applications
          • Native applications
        • TCF 1.1/2.0
      • RGAA compliance
      • Breakdown service
    • Regular review (freshness)
    • Custom Reporting
      • Integration with data analysis tools (BI)
    • AI Systems
      • Establishing a record of AI systems
      • Risk analysis and business value
      • Transparency notice
      • AI Models repository
    • Advanced configuration
      • SCIM
      • Roles and permissions
      • Single Sign On (SSO)
        • SAML 2
        • OpenId
        • ADFS
        • Active Directory
        • Okta
        • Known problems
      • References
      • API key management
      • Notifications
      • Workflow steps / process flow
      • Incoming mail data collection
      • OneDrive/Google Drive integrations
      • Webhooks
      • SMTP configuration
      • Workflow rules
      • Message templates
      • Email domains
  • PARTNERS
    • Portal
  • 📄API documentation
    • Configuration
    • Authentication
    • API References
    • Integrations
      • Frequently asked questions
  • 🛡️Security
    • Security at Dastra
    • Security roadmap
    • Quality of Service
  • Certifications
  • 🤖Other
    • FAQ
    • Known problems
    • Changelog
  • Referentials
    • CNIL referentials
      • HR referential from CNIL
Propulsé par GitBook
Sur cette page
  • Definition of retention periods
  • The data life cycle
  • How to determine them?
  • Where to find the references? (in France)
  • Who is involved?
  • How to control?
  • For more information

Cet article vous a-t-il été utile ?

  1. USEFUL REMINDERS
  2. GDPR key concepts

Data retention period

Learn what shelf life is.

Dernière mise à jour il y a 1 an

Cet article vous a-t-il été utile ?

Definition of retention periods

Retention periods are one of the fundamental principles of personal data protection.

The principle of limited retention periods enshrines the right of individuals to be forgotten.

An obligation resulting from Article 5 of the GDPR:

  • Identifiable form

    • Personal data may be retained in a directly or indirectly identifying form indefinitely by organizations within certain limits.

  • Necessary for the purposes

    • Data must be processed for a limited period of time, in a manner consistent with the objective pursued (i.e. the purpose).

A requirement for documentation in the record provided for in Article 30 of the GDPR:

An obligation to provide information to data subjects under Articles 13 and 14 of the GDPR:

It is thus necessary to determine :

  • A fixed retention period, according to the life cycle of the data.

  • An objective criterion used to determine this duration.

The data life cycle

The data life cycle can be broken down into three stages:

  • The record in which the processing activities and the related retention periods must appear;

  • A reference document centralizing, for example in the form of a table, the duration of the different phases of the data's life for each processing operation (the SIAF's recommendations can be included, if necessary, in the structure's internal archive management tables);

  • The different actions undertaken, including if these actions are still in progress;

  • The written instructions given to the subcontractor regarding time limits;

  • The possible procedures for archiving data, and in particular in the case of compulsory payment for the definitive archiving of public records (payment slip, etc.);

  • The procedure for the destruction of data, if applicable (e.g.: disposal slip, etc.);

  • Authorization management policy and authorization matrix for archiving, etc.

With Dastra, enter the different life cycles of the data and adapt the retention periods to each dataset created.

How to determine them?

By applying the data protection principle from the outset:

  • Define precisely the purpose, i.e. what the personal data will be used for;

  • The different life cycles of this data, the applicable time periods, and the data concerned;

  • Identify the people who will need to process the data during current use, and those in case of intermediate storage;

  • Ensure traceability of access to archived data;

  • Provide for an automatic and selective data purge procedure (for public records, this purge is subject to the authorization of the person responsible for scientific and technical control);

  • If an anonymization process is contemplated, ensure that the data will not allow the data subjects to be "re-identified" at the end of the process.

Where to find the references? (in France)

  • Rely on legal or regulatory provisions

  • The deliberations of the CNIL

  • For public archives, the recommendations of the Archives de France

  • Sector-specific references

If no text or standard provides solutions, it's necessary to determine the duration best suited to the purpose of the processing in accordance with the principle of responsibility.

Who is involved?

  • The department in charge of implementing the processing (which may be a subcontractor) will provide all the elements needed to understand its needs and, thus, to determine the period of current use of the data concerned;

  • The Data Protection Officer (DPO) is the privileged interlocutor when he/she has been appointed; he/she is in charge of ensuring the compliance of the processing implemented within the structure, as well as of advising the data controller;

  • The organization's internal archive, if any, can provide insight into data retention practices for the treatment in question (data life cycle management, etc.);

  • An advisor, whether internal to the structure (e.g. a company's legal department), or external (e.g. a lawyer, a digital services company, etc.). The latter can, in particular, help to target the possible applicable legislative or regulatory provisions;

  • The professional federation to which the data controller belongs can provide support to its network in determining retention periods.

In the public sector (for public structures and for private organizations responsible for a public service mission), the contacts to be favored are the territorially competent departmental archives service (for decentralized services and local authorities and their groupings), or the archives mission of the ministry in charge (for central administration services). These contacts can inform the organization about the obligations that apply to it, and guide it in their implementation (determination of the time limit and final disposition).

How to control?

The practical implementation of retention periods must be checked regularly. Regular audits are therefore necessary. The DPO has the task of controlling the processing operations including the retention periods.

Dastra's Audit feature is ideal for this:

For more information

The (in French) provides clarification on the documentation to be provided on retention periods:

🇪🇺
French CNIL guide on retention periods
Audits and DPIA
Dataset
Planning
Excerpt from Article 5 of the GDPR
Excerpt from Article 30 of the GDPR
Excerpt from Article 13 and 14 of the GDPR
The data life cycle