Sub-processors
Alynrex Pte. Ltd. · UEN 202207417W · Last updated 2026-08-24
Draft — not yet reviewed
This document has not been reviewed by a qualified lawyer. It describes how the platform actually works and is published so prospective customers can see our intended terms early. It is not yet an offer, and it should not be relied on for a procurement or compliance decision. Ask us for the reviewed version before signing anything.
This list forms part of the Data Processing Addendum. It names every third party that processes customer data on our behalf.
Customer workloads and the data they process run on infrastructure located in Indonesia, under Indonesian jurisdiction.
1. Current sub-processors
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Stripe, Inc. | Payment processing, invoicing and tax identification | Billing name, email, business name, tax ID, payment method (held by Stripe; never stored by us) | United States, with EU/UK/SG affiliates |
| Upstream model providers | Serving inference requests for models not hosted in-region | Prompt and completion content for calls routed to that provider Only applies to models the catalog marks as not in-region. A key restricted to in-region models never reaches these. | Varies by provider; disclosed per model in the console catalog |
Infrastructure we operate ourselves is not listed here — a sub-processor is a third party, and the campus is ours.
2. A note on inference
The second entry needs more than a table cell, because whether it applies to you is your choice rather than ours.
The model catalog states, for every model, an explicit jurisdiction and whether it is served in-region. That value is recorded by an operator; it is never inferred from the model's name or its provider.
- Calling a model marked in-region involves no third-party sub-processor. The prompt and completion do not leave the region.
- Calling a model marked not in-region transmits the prompt and the completion to that model's upstream provider, outside the region. The console names the provider before you call it.
An inference key can be restricted to in-region models. A key so restricted cannot reach an out-of-region model, whatever the calling code asks for — so where your data must not leave the region, this is the control to use rather than a policy telling your engineers which model names to avoid.
3. Notice of changes
We give at least 30 days' notice before adding or replacing a sub-processor.Ask us to be added to the notification list and we will email you when this page changes.
If you reasonably object to a new sub-processor on data protection grounds, section 5 of the DPA sets out what happens next.
Questions about this document? Contact us.