Last updated: March 13, 2026

Data Processing Addendum

TrexAPI can make a Data Processing Addendum (“DPA”) available upon request for eligible business customers who require contractual data-processing terms in connection with the Services.

This page is an overview only and does not itself constitute a signed DPA. If you need a DPA, contact us and we will review the request based on your account, use case, and commercial arrangement.

1. Availability

A DPA may be available upon request for enterprise customers, private deployment customers, and other qualifying business users where data-processing terms are reasonably required.

2. What a DPA Typically Covers

Where applicable, a DPA may address topics such as:

  • roles of customer and TrexAPI in data processing;
  • documented processing instructions;
  • confidentiality obligations;
  • security controls and organizational measures;
  • subprocessor use and management;
  • cross-border data transfer safeguards where applicable;
  • incident notification and cooperation;
  • deletion or return of data where contractually required.

3. Scope and Limits

Any DPA is limited to the actual Services and account configuration covered by the underlying agreement.

A DPA does not automatically grant:

  • enterprise features not otherwise purchased;
  • private deployment rights unless separately contracted;
  • custom data residency, encryption, or isolation terms unless expressly agreed;
  • changes to product behavior outside the signed commercial arrangement.

4. Customer Responsibilities

Customers remain responsible for:

  • determining whether TrexAPI is appropriate for their use case;
  • ensuring they have the right to submit and process content through the Services;
  • configuring their own applications and credential flows appropriately;
  • meeting their own obligations to end users, regulators, and third parties.

5. How to Request a DPA

To request a DPA, contact [email protected] or your TrexAPI commercial contact and include:

  • your company name;
  • the email address associated with your account;
  • your expected use case;
  • whether you need enterprise or private deployment terms;
  • any timing or procurement constraints.

6. Review Process

We may review the request based on account status, use case, deployment model, security needs, and the commercial arrangement requested. In some cases, additional onboarding or a separate commercial agreement may be required before a DPA is provided.

7. Contact

For DPA requests or privacy-related commercial questions, contact:

ClawDiary

Email: [email protected]