Developer Terms

Last Modified: July 17th 2026

We are excited that you have chosen to develop with EDMISS Developer Tools. These tools allow you to build amazing Apps and integrations. When you develop using the EDMISS Developer Tools, you agree to be bound by these Terms, so please read them carefully.

  1. Relationship With Other Terms And Definitions

1.1 Relationship With The Agreement

These Developer Terms apply whenever You access or use the EDMISS Developer Tools and form part of the Agreement between You and Us.

Capitalised terms not defined in these Developer Terms have the meanings given in the EDMISS Customer Terms of Service.

You are responsible for all access to and use of the Developer Tools under Your account, including use by Your personnel, contractors, developers, Apps, AI Systems and External Services.

If there is an inconsistency between these Developer Terms and the Customer Terms, these Developer Terms prevail in relation to access to and technical use of the Developer Tools, and the Customer Terms prevail in all other respects.

1.2 Definitions

In these Developer Terms:

“Customer Terms” means the EDMISS Customer Terms of Service.

“Access Credentials” means any API key, access token, client secret, password or other credential used to access the Developer Tools.

“AI System” means any artificial intelligence, machine-learning, generative AI, large-language-model, automated decision-making system, AI agent, assistant or related service.

“App” means any application, software, integration, automation, workflow or other service that accesses or uses the Developer Tools.

“Customer-Configured Integration” means any App, workflow, automation or integration configured, directed or controlled by You or on Your behalf, including a workflow using a connector or integration made available by Us.

“Customer Data” has the meaning given in the Customer Terms.

“Data Protection Requirements” means all privacy, data-protection, cybersecurity, data-breach-notification and electronic-communications laws applicable to You, Your Apps, External Services or the relevant Customer Data.

“Developer Tools” means the APIs, Access Credentials, documentation, connectors, development environments and other developer or integration resources made available by Us.

“External Service” means any third-party application, platform, integration, automation, data-storage service, AI System, data processor or other service connected to, accessed through or used with the Developer Tools by or on Your behalf.

“Security Incident” means any actual or reasonably suspected unauthorised access to, acquisition, use, disclosure, loss, alteration or destruction of Customer Data.

  1. Access to our APIs

2.1 Your Apps

Subject to the restrictions below, We grant You a non-exclusive, worldwide, non-transferable, limited license to access our APIs and documentation only as necessary to develop, test and support an integration of Your Apps with the Subscription Service.

Without limiting your express obligations in these Terms, you are solely responsible, at your own expense, for how you develop, configure, operate, secure and support your Apps and External Services, and for your relationships with end users and third-party providers.

2.2 The Rules

Your license to access our APIs and documentation is limited and subject to compliance with the EDMISS Customer Terms of Service. Further, You will not: (A) access our APIs or documentation in violation of any law or regulation; (B) access our APIs in any manner that (i) compromises, breaks or circumvents any of our technical processes or security measures associated with the Services, (ii) poses a security vulnerability to customers or users of the Services, or (iii) tests the vulnerability of our systems or networks; (C) access our APIs or documentation in order to replicate or compete with the Subscription Services; (D) attempt to reverse engineer or otherwise derive source code, trade secrets, or know-how of our APIs or Services; or (E) attempt to use our APIs in a manner that exceeds rate limits, or constitutes excessive or abusive usage.

2.3 Rate Limits

Use of the Developer Tools is subject to the rate limits, usage allowances and other technical limits applicable to Your subscription plan. These limits may vary depending on Your subscription plan, licensed users, enabled services, integrations and any additional capacity purchased by You.

Your applicable limits will be specified in Your subscription plan, order form or other documentation made available by Us. If there is an inconsistency, Your order form prevails.

If You exceed an applicable limit, We may throttle, restrict or temporarily suspend the affected access until usage returns within the applicable limits.

We may apply reasonable technical limits where necessary to protect the security, availability, performance or integrity of the EDMISS Services. Where reasonably practicable, We will notify You before making a material reduction to an existing contracted limit.

