NICE publishes its standard contract terms online. The NiCE Enterprise Terms and Conditions state that they govern all Transaction Documents, which the terms define as Orders, Schedules, Statements of Work and customer purchase orders.[1] A customer or its Affiliates can buy under them by entering into Transaction Documents with NICE or its Affiliates, and each Transaction Document is treated as a separate contract between the parties to it.[1] For customers who buy through partners, separate End User License Terms apply.[2]
Editions
The terms distinguish three kinds of item a customer can hold. Cloud Services are a subscription-based software-as-a-service offering in a hosted environment, including support. Software is software licensed to the customer on hardware it owns or controls, and the terms say that references to purchasing Software mean purchasing licences to it. Professional Services are consulting, installation, implementation and training services.[1] Software can be bought as a perpetual licence or a term licence: the Invoicing Policy lists both, invoiced 100% in advance from the Delivery Date, with support invoiced 100% in advance and renewed annually.[4] Catalog row: NiCE on-premises Software.
Metrics
For Software, the licence metric is the quantity of licences purchased on the Transaction Document, and the compliance test is whether the quantity of Software licences in use is consistent with that quantity.[3] See Software licence quantity. For cloud services the relevant units are covered in NICE CXone suites and agent licence models and NICE Cognigy AI agents and product-specific terms. The one cross-product unit in the enterprise terms is the Business Unit, an independent, billable software instance of the Cloud Services, within which the customer is responsible for all activity and charges including telephony and network connectivity.[1] See Business Unit.
Counting / floors
Use rights and restrictions
NICE grants a non-exclusive, non-transferable, non-sublicensable right to use the Services or Software, including the Documentation, as set out in a Transaction Document, for the customer’s own internal business purposes.[1] No title or ownership of the Services or Software passes to the customer.[1] The customer may not, and may not allow any user to:[1]
- publish, copy, lease, modify, translate, loan, distribute, resell, transfer, assign, alter or create derivative works of the Services or Software;
- reverse engineer or decompile them, except where statutory law specifically permits (with an EMEA-specific section on interoperability);
- defeat or circumvent any protection mechanism, including mechanisms that limit or control use, copying or access;
- test vulnerability, including scanning or load, stress or penetration testing; or
- use them to service the systems, networks or devices of a third party, for benchmarking, development or competitive purposes, or for any purpose other than as expressly provided.
Using AI or third-party AI to model, replicate or emulate the Services or Software, and training AI technologies with them, is separately prohibited.[1] Any violation of the licence and scope-of-use section is deemed a material breach, and NICE may suspend delivery or terminate immediately without liability.[1] The prohibition on use “on or to service the systems, networks or devices of a third party” is the clause most relevant to outsourcers and managed service providers, who should confirm in the Transaction Document whether service to their own clients is permitted.
Trials and evaluations
NICE may provide trial, evaluation, beta, preview or test-and-development access with limited features and limits on duration, quantity, capacity or environment. Unless a Transaction Document says otherwise, such access carries no support, warranties, service level agreements or indemnification and is provided as is.[1] See Trials, betas and evaluations.
Liability and recovery for over-use
Each party’s aggregate liability is capped at the fees payable or paid in the previous twelve months under the Transaction Document giving rise to the liability, but the cap does not apply to the customer’s payment obligations or to NICE recovering payment for use of the Services or Software in excess of the quantity purchased.[1] The effect is that over-use is recoverable without being limited by the cap.
Virtualization & partitioning
The documents reviewed for this coverage define Software only as software licensed on hardware the customer owns or controls, and do not state separate rules for virtual machines, partitioned servers or hosted deployments of Software.[1] The measure for compliance is the quantity of licences in use against the quantity purchased, not a hardware attribute.[3] Customers deploying NICE Software on virtualised or cloud-hosted infrastructure should therefore confirm the position in the Transaction Document and the product documentation. For the general concept see virtualisation and partitioning.
Cloud / BYOL
The terms do not provide a bring-your-own-licence mechanism for the Cloud Services. For on-premises Software the customer maintains the third-party servers and third-party software used with it, performs routine database maintenance and keeps the physical and virtual security of the Software, and bears the cost of third-party software required for a release, such as Microsoft server or SQL Server licences, and of additional hardware.[3] The customer’s use of third-party products is not licensed by NICE.
Programs
On-premises support term and renewal
Support for Software runs for an initial twelve months from the Delivery Date and renews for additional periods equal to the expiring term. Renewal fees may be increased by the greater of five percent or the most recent annual increase in the CPI-U. At least sixty days before the end of the term either party may give a Non-Renewal Notice, and a customer that gives none is responsible for the full fees for the next term whether or not it issues a purchase order.[3] Updates are available only for the version of, and options included in, the Software originally purchased, if and when they are generally commercially available, and not after termination of the Support Term.[3] Support is subject to a Sunset Policy published on NICE’s self-service portal that sets the lifecycle of Software.[3] See On-premises support term and renewal.
Compliance Verification
The On-Premise Support Policy contains the main audit right in the NICE public terms. On reasonable prior notice, NICE has the right to verify that the customer complies with the licensing terms of the Agreement and that the quantity of Software licences in use is consistent with the quantity purchased under the Transaction Document.[3] The process runs as follows:[3]
- NICE gives reasonable prior notice and provides a NiCE Software script.
- The customer runs the script on the system or systems where the Software is in use.
- Unless otherwise agreed in writing, the customer provides the results report generated by the script within ten days of receiving the script.
- If the report shows use above the licences purchased, NICE invoices the excess number of licences at NICE’s then-current list price for the Software.
- The customer pays within ten days of receiving the invoice.
Three features deserve attention in an audit-readiness review. Verification is a script run by the customer, so the customer controls execution but not the script’s logic. The remedy is purchase of licences at current list price, not at the contracted rate. And the ten-day periods are short. The right is written into the support policy, so it appears to operate while the Software is under support, and its relationship to a customer that has dropped support is not described in the document. See Compliance Verification and the general discussion in software licence audits.
End user terms for partner purchases
The End User License Terms bind customers who buy through partners. They repeat the licence grant for internal business purposes and the restrictions on resale, reverse engineering, circumvention, vulnerability testing, benchmarking and AI replication, and they state that cloud support follows the Cloud Services Terms of Use and Delivery Policy and software support follows the On-Premise Support Policy.[2] A breach of the licence section is a material breach allowing immediate suspension or termination.[2] See End user terms for partner purchases.
Contract mechanics
Governing law and venue follow the NICE entity that signs: for NICE Systems, Inc. or inContact, Inc. the laws and courts of New Jersey; for NICE Systems UK Limited and several European entities English law and courts, with arbitration for some non-UK and non-EU customers; for NICE Ltd. the law and courts of Israel; and other regional rules for Canada, Brazil, Mexico, Australia, Japan and Singapore.[1] Neither party may assign without consent, except that NICE may assign to an Affiliate or to a successor by merger, acquisition or sale of substantially all of its assets.[1] NICE may use the customer’s name and logo for sales and marketing during the term, and the customer can withdraw that authorisation on reasonable notice.[1]
Audits and compliance
Beyond Compliance Verification, NICE relies on the customer’s own monitoring. The terms make the customer responsible for monitoring its and its users’ use of the Services for possible unauthorised usage, for solely responsible activity under its use, and for notifying NICE immediately if it believes the Services are used in an unauthorised manner.[1] For cloud services, usage is metered by NICE for invoicing, and the Invoicing Policy bills variance against the Minimum Commitment.[4] For cloud agent counts, the Configured User and Concurrent User definitions are in the Cloud Services Terms of Use.[5] No court case concerning NICE software licensing or audits was identified in primary court records, so there are no case articles.
Out of scope
This article does not cover data protection terms, the Cloud Services Security Terms, export and sanctions provisions in detail, indemnification mechanics, warranty remedies, EMEA-specific tax provisions, or the product lifecycle documents on NICE’s self-service portal, which are not public. It does not describe NICE Actimize or public safety products.