Data retention duration
Within this page, you will find a detailed information about collected data by our platform, their specific purposes, and their retention duration.
Commanders Act do not transfer any of the information collected outside of the European Union, and this applies to all of our solutions.
Server Side
Event delivery
Type: Data Collection
Purpose: Sampling storage of inbound and outbound hits from server side function
Personal data: Any data necessary for the client's project *IP addresses are automatically obfuscated (the last octet is replaced by 0)
Consent required: Yes
Data retention: 30 days
Collection frequency: 6 requests per minute for each event type *a bonus of 30 request per hour for each event type
Live events inspector (sources & destinations)
Type: Data Collection
Purpose: Sampling storage of inbound and outbound hits from server side function
Personal data: Any data necessary for the client's project *IP addresses are automatically obfuscated (the last octet is replaced by 0)
Consent required: Yes
Data retention: 7 days
Collection frequency: 6 requests per minute for each event type *a bonus of 30 request per hour for each event type
Sources Data Quality
Type: Data Collection
Purpose: Sampling storage of inbound and outbound hits from server side function
Personal data: Yes, depending of customers settings
Consent required: Yes
Data retention: 30 days
Collection frequency: 6 requests per minute for each event type *a bonus of 30 request per hour for each event type
TMS Client Side
Container calls
Type: Data Collection
Purpose: Monitoring of the volume of container calls Generation of TAG invoicing
Personal data: No
Consent required: No
Data retention: 31 days
Deduplication conversions
Type: Data Collection
Purpose: Deduplication reporting by conversions
Personal data: No
Consent required: Yes
Data retention: 90 days
Tag Performance
Type: Data Collection
Purpose: Performance reporting on the tags embedded in our containers
Personal data: No
Consent required: Yes
Data retention: 30 days
One Tag
Type: Data Collection
Purpose: Collecting of online events with possible storage, in order to transfer data to partners or generate user segmentation and exports
Personal data:
ID Unique CA (TC_ID)
IP
User Agent
User ID Any other data necessary for the client's project
Consent required: Yes
Data retention: 30 days
Consent
Banners displayed & consents proof
Type: Data Collection
Purpose: Counting of privacy banner postings and consents. Storage of consents in accordance with legislation
Personal data: Commanders Act uniq ID (TCPID)
Consent required: No
Data retention: 396 days
Cookie Scanner
Type: Data Collection
Purpose: Collection of cookies set up on customer website for conformity check
Personal data: No
Consent required: Yes
Data retention: 30 days
Campaign Analytics
Marketing campaigns (views, clicks, conversions & pages views)
Type: Data Collection
Purpose: Dashboard generation on sales attribution to marketing solutions
Personal data:
Commanders Act uniq ID (TC_ID)
IP
User Agent
Consent required: Yes
Data retention: 90 days
Customer Journey generation
Type: Data Processing
Purpose: Generation of customers journeys from the collected data to be able to constitute the attribution
Personal data: Yes
Consent required: Yes
Data retention: 90 days
Conversion details
Type: Data Processing
Purpose: Storage of conversions with customer journeys
Personal data:
Commanders Act uniq ID (TC_ID)
IP
User Agent
Conversion data
Consent required: Yes
Data retention: 2 years
Additional information: This long retention allows our customers to compare conversion data to previous year.
Exports
Type: Raw or aggregated data exports
Purpose: Export of collected or aggregated data
Personal data:
Commanders Act uniq ID (TC_ID)
IP
User Agent
Consent required: Yes
Data retention:
90 days for raw data
Contract duration for aggregated data.
Imports
Type: Data Processing
Purpose: Importation of campaign or conversion data
Personal data:
Commanders Act uniq ID (TC_ID)
IP
User Agent
Conversion data
Consent required: Yes
Data retention: 2 years
Additional information: This long retention allows our customers to compare conversion data to previous year.
Criteo Graph
Type: Data Processing
Purpose: Identification enhancement using Criteo Ids
Personal data: No
Consent required: Yes
Data retention: 1 year
Data Activation
Pages views
Type: Data Collection
Purpose: Collecting the navigation of Internet users on a website in order to perform profiling
Personal data:
ID Unique CA (TC_ID)
IP
User Agent
User ID Any other data necessary for the client's project
Consent required: Yes
Data retention: 30 days
Users Segmentation
Type: Data Processing
Purpose: Algorithms for the distribution of users in predefined segments
Personal data: No
Consent required: Yes
Data retention: 2 years
Additional information: We consider a user to be inactive after 2 years. This period is set to match the need of some of our customers having long sales cycles
Users Attributes
Type: Data Processing
Purpose: Algorithms for attributes calculations based on existing data
Personal data: No
Consent required: Yes
Data retention: 2 years
Additional information: We consider a user to be inactive after 2 years. This period is set to match the need of some of our customers having long sales cycles
Data Exports
Type: Data Exports
Purpose: Export of data to any destination requested by the customer
Personal data: All collected data is exportable
Consent required: Yes
Data retention:
2 years for users data
30 days for raw events
Additional information: We consider a user to be inactive after 2 years. This period is set to match the need of some of our customers having long sales cycles
Cookies synchronization
Type: Data Collection
Purpose: Correspondence of our IDs with partner IDs
Personal data:
ID Unique CA (TC_ID)
Partners Ids
Consent required: Yes
Data retention: 365 days
Additional information: We consider a user to be inactive after 2 years. This period is set to match the need of some of our customers having long sales cycles
Imports CRM
Type: Data Import
Purpose: CRM data import and reconciliation with collected data
Personal data: Any data necessary for the client's project
Consent required: Yes
Data retention: 3 years
Imports Conversions
Type: Data Import
Purpose: Import of conversion and reconciliation with collected data
Personal data:
Name
first name
email
contact information
Consent required: Yes
Data retention: 3 months
Identity Resolution
User Identification
Type: Data Processing
Purpose: Reconciliation algorithm for multi-device Internet users
Personal data:
ID Unique CA (TC_ID)
IP
User Agent
User ID
Consent required: Yes
Data retention: defined by contract
Backup (all solutions)
Last updated