Privacy Policy
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 policy explains how Alynrex Pte. Ltd. handles personal data. It covers the account you hold with us. It does not cover the data you choose to process through the platform — see section 1.
1. Two kinds of data
The distinction runs through everything below, so it comes first.
- Your account data. Your email, your billing details, your audit trail. We decide what to collect and why, so we are the controller. This policy governs it.
- Your content. Whatever your workloads process — your datasets, your prompts, your customers' records. We hold it only to run the service and act on your instructions, so we are the processor and you are the controller. The Data Processing Addendum governs it.
Put plainly: we know that you deployed a container. We do not inspect what is inside it.
2. What we collect
You give us
- Email address, username, and password (stored only as an Argon2 hash — never in plain text).
- Where you sign in with an identity provider, the identifier and email that provider returns.
- Account type (individual or business), and for a business, the registered name and tax ID.
- Anything you send us in a support conversation.
The service generates
- An audit record of every action that changes something — registering a cluster, deploying a workload, minting or revoking a key, changing a rate — with who did it, when, and whether it succeeded. Failed and refused attempts are recorded too; a denied access attempt is often the entry that matters.
- A credit ledger: every charge and top-up, what it was for, and the balance after.
- Usage metering: machine type and running time for compute, token counts and model for inference.
- Server logs and IP addresses, for security and debugging.
We do not collect
- Card numbers. Payments go directly to Stripe; we never see or store them.
- Advertising or cross-site tracking data. There are no third-party trackers on this site.
- The contents of your workloads, volumes or object storage.
3. Why we process it
| Purpose | Data | Basis |
|---|---|---|
| Providing the service | Account, workspace, workload metadata | Performance of our contract with you |
| Billing and tax compliance | Billing details, ledger, usage | Contract, and our legal obligations |
| Security, abuse prevention, audit | Audit records, IP addresses, logs | Our legitimate interest in a secure platform |
| Service notices (verification, billing, incidents) | Email address | Contract |
We do not sell personal data, and we do not use it to train models. We do not send marketing email without your consent, and consent is withdrawable at any time.
4. Where it lives
Customer workloads and the data they process run on infrastructure located in Indonesia, under Indonesian jurisdiction.
Account and billing records are held in the same infrastructure as the control plane. Payment processing takes place with Stripe, which operates internationally — see sub-processors.
Inference is the exception you should understand. Where you call a model the catalog marks as not in-region, the prompt and the completion are transmitted to that model's upstream provider, outside the region. Restricting an inference key to in-region models prevents this at the platform level.
5. Who we share it with
We share personal data only with:
- Sub-processors that help us run the service, listed at /legal/subprocessors, each bound to protect it.
- Authorities, where legally compelled. Where we are lawfully permitted to tell you about such a demand, we will.
- An acquirer, if the business is sold, subject to the same protections. We will tell you before your data moves.
6. How long we keep it
| Data | Retention | Why |
|---|---|---|
| Account details | While your account is open, then 90 days | Recovery from accidental closure |
| Billing and ledger records | 7 years | Tax and accounting obligations |
| Audit records | 2 years | Security investigation and customer compliance needs |
| Server logs | 30 days | Debugging and abuse response |
| Your content | Until you delete it; 30 days after account closure | Governed by the DPA, not this policy |
Billing records outlive account deletion because we are required to keep them. They are reduced to what tax law requires.
7. How we protect it
- Passwords are stored as Argon2 hashes. We cannot read them.
- Credentials for registered clusters and upstream providers are encrypted at rest with AES-GCM under a key held outside the database, and decrypted only for the request that needs them. A database dump alone does not yield working credentials.
- All connections use TLS.
- Tenants are separated by namespace, and authorisation is checked per request against the workspace that owns the object.
- Multi-factor authentication is available on your account, and we recommend enabling it.
What we cannot yet evidence. We hold no SOC 2 report, no ISO 27001 certificate and no independent penetration test. The controls above are described by us and have not been audited by a third party. See our trust page.
Breaches. If a breach affects your personal data and is likely to create a risk to you, we will notify you and the relevant regulator without undue delay. The two laws that apply to us set their own deadlines, and they do not start counting at the same moment:
| Law | We notify | Within | Counted from |
|---|---|---|---|
| Indonesia UU PDP | the affected person and the PDP Agency | 3 x 24 hours | becoming aware of the breach |
| Singapore PDPA | the PDPC, and affected individuals as soon as practicable | 3 calendar days | completing the assessment that the breach is notifiable |
We work to the Indonesian trigger, because it is the earlier of the two — its clock starts when we become aware of a breach rather than when we finish assessing it, and it is the one that requires telling you directly rather than only the regulator. Meeting it meets the Singapore obligation as well; meeting Singapore's alone would not.
8. Your rights
Depending on where you are, you may have the right to:
- ask what personal data we hold about you, and get a copy;
- have inaccurate data corrected;
- have data deleted, where we are not required to keep it;
- object to or restrict processing based on legitimate interests;
- receive your data in a portable format; and
- withdraw consent where processing relies on it.
Much of this is self-service: the console shows your account data, your ledger and your audit trail, and lets you export and delete. For anything else, contact us and we will respond within 30 days.
The following laws may apply to our processing of your data:
- PDPA — Singapore Personal Data Protection Act 2012: applies to Alynrex Pte. Ltd. as a Singapore-incorporated entity.
- UU PDP — Indonesia Law No. 27 of 2022 on Personal Data Protection: applies to processing of Indonesian data subjects' personal data, including from outside Indonesia.
You have the right to complain to the relevant supervisory authority. We would rather you came to us first.
9. Contacting us
Reach us through our contact page. Write to Alynrex Pte. Ltd., UEN 202207417W.
We will update this policy as the service changes. Material changes are announced by email and the date at the top of this page changes.
Questions about this document? Contact us.