# 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.

{% hint style="success" %}
Commanders Act do not transfer any of the information collected outside of the European Union, and this applies to all of our solutions.
{% endhint %}

### Server Side

<details>

<summary>Event delivery</summary>

**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:** No

**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

</details>

<details>

<summary>Live events inspector (sources &#x26; destinations)</summary>

**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:** No

**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

</details>

<details>

<summary>Sources Data Quality</summary>

**Type:** Data Collection

**Purpose:** Sampling storage of inbound and outbound hits from server side function

**Personal data:** Yes, depending of customers settings

**Consent required:** No

**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

</details>

### TMS Client Side

<details>

<summary>Container calls</summary>

**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

</details>

<details>

<summary>Deduplication conversions</summary>

**Type:** Data Collection

**Purpose:** Deduplication reporting by conversions

**Personal data:** No

**Consent required:** Yes

**Data retention:** 90 days

</details>

<details>

<summary>Tag Performance</summary>

**Type:** Data Collection

**Purpose:** Performance reporting on the tags embedded in our containers

**Personal data:** No

**Consent required:** No (Anonymous data)

**Data retention:** 30 days

</details>

### Consent

<details>

<summary>Banners displayed &#x26; consents proof</summary>

**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

</details>

<details>

<summary>Cookie Scanner</summary>

**Type:** Data Collection

**Purpose:** Collection of cookies set up on customer website for conformity check

**Personal data:** No

**Consent required:** No (anonymous data)

**Data retention:** 30 days

</details>

### Campaign Analytics

<details>

<summary>Marketing campaigns (views, clicks, conversions &#x26; pages views)</summary>

**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 by default

</details>

<details>

<summary>Customer Journey generation</summary>

**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

</details>

<details>

<summary>Conversion details</summary>

**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.

</details>

### Data Activation

<details>

<summary>Pages views</summary>

**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

</details>

<details>

<summary>Users</summary>

**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

</details>

<details>

<summary>Cookies synchronization</summary>

**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:** 90 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

</details>

<details>

<summary>Conversions</summary>

**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:** 12 months by default

</details>

### Backup (all solutions)

<details>

<summary>Backups</summary>

**Type:** Backup

**Purpose:** Backups of all data stored

**Personal data:** All databases

**Consent required:** Not applicable

**Data retention:** 3 months

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.commandersact.com/configure/data-management/data-retention-duration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
