Openwake · evidence pack

Datadog

https://www.datadoghq.com · record 231 · read 2026-09-06 · rules/v1 · generated 2026-09-06 04:02 UTC

Facts

Trains on customer data
unclear
No supporting text found in the documents read.
privacy policy · https://www.datadoghq.com/legal/privacy/ · confidence 0.20
Opt-out mechanism
We will not process your personal information for purposes materially different from the above without providing you with the opportunity to opt out.
“We will not process your personal information for purposes materially different from the above without providing you with the opportunity to opt out.”
privacy policy · https://www.datadoghq.com/legal/privacy/ · confidence 0.50
AI features
none stated
No supporting text found in the documents read.
privacy policy · https://www.datadoghq.com/legal/privacy/ · confidence 0.20
Model providers named
OpenAI
“* OpenAI * SAP Monitoring * OpenTelemetry Use Case”
subprocessors · https://www.datadoghq.com/legal/subprocessors/ · confidence 0.60
Retention
not stated
No supporting text found in the documents read.
privacy policy · https://www.datadoghq.com/legal/privacy/ · confidence 0.20
Hosting regions
not stated
No supporting text found in the documents read.
privacy policy · https://www.datadoghq.com/legal/privacy/ · confidence 0.20
Subprocessor notice
30 days
“Datadog will update the Subprocessors List at least 30 days before appointing a new Subprocessor and will provide Customer with a mechanism to receive notifications of new Subprocessors (a “Change Notice”), which today is available through the Subprocessors List.”

Subprocessors (6)

NameCategoryLocationQuoted from
Amazon Web Serviceshyperscalerunstated
“* Amazon Web Services Monitoring * Azure Monitoring * Google Cloud Monitoring”
Microsoft Azurehyperscalerunstated
“* Azure Monitoring * Google Cloud Monitoring * Oracle Cloud Monitoring”
Google Cloudhyperscalerunstated
“* Google Cloud Monitoring * Oracle Cloud Monitoring * Kubernetes Monitoring”
Oracle Cloudhyperscalerunstated
“* Oracle Cloud Monitoring * Kubernetes Monitoring * Red Hat OpenShift”
OpenAImodel providerunstated
“* OpenAI * SAP Monitoring * OpenTelemetry Use Case”
SAPotherunstated
“* SAP Monitoring * OpenTelemetry Use Case * Application Security”

Sources read

DocumentURLReadContent hashLedger
privacy_policyhttps://www.datadoghq.com/legal/privacy/2026-09-06f5ba8cd110c14841…seq 445
subprocessorshttps://www.datadoghq.com/legal/subprocessors/2026-09-06ff6fa269084f93d1…seq 446
dpahttps://www.datadoghq.com/legal/data-processing-addendum2026-09-062b413317b4d21a14…seq 447
Ledger proof for this record.
seq 502 · key 2f898a895f05b7a0 · 2026-09-06T01:40:51.147Z
hash a4e5d2cfc1fabda1a629ef2660f835114bdbacffcead3786c23c2be6face365c
prev b54ba8ad2e02f1282f87556a12b9d4b2cd93397ae43aba1853cf6d899c62ca9e
payload e8ccc1870cfb5471b686458a2ee8e96ed074b9e86a90790cfa9dd81c023012ea
signature o4FdHmBYYrgtc9dtPi2PZV2gvoMj0cavhmH7hYzCSnvMXLj/CLGGxnuRuV8quHPzs8FbnyWBrkUBPznYDu3GAw==
anchored 2026-09-06 at head seq 564 231a9dea0f93915bd7110e6786e00908325db3031635ace53c1023f850e0c49c
Fetch /v1/keys; for each ledger entry recompute sha256(prev_hash|kind|ref_id|payload_hash|created_at ISO) and verify the Ed25519 signature over that hash. Anchors are committed to git; compare the anchored head with the chain.