You may contact Us if You require additional capacity. Additional usage or increased limits may be subject to approval and additional fees.

2.4 Our Right to Suspend Access and Audit

If We reasonably believe that an App or Your use of the Developer Tools breaches the Agreement, We may require You to modify the App, remedy the breach or suspend the relevant activity.

We may immediately restrict, suspend or revoke access to the Developer Tools where You do not respond within a reasonable period or where We reasonably believe that continued access creates a credible privacy, security, legal or operational risk to Us, the EDMISS Services, Customers, users or any third party.

We may audit an App or request reasonable information and evidence to verify compliance with the Agreement. You must reasonably cooperate with the audit or inquiry and provide the information and evidence requested by Us.

2.5 Access Credentials

Once We have activated Your access to the Developer Tools, We will provide You with Access Credentials.

You are responsible for all activities carried out using Your Access Credentials.

You must keep Access Credentials secure and must not sell, transfer, sublicense or disclose them except to Your authorised personnel who require access and are bound by appropriate confidentiality and security obligations.

You may authorise an External Service using an authentication method supported by Us, including a scoped integration token, where permitted by the Agreement. You must not provide an External Service with usernames, passwords or other Access Credentials except through such a supported authentication method.

You must promptly revoke affected Access Credentials and notify Us if You know or reasonably suspect that any Access Credentials have been lost, compromised or used without authorisation.

  1. Your Responsibilities

3.1 Responsibility for Apps and External Services

You are solely responsible, at Your own expense, for the development, configuration, operation, security, support and use of Your Apps and External Services.

You are responsible for determining what Customer Data is accessed, exported, transmitted, disclosed, stored or otherwise processed through Your Apps or External Services, the purposes for which it is processed and the recipients of that Customer Data.

You must ensure that each such access, use, disclosure and transfer is authorised by You and complies with applicable Data Protection Requirements and Your agreements with the relevant individuals and organisations.

3.2 Protection of Customer Data

You must implement and maintain appropriate technical and organisational measures to protect all Customer Data accessed, received, transmitted, stored or otherwise processed through Your Apps or External Services against accidental, unlawful or unauthorised destruction, loss, alteration, access, disclosure or use. These measures must be appropriate to the nature, volume and sensitivity of the Customer Data and the risks presented by the processing.

You must manage and protect all Access Credentials in accordance with clause 2.5.

3.3 Third-Party Processors and Recipients

Before permitting any third party to access, receive, store or otherwise process Customer Data through the Developer Tools, You must carry out appropriate due diligence and ensure that the third party is bound by an enforceable written agreement that requires it to:

(a) process Customer Data only for authorised purposes and in accordance with applicable Data Protection Requirements;
(b) maintain privacy, confidentiality and security protections that are no less protective than those required of You under these Terms;
(c) restrict access to authorised personnel who are subject to appropriate confidentiality obligations;
(d) implement appropriate technical and organisational security measures;
(e) notify You without undue delay of any actual or suspected unauthorised access, use or disclosure of Customer Data; and
(f) impose equivalent obligations on any further subcontractors or subprocessors it engages in connection with Customer Data.

You remain responsible for the acts and omissions of Your External Services, third-party processors, recipients and subprocessors in connection with Customer Data and Your use of the Developer Tools.

3.4 International Transfers

You must ensure that any international transfer of Customer Data through Your Apps or External Services complies with applicable Data Protection Requirements, including any requirements relating to the destination, transfer mechanism, contractual safeguards and notices or consents.

3.5 Privacy Notices and User Terms

If You make Your Apps available to persons outside Your organisation, You must maintain a user agreement and privacy policy that are prominently available to users. They must accurately and clearly describe the collection, use, storage, disclosure, international transfer and sharing of Customer Data through Your Apps and External Services.

3.6 Security Incidents and Cooperation

You must notify Us without undue delay at support@equatorit.com if You become aware of a Security Incident that impacts, or is reasonably likely to impact, the Subscription Service, Customer Data obtained through the Developer Tools, or EDMISS customers or users. You must promptly provide reasonable information and cooperation requested by Us in connection with the incident.

