Data Processing Addendum
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 addendum forms part of the Terms of Service between you ("Controller") and Alynrex Pte. Ltd. ("Processor") and applies whenever you process personal data through the platform.
Where you require a signed copy on your own paper, ask us.
1. Roles
You are the controller of the personal data your workloads process. You decide what data enters the platform and why. We do not see into your workloads and have no independent purpose for their contents.
We are the processor of that data, acting on your documented instructions.
Separately, we are the controller of your account and billing data — your email, your invoices, your audit trail. That is governed by the Privacy Policy, not this addendum. The line matters: your audit trail is ours to keep because we need it to run and secure the platform, and it is not deleted on your instruction the way your content is.
2. Scope and instructions
Your use of the platform is your instruction to us. We process personal data only to provide the service, and for no other purpose. We do not use it to train models, to build profiles, or to improve the service beyond what operating it requires.
We will tell you if, in our opinion, an instruction infringes applicable data protection law. If we are legally required to process beyond your instructions, we will tell you before doing so unless the law forbids that notice.
Annex A sets out the subject matter, duration, nature, purpose, data types and data subjects.
3. Our obligations
- Process only on your documented instructions.
- Bind everyone with access to confidentiality obligations.
- Implement the security measures in Annex B.
- Engage sub-processors only on the terms in section 5.
- Assist you with data subject requests and with your own compliance obligations.
- Notify you of personal data breaches without undue delay.
- Delete or return your data at the end of the service, per section 10.
- Make available the information needed to demonstrate compliance, per section 9.
4. Your obligations
You are responsible for:
- having a lawful basis for the data you put through the platform;
- giving any notices and obtaining any consents your own processing requires;
- the accuracy of your data, and for deciding what to place in a workload in the first place; and
- configuring the platform appropriately for your risk — in particular, restricting inference keys to in-region models where your data must not leave the region (see section 6).
5. Sub-processors
You give general authorisation for us to engage sub-processors. The current list is published at /legal/subprocessors and is part of this addendum.
We will give at least 30 days' notice before adding or replacing a sub-processor. If you reasonably object on data protection grounds within that period, we will work with you to find an alternative; if we cannot, you may terminate the affected service and we will refund the unused balance attributable to it.
Each sub-processor is bound by terms no less protective than these, and we remain liable to you for their performance.
6. International transfers
Customer workloads and the data they process run on infrastructure located in Indonesia, under Indonesian jurisdiction.
Compute does not leave Indonesia. A workload you deploy runs on infrastructure in the region it was placed in, and the platform does not relocate it to another region for capacity reasons.
Two transfers you should plan for, because they are properties of the service rather than exceptions:
- Payment data is processed by Stripe internationally. This concerns your billing contact and tax details, not your workload content.
- Out-of-region inference. Where you call a model the catalog marks as not in-region, the prompt and completion are transmitted to that model's upstream provider outside the region. The catalog states each model's jurisdiction as an explicit recorded value, never inferred from the model or provider name. Restricting an inference key to in-region models prevents this at the platform level, and is the control to use where your data must not leave the region.
Where a transfer requires a lawful mechanism under applicable law, we will put an appropriate one in place.
7. Security measures
We implement appropriate technical and organisational measures, set out in Annex B. We may update them, but not in a way that materially reduces protection.
8. Breach notification
We will notify you without undue delay, and in any event within 72 hours of becoming aware of a personal data breach affecting your data. The notification will describe the nature of the breach, the categories and approximate volume of data affected, the likely consequences, and the measures taken or proposed.
Where we cannot provide all of that at once, we will provide it in phases without further undue delay. Notifying you is not an admission of fault.
9. Assistance and audit
Data subject requests. Much of what you need is self-service: the console exposes your data and lets you export and delete it. Where a request needs our help, we will provide it, and we will forward to you any request we receive directly from your data subjects rather than answering it ourselves.
We will also assist with data protection impact assessments and prior consultations, taking into account the information available to us.
Audit. We will make available the information needed to demonstrate compliance with this addendum. You may audit no more than once in any twelve-month period, on 30 days' notice, during business hours, without unreasonably disrupting our operations, and subject to confidentiality. More frequent audits may follow a breach affecting your data, or a regulator's requirement.
We do not currently hold a third-party audit report — no SOC 2, no ISO 27001, no independent penetration test — so we cannot satisfy an audit obligation by handing you one. If your process requires that, tell us before contracting rather than after.
10. Return and deletion
On termination, you may export your data through the platform. We delete your content within 30 days of account closure, except where law requires us to keep it — in which case we keep only what is required, and continue to protect it under this addendum.
Billing and audit records are retained per the Privacy Policy, as data for which we are controller.
Annex A — Processing details
| Subject matter | Provision of container compute and inference services |
|---|---|
| Duration | For as long as you hold an account, plus the deletion period in section 10 |
| Nature and purpose | Storage, execution and transmission of customer workloads and their data; routing of inference requests to the model you select |
| Types of personal data | Determined by you. The platform imposes no restriction on what your workloads process, so this may include any category you choose to introduce |
| Special categories | Only if you introduce them. Tell us in advance if you intend to process health, biometric or similarly sensitive data, so we can confirm the configuration is appropriate |
| Data subjects | Determined by you — typically your customers, users or employees |
| Location of processing | Customer workloads and the data they process run on infrastructure located in Indonesia, under Indonesian jurisdiction. |
Annex B — Security measures
| Area | Measure |
|---|---|
| Encryption in transit | TLS on all external connections, and on the control channel to managed clusters |
| Encryption at rest | Cluster credentials and upstream provider credentials sealed with AES-GCM under a key held outside the database, decrypted just-in-time per request |
| Authentication | Argon2 password hashing; optional multi-factor authentication; API credentials shown once and revocable immediately |
| Tenant isolation | Per-workspace Kubernetes namespaces with scoped service accounts; per-request authorisation against the owning workspace; optional network policy per namespace |
| Access control | Role-based access within a workspace; separate platform operator and admin tiers |
| Logging and monitoring | Append-only audit record of every state-changing action including refused attempts, with actor, target and outcome |
| Resilience | Stateless, horizontally scalable control plane; database backups with a documented restore procedure |
| Data residency | Explicit recorded jurisdiction per model; inference keys restrictable to in-region models |
Applicable data protection laws for this processing may include:
- PDPA — Singapore Personal Data Protection Act 2012.
- UU PDP — Indonesia Law No. 27 of 2022 on Personal Data Protection.
Questions about this document? Contact us.