Third Party Integrations. Customer acknowledges and agrees to only use Third Party Integrations if;
a) Customer has a BAA or related agreements in place with the Third Party Service Provider consistent under The Regulations, or;
b) Third Party Service Provider publicly announces HIPAA compliance in all the services provided, or;
c) Jotform announces HIPAA Compliant Integration with Third Party Service.
Third Party Integrations. Customer may enable integrations between the Entrust Technology and certain third-party services contracted by Customer (each, a “Third-Party Integration”). By enabling a Third-Party Integration between the Entrust Technology and any such third-party services, Customer is expressly instructing Entrust to share all Authentication Records, Customer Data, Profiles, Personal Data, and/or Service Data, necessary to facilitate the Third-Party Integration. Customer is responsible for providing any and all instructions to such third part services provider about the use and protection of such Authentication Records, Customer Data, Profiles, Personal Data, and/or Service Data. Customer acknowledges and agrees that Entrust is not a sub-processor for any such third-party services providers in relation to any Personal Data contained in the aforementioned data or information, nor are any such third-party services providers sub-processors of Entrust in relation to any Personal Data contained in the aforementioned data or information.
Third Party Integrations. The Services may contain features designed to interoperate with applications or services you contract directly with third-parties to receive. Any: (a) operation or transaction completed via any integration with such a third-party service is between you and the relevant third party, and not Us;
Third Party Integrations. The Subscription Service and Legacy Software may allow you to access, integrate, acquire, or interact with Third-Party Integrations, including integrations that may allow you to store or transmit Customer Content. We do not license any intellectual property to you as part of Third-Party Integrations and we are not responsible or liable to you or others for information or services provided by any third party unless otherwise expressly stated in an Order. You should review the third-party terms and privacy policies before acquiring, using, requesting, or linking the Subscription Service or Legacy Software to Third-Party Integrations; further, any such third-party terms do not modify this Agreement.
Third Party Integrations. Any problems resulting from Client’s combining or merging the Subscription Service with any hardware or software not supplied by us or not identified by us in writing as compatible with the Subscription Service;
Third Party Integrations. In executing its services, GLO may leverage third-party platforms, tools, or services. The functionality, availability, and terms of these third-party offerings are beyond the Agency's control, and GLO is not responsible for any changes, disruptions, or issues arising from them.
Third Party Integrations. 14.1 The Applications may integrate with third-party hardware and software providers, and in some instances, allow End User to use third-party integrations to connect the Applications to End User’s system(s), as applicable. Some of the third-party software is essential to the core operation, for example operating systems and databases. Other third-party software is needed to implement. Sangoma will not support integration to third-party hardware or software that is no longer supported by the respective vendor. Sangoma will also not support third-party hardware or software that is not directly used in the Application, as such, but can be used as tools that support the general use of the Application, for example, Microsoft Excel or Google Sheets.
14.2 Many third-party software and service providers do not follow strict software lifecycle policies where changes to their application programming interfaces (“APIs”) are announced. This applies to, for example, Facebook and Google. Sangoma follows updates to applicable APIs and will update Applications to comply with updates as quickly as possible, as appropriate. However, Sangoma is not responsible for any limitations, thresholds, bugs, or the like in such third-party APIs.
14.3 End User acknowledges and agrees that when using the following third-party integrations in conjunction with the Applications, the applicable terms of services apply: (1) Google APIs are governed by the Google APIs Terms of Service found at xxxxxxxxxx.xxxxxx.xxx/xxxxx; (2) Dropbox APIs are governed by the Dropbox Developer Terms and Conditions found at xxxxxxx.xxx/xxxxxxxxxx/xxxxxxxxx/xxx; and (3) Atlassian Connect, Jira Cloud Platform, Atlassian OpenAPI, Xxxxxx API, and Confluence Cloud using Connect are governed by the Atlassian Developer Terms found at xxxxxxxxx.xxxxxxxxx.xxx/xxxxxxxx/xxxxxxxxxxx/xxxxxxxxx-xxxxxxxxx-xxxxx/. Other APIs may become available and additional terms posted to this website.
Third Party Integrations. 25.1 Where any part of the Services requires input form a Third Party Supplier, the Supplier will provide support as deemed necessary by the Supplier in accordance with this agreement.
25.2 If the Customer requires the Hosting Service or use of the Payment Gateway, such services shall commence on the date that the Customer accepts the Supplier’s Quotation in respect of each of those services (the Effective Date). The agreement to use the Hosting Service or Payment Gateway shall be for a minimum period of 12 months (Initial Term), after which time it shall continue for consecutive 12 month rolling periods unless terminated by the Customer giving no less than 3 months’ notice prior to each anniversary of the Initial Term Date.
25.3 Where the Hosting Service is terminated in accordance with clause 25.2, the Customer shall be responsible for any costs associated with the local installation of the Software.
Third Party Integrations. If a third-party application integrates or accesses data into the Delphi custom object in SFDC (vs. a SFDC object) (“Third Party Integration”), Amadeus certification is required for such Third Party Integration.
Third Party Integrations. The 2Ring Service may integrate with third party products or services (each, a “Third Party Product”) through APIs made available by the owner of such Third Party Products (“Third Party APIs”). 2Ring makes no representations or warranties regarding the performance or suitability of any such Third Party Products or Third Party APIs for Subscriber’s intended requirements or purposes, including for use with the 2Ring Service or Subscriber’s systems or networks. Further, 2Ring makes no representations or warranties regarding the security or integrity of data transmitted, transferred, stored, obtained or received through any such Third Party Products or Third Party APIs. 2Ring is not responsible for any disclosure, modification or deletion of Subscriber Content resulting from access by any Third Party Product. 2Ring is not obligated to maintain or support any Third Party Products or Third Party APIs, or to provide Subscriber with updates, fixes, or services on the 2Ring Service related to any Third Party Products or Third Party APIs, or any changes made by any third party to such Third Party Products, Third Party APIs, or Subscriber Content. 2Ring makes no representations or warranties regarding the availability, functionality, or any changes to the features or specifications, of any Third Party Products or Third Party APIs. Subscriber assumes all risk arising from the use of any Third Party Products or Third Party APIs, including the risk of damage to Subscriber’s computer system, software, the corruption or loss of data, and compliance with all applicable laws and regulations (such as, but not limited to, the laws and regulations related to privacy and data protection).
