Criteo
No tracked subprocessors.
Documents
| Document | Verified | Changed | Evidence |
|---|---|---|---|
| Trust center | snapshot | ||
| Subprocessor list | snapshot | ||
| Data processing addendum | snapshot | ||
| Privacy policy | snapshot | ||
| Terms | snapshot | ||
| Security page | snapshot | ||
| security.txt | snapshot | ||
| Status page statuspage | snapshot |
Subprocessors
None extracted.
Listed as a subprocessor by (1)
Purposes as each company states them.
Next Millennium Media nextmillennium.com
Service status
- 10 incidents in 80 days
- 3 major or critical
- 5 h 8 min typical time to resolve
- 2 days longest major
| Began | Incident | Impact | Lasted |
|---|---|---|---|
| Data Processing Delays - Reporting Tools Affected | minor | 4 h 25 min | |
| Users may have trouble accessing Criteo reporting API component | major | 2 days | |
| Users may have trouble accessing Commerce Max Analytics UI | major | 3 h 39 min | |
| Data Processing Delays - Reporting Tools Affected | minor | 8 h 8 min | |
| Users may have trouble accessing Criteo UI and APIs. | minor | 24 min | |
| Data Processing Delays - Sales metrics Affected | minor | 10 h 4 min | |
| Users in Australia may have trouble with Commerce Max and/or Commerce Yield component performance | minor | 31 min | |
| Data Processing Delays - Sales metrics Affected | minor | 22 h 44 min |
As Criteo's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)
Changes
None since tracking began.