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 page describes what the document states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability may vary by jurisdiction. Methodology
“Customer may create a Custom TTS Application for their own use but cannot offer it as a service to third parties or distribute it as part of a Customer Product as described in Section 1.1.2.”
“NVIDIA DGX Software is only licensed for use in DGX Systems. Firmware licensed for specific DGX Systems may not be used in other products.”
“Software offered as part of the developer program is not for use, distribution or deployment in production. Customer will not include developer program Software in a Customer Product.”
“If Customer obtains a personal use license for Enterprise Products through the NVIDIA developer program, Customer may exercise the Section 1.1.1 grants for Software designated and updated by NVIDIA from time to time, solely for internal evaluation, development or testing for non-production purposes.”
“Customer may not use the Software or any of its components for the purpose of emotion recognition.”
“offer as a service the Software, Derivative Samples and Derivative Models as part of a Customer Product on infrastructure Customer owns or leases”
This document sets out the rules for how you can and cannot use NVIDIA NIM software. You can build things with it and offer them as a service through your own products, but you cannot use developer-program software in production, deploy it in shared commercial systems, or use any part of it for emotion recognition. NVIDIA may collect telemetry data from NIM containers, but you can turn that collection off by setting an environment variable.
This document establishes the acceptable use conditions under which NVIDIA NIM licenses its Software, defining permitted and prohibited deployment contexts, hardware restrictions, and data practices. Customers may offer the Software, Derivative Samples, and Derivative Models as a service within a Customer Product on owned or leased infrastructure, but developer-program Software is confined strictly to internal, non-production evaluation and testing. The document imposes absolute prohibitions on emotion recognition use and multi-user commercial deployments, restricts proprietary components such as CUDA toolkit, TensorRT, cuDNN, NVIDIA drivers, and NVIDIA Omniverse to systems with NVIDIA Platforms, and limits DGX Software and firmware to designated DGX Systems. NVIDIA NIM collects telemetry data in NIM container releases for product configuration, optimization, and improvement, and retains a right to request periodic usage reporting from customers no more than monthly.
For an individual user or customer, this document means that the Software comes with firm boundaries: developer-program Software is for internal testing only and cannot be shipped in a product or run in production, and no use of the Software—or any component—for emotion recognition is permitted under any circumstances. NVIDIA may ask you to report which software your personnel and end users are using, up to once a month by email. Telemetry data is collected in NIM container releases; you can disable this collection by setting the environment variable NIM_TELEMETRY_MODE=0.
Which mapped governance frameworks each document engages, tied to the specific provisions that engage them.
We withheld clauses we had published from this document. Each withholding is recorded in our correction log:
“Customer may create a Custom TTS Application for their own use but cannot offer it as a service to third parties or distribute it as part of a Customer Product as described in Section 1.1.2.”
“If Customer obtains a personal use license for Enterprise Products through the NVIDIA developer program, Customer may exercise the Section 1.1.1 grants for Software designated and updated by NVIDIA from time to time, solely for internal evaluation, development or testing …”
“Software offered as part of the developer program is not for use, distribution or deployment in production. Customer will not include developer program Software in a Customer Product.”
“NVIDIA DGX Software is only licensed for use in DGX Systems. Firmware licensed for specific DGX Systems may not be used in other products.”
“Customer may not use the Software or any of its components for the purpose of emotion recognition.”
“offer as a service the Software, Derivative Samples and Derivative Models as part of a Customer Product on infrastructure Customer owns or leases”
“not used in a commercial kiosk, server or other system used to service multiple users.”
“The following proprietary Software components are licensed solely to run on systems with NVIDIA Platforms: (a) NVIDIA software development kits (such as CUDA toolkit, TensorRT, cuDNN), (b) NVIDIA drivers, and (c) NVIDIA Omniverse.”
“If you obtain a Subscription specifically for one of these platforms, your license is restricted to use solely on that particular platform, NVIDIA or an authorized reseller or distributor may invoice you for the difference in fees...”
“Customer must report upon NVIDIA's email request, no more than monthly, the Software in use by Customer Personnel and Customer End Users Customer enabled, quantity, start and end dates, and any other reasonably required information...”
“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.”
“Customer can disable telemetry collection by setting the environment variable NIM_TELEMETRY_MODE=0 and enable telemetry collection by setting NIM_TELEMETRY_MODE=1.”
Every distinct legal provision identified in this document. Featured provisions appear above with analysis.
We have not recorded a change to this document since we began capturing it. Monitor includes same-day alerts, structured change summaries, and monitoring for up to 20 platforms.
Need provision-level monitoring and regulatory mapping? Insight includes governance timelines, drift analysis, and full provision tracking.
Cross-platform context
See how other platforms handle Custom TTS Third-Party Service Prohibition and similar clauses.
Compare across platforms →Governance Monitoring
Structured alerts for policy changes, governance events, and provision updates across 352+ platforms.