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
  • Activate the processing freshness option
  • Disable the processing freshness option
  • Freshness indicators
  • Mark as fresh
  • Important information about how freshness works
  • Notifications

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

  1. Features
  2. Record of processing activities

Processing freshness

Learn how to activate and use the processing freshness option

Dernière mise à jour il y a 1 an

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

The freshness of a processing is an indicator of when it was last updated. Freshness will decrease as the expiry date of the processing approaches. This feature is a simple and fun way of ensuring that the information in your record of processings is always up to date.

Activate the processing freshness option

Processing freshness is optional and deactivated by default.

To activate the option, go to your record of processings, click on the action selector for the "New data processing" button and then on "Enable processings freshness".

This action is reserved for your workspace administrators.

The following window appears, giving you the option of setting the expiry interval for your processing. The freshness of a processing corresponds to the number of days between the last date on which the processing was marked as fresh and the expiry date of the processing.

The expiry date is a date in the future calculated from the last date on which the processing was marked as fresh, to which we add the expiry interval. Please note that this expiry interval will be the same for all processing in your register.

A second option allows you to mark all the processing in your register as fresh when you activate the option (this will start a freshness cycle for all the processing in the register immediately).

Example: Today is 04/07/2023, I activate the freshness of processing option in my record of processings and set an expiry interval of 1 month. I tick the option "set all of your processings as fresh as of today" and validate. The expiry date for my processing is calculated as 04/08/2023 (last date on which my processing was marked fresh, 04/07/2023, to which we add the expiry interval, 1 month). I reconnect on 15/07/2023, and my processing still has 20 days of freshness left (the difference between the expiry date and today's date).

Disable the processing freshness option

To deactivate the option, go to your record of processings, click on the action selector for the "New data processing" button and then on "Disable processing freshness option".

This action is reserved for your workspace administrators. Each processing will retain the last date on which it was marked as fresh if you decide to reactivate the option in the future.

Freshness indicators

Once the option has been activated, you will find freshness indicators for your processing in several places. Please note that freshness is only displayed for published processings that have been marked as fresh at least once (either when the option is activated via the "mark all your processings as fresh as of today" selector, or manually in a processing record).

In the right-hand menu of your processing record

You will find the freshness indicator in the top right-hand corner of your processing record (provided that the processing has been published and marked as fresh at least once). This indicator consists of a label with the values "Fresh", "Relatively fresh" and "Expired", a colour (green, yellow and red respectively), a progress bar that decreases as the expiry date approaches, a button for marking the processing as fresh and the number of days remaining or overdue in relation to the expiry date.

In the freshness column of your processing register

By displaying the freshness column in the list view of your processing register, you can find the indicator for each processing record that meets the display conditions (published processing with at least one date on which it was identified as fresh).

Mark as fresh

You can decide to refresh a processing at any time, without necessarily waiting for the expiry date.

To do this, click on "mark as fresh" to display the window for refreshing a processing (in mobile display, this window can be accessed by clicking on the leaf freshness icon):

By marking the processing as fresh, you will restart a freshness cycle from today's date until the next expiry date. The expiry date is calculated by default according to the freshness policy of your workspace (freshness interval applied when the processing freshness option is activated). You can decide to ignore this default date and apply a specific expiry date to this processing by ticking the "Change expiry date" option and selecting a new date (the expiry date must be at least D+1).

Important information about how freshness works

Please note that we treat the date on which a processing record is updated (when the record is saved, for example) independently of the date on which a processing was identified as fresh. It is therefore necessary to click on "mark as fresh" to (re)initialise the freshness date of a processing record.

Notifications

The owner of a processing that has become outdated will receive a warning email to remind them that one of their treatments has not been reviewed for a long time and that it is time to refresh it.

⚙️
In mobile view, you will also find this indicator in the navigation bar at the top of your processing record.