Telemetry and Privacy | NVIDIA NeMo Platform

NeMo Platform and its bundled library plugins include optional anonymous telemetry to help NVIDIA improve reliability, usability, and product direction. No user content, credentials, prompts, model outputs, file contents, or personally identifiable information is collected by these telemetry events.

You can opt out at any time. When you run components through NeMo Platform, the platform telemetry controls are the recommended broad opt-out for the CLI and bundled plugins that share this telemetry system. When you use a library standalone, configure telemetry separately for that library.

Opting out of NeMo telemetry does not affect data collection by inference endpoints you separately configure, such as NVIDIA Build, OpenRouter, or local model servers. Those endpoints are governed by their own terms and privacy practices.

What Is Collected

All telemetry is operational or configuration-level. Telemetry event payloads do not include user inputs, file contents, model responses, user identifiers, device fingerprints, hostnames, or machine-derived identifiers.

Component	Identifier	Data collected
NeMo Platform	Random session identifier stored in local platform state and rotated every 30 days. If the state file has no creation date, an invalid creation date, or an expired creation date, NeMo Platform creates a new identifier.	Session identifier; onboarding step name, outcome, and invocation method; CLI command name, duration, and outcome; job type, duration, plugin references, model-data present/absent bucket, and token counts when available; CI flag; coding-agent flag; package version; CPU architecture.
Anonymizer	Per-session rotating identifier, not persistent across sessions.	Job-level operational metrics, such as final run status, processing time, record counts, token counts, configuration parameters, deployment type, and model endpoint information.
Data Designer	Per-session rotating identifier, not persistent across sessions.	Model names used and input/output token counts.
Guardrails	Per-session rotating identifier, not persistent across sessions.	Configuration and environment metrics, such as library version, Python version, operating system, Colang version, LLM engine names, rail configuration, active features, and deployment context.
Safe Synthesizer	Per-session rotating identifier, not persistent across sessions.	Run-level operational metrics, such as final run status, processing time, record counts, token counts, configuration parameters, top-level quality and privacy scores, base model, deployment type, and GPU type.

Aggregate data, such as model usage distribution and total token counts, may be shared publicly with the community. Telemetry is used to prioritize product improvements, not to track individual users.

Opt Out

NeMo Platform

Disable NeMo Platform telemetry with any one of these controls:

$ export NEMO_TELEMETRY_ENABLED=false

1 telemetry_enabled: false

$ nemo --no-telemetry workspaces list

The environment variable disables telemetry for the CLI and bundled plugins that share the platform telemetry controls. The configuration file setting telemetry_enabled: false goes in ~/.config/nmp/config.yaml. The --no-telemetry flag disables telemetry for one CLI invocation.

For CLI-specific behavior, see CLI configuration.

Data Designer

When you use Data Designer through NeMo Platform, use the platform controls above. For standalone library usage, configure telemetry using the standalone Data Designer library’s documented opt-out controls.

Anonymizer

When you use Anonymizer through NeMo Platform, use the platform controls above. Standalone Anonymizer configs can disable telemetry with the emit_telemetry field:

1 from anonymizer.config.anonymizer_config import AnonymizerConfig
2 from anonymizer.config.replace_strategies import Redact
3 
4 config = AnonymizerConfig(replace=Redact(), emit_telemetry=False)

Safe Synthesizer

When you use Safe Synthesizer through NeMo Platform, use the platform controls above. Standalone Safe Synthesizer configs can disable telemetry with the emit_telemetry field:

1 emit_telemetry: false

Guardrails

Set any one of the following before the Guardrails library starts:

$ export NEMO_GUARDRAILS_NO_USAGE_STATS=1

$ export DO_NOT_TRACK=1

$ mkdir -p ~/.config/nemoguardrails
$ touch ~/.config/nemoguardrails/do_not_track

Changing the environment variable or creating the do_not_track marker after the library has started does not stop an already-running heartbeat thread.

Third-Party Endpoints

NeMo Platform and bundled library plugins can use third-party inference endpoints such as NVIDIA Build, OpenRouter, or local model servers. If you configure one of these endpoints:

That endpoint’s terms of service and privacy practices apply independently of NeMo Platform.
NeMo telemetry opt-out controls do not extend to data collection by your chosen inference endpoint.
NVIDIA Build is intended for evaluation and testing only and may not be used in production environments. Do not submit confidential information or personal data when using NVIDIA Build.