Common use of Developer’s Clause in Contracts

Developer’s. User, its employees, and any party approved by Honeywell in writing in accordance with this Section, accessing the DevTools on User’s behalf (collectively, “Developers”) may exercise the Dev Rights, provided that, User must bind them to this Agreement and User is responsible and liable for its Developers’ compliance with this Agreement, including any of their acts and omissions. User authorization credentials for access the DevTools will be assigned only by Honeywell for use by Developers. Once User’s authorization credentials are assigned, User is responsible to ensure the following is in place within its organization to manage Developer access and use of the DevTools: (a) User must create unique ClientIDs for Developer access to the DevTools, ensure access is only enabled through the authorization DevTools License Agreement v_1.0 credentials and its ClientIDs, and maintain confidentiality and secrecy of such credentials; (b) ensure log-in credentials are secured and only accessed and used by Developers within User’s authorized and authenticated company systems; (c) only create and share authorized credentials with User employees who have a need to know; (d) maintain logs and management tools to confirm each Developer is in compliance with all credentialed access; and (e) immediately discontinue and delete any log-in credentials and passwords once a Developer no longer needs or is permitted to have access, including upon a DevTool termination or suspension. User shall not share any authorization credentials with any third party except to Developers who are contractors with Honeywell’s prior written approval who are bound in writing to maintain the secrecy of the authorization credentials and to access and use the same solely to perform work for User. In the event the authorization credentials become lost, stolen, or compromised by any known or unknown means, User shall immediately contact ▇▇▇▇▇▇▇▇▇ and follow the instructions provided by Honeywell to invalidate the impacted authorization credentials. User is responsible to follow all DevTools set up and use requirements in accordance with Honeywell’s data sheets and documentation, including using only one set of keys per a single application, not embedding keys in source code or repositories, confirming the key rotation policy is followed, and deleting keys when no longer in use. Honeywell also recommends that User add expiration dates to its credentials and keys for more robust security. User and Developers understand and agree that Honeywell is unable to retrieve expired credentials. User may not resell Dev Rights or permit third parties (except affiliates or User third-party Developer contractors as provided in this section) to be Developers or make copies of the DevTools (except for single use back up purposes) except as agreed by Honeywell in writing. Honeywell has no responsibility with respect to actions or inactions of User or Developers.

Developer’s. UserBuyer, its employees, and any party approved by Honeywell in writing in accordance with this Section, accessing the DevTools on UserBuyer’s behalf (collectively, “Developers”) may exercise the Dev Rights, provided that, User Buyer must bind them to this Agreement and User Buyer is responsible and liable for its Developers’ Developer compliance with this Agreement, including any of their acts and omissions. User Buyer authorization credentials for access the DevTools will be assigned only by Honeywell for use by Developers. Once UserBuyer’s authorization credentials are assigned, User Buyer is responsible to ensure the following is in place within its organization to manage Developer access and use of the DevTools: (a) User Buyer must create unique ClientIDs for Developer access to the DevTools, ensure access is only enabled through the authorization DevTools License Agreement v_1.0 credentials and its ClientIDs, and maintain confidentiality and secrecy of such credentials; (b) ensure log-in credentials are secured and only accessed and used by Developers within UserBuyer’s authorized and authenticated company systems; (c) only create and share authorized credentials with User Buyer employees who have a need to know; (d) maintain logs and management tools to confirm each Developer is in compliance with all credentialed access; and (e) immediately discontinue and delete any log-in credentials and passwords once a Developer no longer needs or is permitted to have access, including upon a DevTool termination or suspension. User Buyer shall not share any authorization credentials with any third party except to contractor Developers who are contractors with Honeywell’s prior written approval who are bound in writing to maintain the secrecy of the authorization credentials and to access and use the same solely to perform work for UserBuyer. In the event the authorization credentials become lost, stolen, or compromised by any known or unknown means, User shall immediately contact ▇▇▇▇▇▇▇▇▇ and follow the instructions provided by Honeywell to invalidate the impacted authorization credentials. User is responsible to follow all DevTools set up and use requirements in accordance with Honeywell’s data sheets and documentation, including using only one set of keys per a single application, not embedding keys in source code or repositories, confirming the key rotation policy is followed, and deleting keys when no longer in use. Honeywell also recommends that User add expiration dates to its credentials and keys for more robust security. User and Developers understand and agree that Honeywell is unable to retrieve expired credentials. User may not resell Dev Rights or permit third parties (except affiliates or User third-party Developer contractors as provided in this section) to be Developers or make copies of the DevTools (except for single use back up purposes) except as agreed by Honeywell in writing. Honeywell has no responsibility with respect to actions or inactions of User or Developers.known