Telemetry

The NVIDIA NeMo Guardrails library collects anonymous telemetry to help the NVIDIA engineering team understand which deployment patterns and safety features are most widely used. The event payload is transparent and does not contain user content or direct user identifiers such as usernames, API keys, or IP addresses.

After cleaning and aggregation, NVIDIA might share a subset of the data with the community, such as adoption charts that show which built-in safety features are most used. NVIDIA will not share any user content or direct user identifiers such as usernames, API keys, or IP addresses.

Data Collected by Telemetry

The library collects data when you construct LLMRails, IORails, or Guardrails and through periodic heartbeats. The data describes the deployment, not individual requests.

In this context, a session is the lifetime of a single Python process running the NVIDIA NeMo Guardrails library. The library generates the session ID in memory when telemetry starts and does not store it for reuse across process restarts. The same session ID appears in local audit records and transmitted telemetry events so startup and heartbeat events from one process can be correlated. Two guardrails runs by the same user produce two unrelated session IDs.

Possible Values for Built-In Features

Each value corresponds to a directory under nemoguardrails/library/. This list reflects the current release; the directories under nemoguardrails/library/ are the authoritative source.

activefence, ai_defense, autoalign, clavata, cleanlab, content_safety, crowdstrike_aidr, factchecking, fiddler, gliner, guardrails_ai, hallucination, injection_detection, jailbreak_detection, llama_guard, pangea, patronusai, policyai, prompt_security, regex, self_check, sensitive_data_detection, topic_safety, trend_micro.

Data Not Collected by Telemetry

Telemetry excludes the following data from event payloads:

• Model names, model paths, or model parameters
• API keys, endpoints, URLs, or credentials
• Rail definitions, Colang source code, or YAML configuration contents
• Prompts, completions, or any user messages
• Token counts, request latency, or per-request metrics
• File paths, usernames, or IP addresses

The schema is designed to avoid user content and direct user identifiers. Review the audit file to confirm the exact event fields emitted by your local configuration.

Sample Payloads

The following examples show the startup and heartbeat event payloads:

Startup event:

1
{
2
  "sessionId": "2b8e9879-80be-42bb-ad3f-81db8ec28e15",
3
  "nemoguardrailsVersion": "0.22.0",
4
  "pythonVersion": "3.13.7",
5
  "platform": "Linux-5.15.0-x86_64-with-glibc2.35",
6
  "osName": "Linux",
7
  "colangVersion": "1.0",
8
  "llmProviders": ["nim"],
9
  "numRailsConfigured": 4,
10
  "railTypesInUse": ["input", "output"],
11
  "tracingEnabled": false,
12
  "deploymentType": "library",
13
  "nemoSource": "guardrails",
14
  "railsEngine": "LLMRails",
15
  "hasKnowledgeBase": false,
16
  "streamingConfigured": false,
17
  "builtinFeatures": ["content_safety", "jailbreak_detection", "topic_safety"],
18
  "numCustomFlows": 0,
19
  "timestamp": 1775716074.855979,
20
  "event": "startup"
21
}

Heartbeat event (every 10 minutes):

Heartbeat events reuse the startup event metadata and update only event and timestamp; sessionId remains constant for the lifetime of the process.

1
{
2
  "sessionId": "2b8e9879-80be-42bb-ad3f-81db8ec28e15",
3
  "nemoguardrailsVersion": "0.22.0",
4
  "pythonVersion": "3.13.7",
5
  "platform": "Linux-5.15.0-x86_64-with-glibc2.35",
6
  "osName": "Linux",
7
  "colangVersion": "1.0",
8
  "llmProviders": ["nim"],
9
  "numRailsConfigured": 4,
10
  "railTypesInUse": ["input", "output"],
11
  "tracingEnabled": false,
12
  "deploymentType": "library",
13
  "nemoSource": "guardrails",
14
  "railsEngine": "LLMRails",
15
  "hasKnowledgeBase": false,
16
  "streamingConfigured": false,
17
  "builtinFeatures": ["content_safety", "jailbreak_detection", "topic_safety"],
18
  "numCustomFlows": 0,
19
  "timestamp": 1775716674.123456,
20
  "event": "heartbeat"
21
}

Before transmission, the telemetry client wraps each event in the shared NVIDIA telemetry envelope (schema v1.7, protocol v1.6) with nemoSource: "guardrails".

Inspect What Is Sent

The telemetry client attempts to write each outgoing event payload to a local audit file before sending it over the network:

$
cat ~/.config/nemoguardrails/usage_stats.json

The file uses JSON Lines format with one event per line. It rotates when the current file exceeds 10 MB, keeping only usage_stats.json and one usage_stats.json.1 backup, so local audit storage is bounded. It stores the inner event payload, not the full NVIDIA telemetry envelope. Audit writes are best effort. If local audit writing fails, telemetry transmission still proceeds.

Opt Out

Set one of the following options to opt out of telemetry collection:

$
# Product-specific:
$
export NEMO_GUARDRAILS_NO_USAGE_STATS=1
$
$
# Industry standard:
$
export DO_NOT_TRACK=1
$
$
# File-based:
$
mkdir -p ~/.config/nemoguardrails && touch ~/.config/nemoguardrails/do_not_track

When any opt-out is active, the library does not start the heartbeat daemon thread, does not write to the audit file, and does not make any network requests.

Set the opt-out before the NVIDIA NeMo Guardrails library starts. Changing environment variables or creating do_not_track after telemetry has started does not stop an already-running heartbeat thread.

Automatic Suppression in Test and CI Environments

The telemetry client also disables telemetry automatically, with no configuration required, when either of the following environment variables is set:

• CI (truthy: 1 or true). Set by GitHub Actions, GitLab CI, CircleCI, Travis, Buildkite, and most other CI runners. Honoring this is the same convention used by Homebrew, npm, conda, and others.
• PYTEST_CURRENT_TEST. Set by pytest while a test is running. Suppresses telemetry from your test suite even outside CI.

This behavior keeps adoption metrics focused on real deployments, not synthetic test or CI traffic. If you genuinely want telemetry from a CI run, unset CI for that step.

Schema and Source Code

The Python source for the event lives in nemoguardrails/telemetry.py. The wire contract is validated against a vendored snapshot of the shared NVIDIA telemetry schema at schemas/anonymous_events.snapshot.json. The conformance test in tests/telemetry/test_usage_reporting.py validates emitted payloads against that snapshot with jsonschema.