You must comply with any reasonable technical standards, support processes and instructions that We provide from time to time. You must also provide satisfactory responses within 7 calendar days to complaints made to Us about Your Apps or use of the Developer Tools.

3.7 AI Systems and Customer-Configured Integrations

You must not configure or permit an AI System to access Customer Data unless:

(a) You have approved the purpose, data categories, functionality, recipients and processing locations involved;
(b) access is restricted to the minimum Customer Data and functionality reasonably required for the approved purpose;
(c) appropriate authentication, access controls, monitoring and audit logging are maintained;
(d) the AI System provider is bound by enforceable obligations meeting the applicable privacy, confidentiality, security, incident-notification and subprocessor requirements in clause 3.3; and
(e) the use complies with the Customer Terms and all applicable Data Protection Requirements.

You must not permit an AI System provider to use Customer Data, prompts, responses or derived information to train or improve a general-purpose model, or for advertising, profiling or an unrelated purpose, unless expressly authorised by You in writing and permitted under the Agreement and applicable law.

You must maintain meaningful human oversight where an AI System can modify Customer Data, communicate with individuals, or take actions that may significantly affect an individual.

We may restrict or suspend an AI System or Customer-Configured Integration where We reasonably believe it creates a privacy, security, legal or operational risk.

The availability of an API, connector or integration through EDMISS does not mean that We have approved or control Your configuration, data destinations or subsequent use of Customer Data. You remain responsible for those matters under these Developer Terms and the Customer Terms.

3.8 Ending Access

Upon suspension, expiry or termination of Your access to the Developer Tools, You must immediately stop using the affected Developer Tools and Access Credentials and disable any affected Apps, AI Systems and External Services.

You remain responsible for Customer Data previously transferred to or processed by Your Apps, AI Systems and External Services. You must ensure that such Customer Data is retained, returned or securely deleted in accordance with the Customer Terms, applicable Data Protection Requirements and Your agreements with the relevant third-party providers.

On request, You must provide reasonable information confirming that access has ceased and that the affected Access Credentials have been revoked.

  1. Intellectual Property Rights and Additional Terms

4.1 Reservation of Rights

You retain Your ownership rights in Your Apps and we own and will continue to own our APIs, documentation and Services, including all related intellectual property rights therein. All of our rights not expressly granted by the Agreement are hereby retained.

4.2 EDMISS Independent Development

You understand and acknowledge that We may be independently creating (or may receive from third parties) features, applications, content, or other products or services that may be similar to or competitive with Your Apps, and nothing in these Terms will be construed as restricting or preventing Us from doing so. In addition, in order to allow others to benefit from the Developer Tools, You agree not to assert (or assist or encourage anyone in asserting) any patent claims against EDMISS (or its users, or Affiliates, or Customers) where such patent claim relates to the integration, combination or interface of any applications, products or services with the EDMISS Service or our other products or services.

4.3 Modifications to our APIs and Documentation

EDMISS is still evolving, and so we need the flexibility to occasionally make changes to our APIs, including backwards incompatible changes. We will try to give notice of these changes, but you should consider viewing our changelogs for updates. Also, parts of our API are undocumented, including certain methods, events, and properties. Given that these undocumented aspects of our APIs may change at any time, you should not rely on their behaviours.

  1. Disclaimer of Warranties

EXCEPT AS EXPRESSLY PROVIDED IN THE AGREEMENT AND TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE APIS, DOCUMENTATION AND ALL RELATED COMPONENTS AND INFORMATION ARE PROVIDED BY US ON AN “AS IS” AND “AS AVAILABLE” BASIS WITHOUT ANY WARRANTIES OF ANY KIND, AND WE EXPRESSLY DISCLAIM ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. YOU ACKNOWLEDGE THAT WE DO NOT WARRANT THAT THE APIS WILL BE UNINTERRUPTED, TIMELY, SECURE, OR ERROR-FREE.