Datadog

The reviewed policy does not provide a simple no-AI-training promise for all telemetry and event data.

Datadog uses collected information to improve existing products and create new ones.

Datadog publishes privacy-policy coverage for monitoring services and account data.

Admins can control what telemetry is ingested in the first place through instrumentation and scrubbing choices.

Datadog supports access and configuration controls that can narrow which users see collected telemetry.

Telemetry can still flow through integrations, cloud providers, subprocessors, organization users, and legal disclosures.

Marketing, analytics, and social-sharing features widen the sharing surface beyond core monitoring.

Datadog documents privacy rights and service-provider handling.

Admins can govern access, archives, and integrations for observability data.

Datadog documents account-management and rights-request paths for personal information.

Security-focused processing is clearly called out instead of being hidden in vague operational language.

Analytics and observability tools can collect identifiers, events, session replays, logs, traces, device data, and usage metadata.

Teams can reduce exposure with masking, consent mode, sampling, log scrubbing, retention controls, and restricted access.

Retention still depends on product, plan, archive settings, backups, and legal needs.

Observability exports and integrations can preserve copies of telemetry outside the main workspace lifecycle.

Retention can be configured by product and plan for many telemetry types.

Admins can manage archives and access in ways that affect how long sensitive telemetry remains easily available.

Datadog says it keeps personal information only as long as necessary, then deletes or archives it unless there is a lawful reason to retain it.

Rights-request and access paths are documented.

Admins can manage data scrubbing, access, retention, archives, and integrations.

Customers can update account information, access rights, and portability requests.

Instrumentation hygiene lets teams decide what sensitive data never enters Datadog.

Security contact and abuse-report paths are clearly documented.

Privacy still depends on whether teams scrub sensitive data before sending it.

End-user visibility into collected telemetry is much weaker than administrator control.