Terms of Service
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.
These terms govern your use of the ALYNREX platform, operated by Alynrex Pte. Ltd. (UEN 202207417W), a company incorporated in Singapore. By creating an account or using the service, you agree to them.
1. The agreement
"You" means the person or organisation using the service. Where you accept these terms on behalf of an organisation, you confirm you are authorised to bind it, and "you" means that organisation.
These terms, together with the Acceptable Use Policy and the Privacy Policy, form the whole agreement between us. Where you have signed a separate written agreement with us, that agreement takes precedence over these terms to the extent of any conflict.
2. Accounts
You must provide accurate registration details and keep them current. You are responsible for activity under your account, including activity by members you invite to a workspace and by any API key or access credential you create.
Keep your credentials secret. API keys and inference keys are shown once at creation and cannot be retrieved afterwards. If a credential is exposed, revoke it in the console. Revocation is not instantaneous: the inference gateway caches key lookups for up to 30 seconds, and for up to five minutes if it cannot reach our control plane, so a revoked key may continue to work for that long. Treat an exposed key as live until that window has passed.
You must be at least 18 years old, and you must not use the service if you are subject to sanctions that would prohibit us from providing it to you.
3. Credits and payment
The service is prepaid. You buy credits, and usage draws them down. We do not invoice in arrears for usage beyond your balance.
- Compute is metered by machine type and running time, charged per minute for as long as a workload is running — including while it is idle. Stopping a workload stops the charge.
- Inference is metered by input and output tokens at the rate published for the model in the console at the time of the call.
- Rates are shown in the console before you use a resource. We may change rates prospectively; changes never apply retroactively to usage already incurred.
Running out. When your balance reaches zero, running workloads are stopped automatically and new ones are refused. Because a charge covers time already served, a balance may end slightly below zero — for example where a workload was mid-minute, or an inference call was in flight, when the balance ran out. We do not treat that residue as a debt and we do not pursue it, but it is deducted from your next top-up.
Spend caps. A workspace may carry a monthly spend cap set by whoever pays for it. A capped workspace stops spending when it reaches its cap even if the payer's balance is positive. Caps limit spending; they are not a fund and hold no money.
Refunds. Credits are refunded to your balance automatically where we charge you for a resource that failed to start. Unused credits are otherwise non-refundable except where required by law or where we terminate the service for a reason other than your breach, in which case we will refund the unused balance. Credits have no cash value and cannot be transferred between accounts.
Taxes. Prices exclude taxes unless stated. You are responsible for any taxes arising from your use, other than taxes on our income. Provide a valid tax identification number where one applies to you.
4. The service
We provide container compute on managed Kubernetes and an inference API over a catalog of models. Customer workloads and the data they process run on infrastructure located in Indonesia, under Indonesian jurisdiction.
Where inference runs. Each model in the catalog states its jurisdiction and whether it is served in-region. Calls to a model marked as not in-region are routed to the upstream provider named for it, and prompt and completion content reaches that provider. You can restrict an inference key to in-region models only; a key so restricted cannot reach an out-of-region model. See the sub-processors list.
Changes to the catalog. Models are added, repriced and withdrawn over time. We will give reasonable notice before withdrawing a model you are actively using where we can.
5. Your content
You keep all rights in the code, data, models and content you bring to the platform. We claim no ownership of it.
You grant us only the licence needed to run the service for you: to store, transmit and process your content for the purpose of providing the platform, and to disclose it where legally compelled. We do not use your content, prompts or completions to train models.
You are responsible for having the rights to what you run and for the lawfulness of the data you process. Where you process personal data through the platform, the Data Processing Addendum applies.
Deletion. Deleting a workload deletes its running state. Data you have stored in a volume or object storage is deleted when you delete it, or when your account is closed and the retention period in the Privacy Policy has passed. Keep your own backups — we do not undertake to restore customer data you have deleted.
6. Acceptable use
Your use must comply with the Acceptable Use Policy, which forms part of these terms. In short: no unlawful use, no attacking others, no attacking the platform or other tenants, and no cryptocurrency mining.
7. Availability
We do not currently offer a service level agreement. The service is provided as it stands. We aim for high availability and will tell you about planned maintenance where we can, but we make no uptime commitment and offer no service credits.
If you need a contractual availability commitment, talk to us before you rely on the platform for production work. We would rather negotiate one than have you assume it.
8. Suspension and termination
We may suspend or limit your access where:
- you breach these terms or the Acceptable Use Policy;
- your usage threatens the stability or security of the platform or another tenant; or
- we are required to by law.
Where circumstances allow, we will tell you first and give you a chance to fix the problem. Where the risk is immediate — an active attack, or a legal requirement — we may act first and tell you after.
You may close your account at any time. Closing it stops your workloads. We may terminate this agreement on 30 days' notice; if we do, we will refund your unused credit balance.
9. Liability
Nothing in these terms limits liability that cannot lawfully be limited, including for death or personal injury caused by negligence, or for fraud.
Subject to that, neither party is liable for indirect or consequential loss, loss of profit, revenue, goodwill, or loss or corruption of data. Our total liability arising from this agreement in any twelve-month period is limited to the amount you paid us in that period.
Model output. Output from a model is generated automatically and may be wrong, incomplete or unsuitable for your purpose. We do not warrant its accuracy. Decisions you take on the basis of model output are yours, and you should not use the service as the sole basis for decisions with legal, financial, medical or safety consequences.
10. Changes
We may change these terms. Where a change materially reduces your rights, we will give at least 30 days' notice by email to your registered address and publish the revised terms here with a new date. Continuing to use the service after a change takes effect means you accept it. If you do not, close your account and we will refund your unused balance.
11. Governing law
This agreement is governed by the laws of Singapore, and the parties submit to the exclusive jurisdiction of the courts of Singapore.
Governing law is a separate question from where your data sits. Customer workloads and the data they process run on infrastructure located in Indonesia, under Indonesian jurisdiction. Data residency is addressed in the Data Processing Addendum.
Questions about this document? Contact us.