Invocation of Disabling Code Clause Samples
The 'Invocation of Disabling Code' clause defines the conditions under which certain software code or features can be intentionally deactivated or rendered inoperative. Typically, this clause outlines the mechanisms by which a party—often the software provider—may trigger disabling code, such as through remote commands or upon the occurrence of specific events like license expiration or breach of contract. For example, if a customer fails to pay for continued use, the provider may invoke code that disables access to the software. The core function of this clause is to provide a clear legal and technical basis for disabling software in specified circumstances, thereby protecting the provider’s rights and ensuring compliance with licensing terms.
Invocation of Disabling Code. In addition to the invocation of disabling code when HGST has received Licensee’s consent described in Section 7.1, HGST may, at its option, invoke disabling code in HGST’s Software without receiving Licensee’s consent (i) if in HGST’s sole, reasonable discretion, HGST believes that such Software has been, is being or will be used in violation of laws; (ii) if HGST is required to do so, because of a court or regulatory order; (iii) if Licensee has not paid the applicable License Fee by the expiration of the Software trial period; or (iv) if Licensee has used the Software other than as authorized by Licensee’s license. HGST shall have no liability to Licensee for any good faith invocation of any such disabling code.
Invocation of Disabling Code. Notwithstanding anything to the contrary, ▇▇▇▇▇▇▇▇▇▇ may invoke the disabling code without Customer’s consent if (i) Cellebrite reasonably believes that such Software has been, is being, or will be used in violation of Laws; (ii) Cellebrite is required to do so because of a court or regulatory order; (iii) Customer has not paid an outstanding invoice more than sixty (60) days after such invoice is due, or; (iv) Customer has used the Software other than as authorized by Customer’s license. Cellebrite shall have no liability to Customer for any good faith invocation of any such disabling code.
Invocation of Disabling Code. In addition to the invocation of disabling code when Cellebrite has received ▇▇▇▇▇’s consent described in Section 9.A, Cellebrite may, at its option, invoke disabling code in Cellebrite’s Software without receiving Buyer’s consent: (i) if in Cellebrite’s sole, reasonable discretion, Cellebrite believes that such Software has been, is being or will be used in violation of Laws; (ii) if Cellebrite is required to do so, because of a court or regulatory order;
Invocation of Disabling Code. In addition to the invocation of disabling code when Cellebrite has received the Customer’s consent described in Section ▇.▇, ▇▇▇▇▇▇▇▇▇▇ may, at its option, invoke disabling code in Cellebrite’s Software without receiving the Customer’s consent:
(i) if in Cellebrite’s sole, reasonable discretion, Cellebrite believes that such Software has been, is being or will be used in violation of any applicable Law; (ii) if Cellebrite is required to do so, because of a court or regulatory order; (iii) if the Customer has not paid an outstanding invoice more than sixty (60) days after such invoice is due; or (iv) if the Customer has used any Software other than as authorized by the Customer’s license, including if a Product is removed from the Secure Room in which such Product is licensed to be used. Cellebrite shall have no liability to the Customer for any good faith invocation of any such disabling code.