Openwake · evidence pack

Datadog

https://www.datadoghq.com · record 685 · read 2026-10-20 · rules/v1 · generated 2026-10-23 04:13 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-10-13ff7344a14c2b1628…seq 53147
dpahttps://www.datadoghq.com/legal/data-processing-addendum2026-10-133a49e14dd89bf8c3…seq 53149
subprocessorshttps://www.datadoghq.com/legal/subprocessors/2026-10-206d43127f81667cd2…seq 61332
Ledger proof for this record.
seq 61355 · key 2f898a895f05b7a0 · 2026-10-20T05:26:55.750Z
hash 45dc4964631a6698623441f404f027ee4deacefa62078b4f882b87207cab7038
prev 3e9f89090972da9b34960f69eb7b0a65bcd9190be03420aa722be2af81db7644
payload c81b68580740f7520b256bb57915473a340c5c3a40451a938cef999dd3c9780b
signature /Vvr2L+/NmvPeKPhgYb4bwdGOi0xn3GWfZmTWE6O0E8hI2fwVERVrn3lTxC1hrmVRdnhN3DbOV61VdpJVEORAA==
anchored 2026-10-20 at head seq 61385 90198bd6475ff15c3c045ae583b71db10ee5886294226a625dc412e74fd1ffd3
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.