Subprocessors

1. How we use subprocessors

We engage the following categories of subprocessors to operate self-service accounts, billing and support. Providers act only on our instructions under contractual confidentiality and data-protection duties. Interaction Data (prompts and outputs) is processed on infrastructure we operate in mainland China and is not sent to the account, auth or billing providers below for model training.

2. Current categories

• Console hosting and account services: hosts platform.iteracompute.com sign-up, sign-in, account management and API-key issuance; processes account data and auth events.
• Third-party sign-in (OAuth, where offered): GitHub / Google or similar providers share basic profile data (account ID, email, name, avatar) at your direction for authentication only.
• Payment processing and invoicing: processes transactions and invoices; receives billing contact, amounts and limited card metadata (brand, last four digits, expiry). Full card numbers are handled by the payment provider only.
• Support ticketing and communications: processes support requests and contact correspondence you send to us.
• Service monitoring and logging infrastructure: processes API metadata, error logs and service-status data for billing, security, abuse prevention and operations.

3. Updates

We will update this page when we add or replace subprocessor categories for self-service offerings. Enterprise customers with signed agreements will be notified of material changes through the channels agreed in their service agreement. Specific vendor names are disclosed on request or in enterprise security review, subject to confidentiality.