Enterprise Data Processing Addendum

Last updated: October 2026

1. Purpose

This page summarizes how enterprise customers can establish enhanced data-processing terms with IteraCompute. The executed Data Processing Addendum ("DPA") attached to your signed service agreement prevails over this summary and over the public Privacy Policy where they differ.

2. Roles and scope

For enterprise API services, the customer acts as data controller for Interaction Data and IteraCompute acts as processor, processing only to deliver the contracted services, on documented customer instructions, and as required by applicable law. Processing details (subject matter, duration, data types, data-subject categories) are set out in the executed DPA order form.

3. Zero data retention (ZDR)

Enterprise ZDR — including scope (for example designated models or endpoints), logging exclusions, cache behavior and legally required exceptions — must be established through a written agreement and technical configuration review. Absent an executed ZDR schedule, standard retention and logging described in the Privacy Policy applies.

4. Security and subprocessors

We apply the technical and organizational controls described on our Security page, with enterprise-specific measures (for example IP allowlists, key scoping, additional audit support) agreed per contract. Enterprise subprocessors and any region-specific processing commitments are listed in the executed DPA; changes follow the notice process in that DPA.

5. Audits, incidents and assistance

The executed DPA sets out audit cooperation, security-incident notification timeframes, data-subject-request assistance, return-or-deletion on termination, and cross-border or outsourcing formalities required by applicable law. To request a DPA, contact partnerships@iteracompute.com with your company, workload and compliance requirements.