A1. Roles.
For customer content processed to provide the service, the customer is the controller and Inferock is the processor, acting only on the customer's documented instructions (these terms, the customer's configuration, and the product's normal operation are the instructions). For Inferock Watch, inference executes against the customer's own provider key; Inferock does not act as controller of that content.
A2. Scope, purpose, duration.
Purpose: operate the platform (routing, tenant key management, usage/ billing metering, support). Duration: the term of the account plus the retention windows in Part B. Processing is limited to what the service requires; no independent use of customer content.
A3. Data categories + data subjects.
Categories: account/identity data (email, tenant identifiers, auth), inference request/response content the customer submits, usage/metering records. Data subjects: the customer's own users and whoever the customer includes in inference content. What Inferock keeps from that content is set out in What we see and keep on a call. The customer must not submit special-category data it is not authorized to process.
A4. Sub-processors (extends base §3).
The customer authorizes Inferock to engage sub-processors for hosting, model inference through Inferock Serve or Inferock Dedicated, and operational tooling. Inferock (i) maintains a current sub-processor list available on request, (ii) imposes data-protection terms no less protective than these on each sub-processor (flow-down), and (iii) gives notice of a material change or a new sub-processor with a reasonable objection window before it takes effect. Inferock Serve and Inferock Dedicated inference content is routed to the model-hosting sub-processor on a de-identified basis per base §3 (account identifiers + customer metadata stripped; not used to train the partner's models; not retained by the partner beyond serving the request).
A5. Security measures.
Access is tenant-scoped with server-side tenant authorization; provider keys and secrets are held encrypted at rest; transport is encrypted (TLS); least-privilege operational access; audit logging of privileged actions; old-key revocation on rotation.
A6. Data-subject-rights assistance.
Inferock assists the customer, taking into account the nature of processing, to respond to data-subject access, correction, deletion, and portability requests through the export and deletion request processes in Part B, plus reasonable support for requests those processes do not cover.
A7. Personal-data breach notification.
On becoming aware of a personal-data breach affecting customer content, Inferock notifies the affected customer without undue delay (in-house target: within 72 hours of confirmation) with the known nature, scope, likely consequences, and mitigation, per the Part B incident process.
A8. Deletion / return on termination.
On account closure or on the customer's written request, Inferock deletes or returns customer content per the Part B deletion process, subject to any copies the law requires be retained; backups age out on the Part B backup cycle.
A9. Audit / information.
Inferock makes available the information reasonably necessary to demonstrate compliance with this DPA and, on reasonable notice and confidentiality, supports a proportionate audit (documented responses / a walkthrough by default; on-site only where genuinely required and scheduled).
A10. International transfers.
Where content crosses borders to a sub-processor, the transfer rides the sub-processor's own lawful-transfer basis and the flow-down in A4; the de-identification in A4 limits what is transferred.
A11. Liability.
DPA liability follows the main terms' limitation and cap; the SLA service credit (base §2) is the exclusive remedy for availability.