Integration Terms
Policy Owner: Kyriakos Eleftheriou
Last updated: March 6th, 2026
Effective date: March 6th, 2026
PREAMBLEThese Terra Integration Terms ("Integration Terms") govern participation in Terra's integration program. These Integration Terms are entered into between Terra Enabling Developers Inc. ("Terra") and the entity or person submitting an integration application, configuring integration endpoints, or otherwise participating as an integration partner ("Integration Partner").By clicking "I Agree", submitting an integration application, or otherwise participating in the integration program, Integration Partner agrees to these Integration Terms.These Integration Terms are a standalone agreement governing participation in Terra's integration program by integration partners. For clarity, Terra's developer-facing Terms of Service govern developer/customer use of Terra services and do not govern Integration Partners except where expressly stated. Terra's developer-facing Terms are available at https://tryterra.co/terms-of-service and these Integration Terms are available at https://tryterra.co/integration-partner-terms. For integration-partner-specific matters, these Integration Terms control; otherwise Terra's developer-facing Terms control.1. DEFINITIONS1.1 "Integration Data" means data made available by Integration Partner's systems through Integration Partner authorized endpoints, including related metadata.1.2 "Integration Credentials" means OAuth client credentials, secrets, keys, tokens, and similar authentication artifacts supplied by or on behalf of Integration Partner.1.3 "Authorized Developer" means a Terra customer approved by Terra to access relevant data through Terra's services in accordance with applicable Terra terms and policies.1.4 "End User Rights Request" means a request by or on behalf of an end user to access, delete, correct, restrict, or otherwise exercise rights under applicable data protection laws.2. PROGRAM SCOPE2.1 Integration Partner appoints Terra to receive, process, normalize, and transmit Integration Data through Terra's services to Authorized Developers for approved use cases.2.2 Integration Partner participation is subject to Terra's compliance review and approval processes, which Terra may apply, repeat, or update at its discretion.2.3 Terra may suspend, limit, or revoke integration-program access where reasonably necessary for legal, security, compliance, technical, or risk reasons.2.4 Terra may suspend or terminate an Integration Partner's participation where Integration Partner conduct threatens the security, reliability, or integrity of Terra's platform or ecosystem, including misuse of integrations, abusive behavior, or actions that materially affect Terra or other participants.2.5 These Integration Terms apply prospectively from the Effective date and do not apply retroactively to periods before acceptance.3. INTEGRATION PARTNER RESPONSIBILITIESIntegration Partner represents, warrants, and covenants that:3.1 Lawful authority and rights•
Integration Partner has all rights, permissions, and legal authority required to make Integration Data available through Terra and to authorize Terra's processing and distribution as contemplated by these Integration Terms.
3.2 Authorization and consent•
Integration Partner is responsible for its OAuth and authorization experiences and for obtaining and maintaining any notices, consents, authorizations, and legal bases required under applicable law.
3.3 Configuration accuracy•
Integration Partner will provide accurate and complete OAuth endpoints, scopes, credentials, endpoint details, and related technical documentation.
•
Integration Partner will promptly notify Terra of material changes to OAuth, scopes, endpoint behavior, auth methods, or data schemas.
3.4 Security baseline•
Integration Partner will maintain commercially reasonable administrative, technical, and organizational safeguards for its systems and credentials.
•
Integration Partner will not knowingly provide malware, malicious payloads, or unauthorized access vectors via integration endpoints.
3.5 Legal compliance•
Integration Partner is responsible for compliance with laws and regulations applicable to Integration Partner's collection, use, disclosure, and transfer of Integration Data.
3.6 Downstream restrictions and disclosures•
Integration Partner will disclose any integration-specific usage restrictions that Terra must enforce technically or contractually.
3.7 Service continuity; deprecation and access changes•
Integration Partner will not materially reduce, suspend, disable, or discontinue Terra's production access to integration APIs, scopes, or core data endpoints without at least one (1) year prior written notice.
•
Integration Partner will not unilaterally revoke Terra's production credentials or integration access except where required by law, regulator order, or immediate security threat.
•
If emergency action is required, Integration Partner will notify Terra without undue delay and use commercially reasonable efforts to restore access or provide a workable alternative as soon as reasonably practicable.
•
During any planned deprecation period, Integration Partner will maintain backward compatibility or provide a migration path reasonably acceptable to Terra.
4. TERRA RESPONSIBILITIES4.1 Terra will operate the integration, normalization, and delivery services using commercially reasonable care and security practices.4.2 Terra will process Integration Data for the following purposes:•
operating and maintaining Terra's services;
•
authenticating and connecting integrations;
•
ingesting, caching, synchronizing, transforming, normalizing, storing, and transmitting Integration Data;
•
retry logic, reliability mechanisms, troubleshooting, debugging, abuse prevention, security monitoring, compliance, and support;
•
billing/metering and service analytics.
4.3 Terra may use de-identified and/or aggregated data for internal analytics, research, AI/ML development, and product improvement related to Terra's platform and services, provided Terra does not attempt to re-identify end users.4.4 Except as expressly permitted in these Integration Terms, Terra acts solely as infrastructure processing Integration Data on behalf of Integration Partners and/or Authorized Developers and does not independently determine the purposes for processing Integration Data.4.5 Integration Partners remain responsible for determining and maintaining the lawful basis and purposes for processing Integration Data under applicable law.4.6 Terra will maintain a process to receive and action valid Integration Partner rights/security requests as described in Section 6.5. DATA USE, OWNERSHIP, AND LICENSE5.1 As between Terra and Integration Partner, Integration Partner retains rights in Integration Data made available by Integration Partner, subject to rights granted herein.5.2 Integration Partner grants Terra a worldwide, non-exclusive, royalty-free license to use Integration Data as needed to perform the services and rights described in these Integration Terms.5.3 Terra retains all rights in Terra services, software, documentation, tooling, and Terra-generated derivative service outputs (excluding rights in raw Integration Data itself).6. END USER RIGHTS REQUESTS (ALLOCATION)6.1 Intake•
Integration Partner remains responsible for receiving and validating End User Rights Requests directed to Integration Partner, unless otherwise agreed in writing.
6.2 Instruction to Terra•
Where action is required in Terra-controlled systems, Integration Partner will submit a verifiable request through Terra's designated channel/API, including sufficient identifiers.
•
Terra will acknowledge receipt of valid requests promptly.
6.3 Terra action•
Terra will use commercially reasonable efforts to action valid requests in Terra-controlled production systems without undue delay.
•
Where deletion is requested, Terra will delete or irreversibly de-identify applicable records in active systems, subject to legal retention obligations, fraud/security needs, and backup lifecycle limits.
6.4 Confirmation•
Terra will provide status confirmation (received, in-progress, completed, rejected with reason) to Integration Partner.
6.5 Developer propagation•
Terra may notify relevant Authorized Developers where required for downstream completion; each developer remains responsible for actions in developer-controlled systems under their applicable terms.
6.6 Emergency/legal override•
Nothing in this Section limits either party from taking actions required by law, regulator instruction, or urgent security/risk mitigation.
7. SECURITY INCIDENTS7.1 Each party will maintain incident response procedures appropriate to its role.7.2 If a party becomes aware of a confirmed security incident materially affecting data processed under these Integration Terms, that party will notify the other party without undue delay and as required by applicable law, and cooperate in good faith on containment and remediation.8. CONFIDENTIALITYEach party will protect the other party's confidential information using reasonable care and will use such information only for purposes of these Integration Terms, subject to standard exceptions (public domain, independent development, lawful prior possession, compelled disclosure).9. WARRANTIES; DISCLAIMERS9.1 Integration Partner warrants it has authority to provide Integration Data and enter these Integration Terms.9.2 Except as expressly stated, Terra's services are provided "as is" and "as available" to the maximum extent permitted by law.10. INDEMNITY10.1 Integration Partner will defend and indemnify Terra from third-party claims arising from Integration Partner's breach of law, consent/authorization failures, or breach of these Integration Terms.11. LIMITATION OF LIABILITYTo the maximum extent permitted by law, each party's aggregate liability under these Integration Terms is limited to the greater of: (a) amounts paid or payable by Integration Partner to Terra in the 6 months preceding the event; or (b) USD $100, unless otherwise agreed in writing. Neither party is liable for indirect, special, incidental, consequential, punitive, or exemplary damages.12. TERM; TERMINATION12.1 These Integration Terms begin on acceptance and continue until terminated.12.2 Terra may suspend or terminate integration-program participation for breach, legal/compliance risk, or security reasons.12.3 Integration Partner may terminate participation upon one (1) year prior written notice; provided that Integration Partner will continue to honor obligations in Section 3.7 during the notice period and any agreed migration period.12.4 Notwithstanding Section 12.3, Integration Partner may immediately suspend or terminate access where required by law, regulator order, or immediate security threat, with notice to Terra without undue delay.12.5 Upon termination, Terra may cease ingestion/delivery for affected integrations, subject to legal retention and transition obligations.13. CHANGES TO INTEGRATION TERMSTerra may update these Integration Terms by posting updated terms and/or notifying Integration Partner. Updated terms become effective on the date stated in the notice. Continued participation after that date constitutes acceptance, except where explicit re-acceptance is required by law or by Terra policy.14. GOVERNING LAW; DISPUTE RESOLUTIONUnless otherwise agreed in writing, governing law and dispute resolution follow Terra's core terms.15. ACCEPTANCE MECHANICS AND EVIDENCE15.1 Integration Partner acceptance must occur through explicit click acceptance in Terra's integration application flow before an integration application can be submitted.15.2 Terra will maintain acceptance evidence, including accepted terms version, timestamp, and account/user identifier, for as long as reasonably necessary to demonstrate acceptance and comply with applicable law.15.3 If required by law or Terra policy, Terra may require re-acceptance of updated terms before continued integration-program participation.