NIM containers may collect telemetry data including microservice settings, usage data, and hardware environment information for product configuration and improvement purposes; customers can disable this collection by setting an environment variable.
This analysis describes what NVIDIA NIM's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision discloses that NIM container deployments may collect operational and hardware telemetry data, and requires customers to affirmatively configure environment variables to disable collection. The opt-out mechanism is technical rather than UI-based, meaning it requires developer-level access to implement, which is relevant for enterprise compliance workflows.
Interpretive note: The document does not explicitly state whether NIM container telemetry is enabled or disabled by default for all releases, creating uncertainty about the default data collection posture that customers must verify per container.
The agreement discloses that NIM containers may collect microservice settings, usage data, and hardware environment data; under these terms, collection is enabled by default unless customers set the environment variable NIM_TELEMETRY_MODE=0 in their deployment configuration.
Cross-platform context
See how other platforms handle NIM Container Telemetry Collection and Opt-Out and similar clauses.
Compare across platforms →"Customer acknowledges that NIM container releases that collect data, collect it for the following purposes: (a) to properly configure and optimize products for use with Software; and (b) to improve NVIDIA products and services. NIM containers that collect telemetry will have environment variables to enable or disable data collection. When enabled with telemetry mode, telemetry information collected includes: (i) microservice settings, (ii) usage data and (iii) hardware environment. Customer can disable telemetry collection by setting the environment variable NIM_TELEMETRY_MODE=0 and enable telemetry collection by setting NIM_TELEMETRY_MODE=1.Excerpt from NVIDIA NIM's NVIDIA AI Foundation Models AUP
(1) REGULATORY LANDSCAPE: The collection of usage data and hardware environment information from enterprise deployments engages GDPR data minimization and transparency principles for EU/EEA customers, and CCPA disclosure requirements for California-based customers.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision discloses that NIM container deployments may collect operational and hardware telemetry data, and requires customers to affirmatively configure environment variables to disable collection. The opt-out mechanism is technical rather than UI-based, meaning it requires developer-level access to implement, which is relevant for enterprise compliance workflows.
The agreement discloses that NIM containers may collect microservice settings, usage data, and hardware environment data; under these terms, collection is enabled by default unless customers set the environment variable NIM_TELEMETRY_MODE=0 in their deployment configuration.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by NVIDIA NIM.