Security
Specific measures, not adjectives. Each item below describes how the production system is set up today. The last section lists what we do not claim.
The platform runs in the AWS Asia Pacific (Thailand) region, ap-southeast-7.
Your account, credit balance, billing ledger, usage records and tax invoices are stored in the AWS Thailand region, along with the API gateway and the services that handle them. An encrypted backup copy is made every night and kept outside AWS, on Cloudflare R2, and service logs are forwarded to our company’s monitoring system.
To answer a request, it has to reach the model provider — AWS Bedrock, Google Vertex AI, Azure AI Foundry or another provider in the catalogue. Most models are served from Singapore or Tokyo; some only from a provider’s global region, which can be outside Asia, for example the United States. Organisations on the available policy can also reach providers in mainland China.
Your organisation has a routing policy — strict, regional or available — which our team sets for you on request. A new API key takes that policy when it is created, and it is enforced on every call. See the docs for exactly what each allows.
In transit over the internet and to every data store, and at rest in every store that holds your data.
Connections from your client to the gateway use TLS, and so do our services’ connections to the database, the cache and object storage. Traffic between our own services stays on a private network inside AWS and is not TLS-encrypted.
The PostgreSQL database, the cache and the object storage holding invoices and reports are encrypted at rest.
A key is shown to you once, when you create it. We keep only a hash of it, so nobody here can read it back — including us.
What happens to the database if a data centre fails, and how data is recovered.
The database runs with a synchronous standby in a second AWS availability zone in Thailand. If one zone fails, the standby takes over.
The database can be restored to any point in the last 7 days, and is protected from accidental deletion.
Billing entries are append-only at the database level. A correction is a new, visible entry — history is never rewritten.
Who and what can reach the system.
Services run in private network subnets with no public IP addresses. Only the load balancer faces the internet. Containers run as non-root users.
Required for owners and admins of organisation (B2B) accounts, using an authenticator app, with single-use recovery codes. Staff accounts require it too. For individual accounts it is optional.
A top-up is credited only after a signed callback from the payment gateway is verified and processed once, or after our team checks a transfer slip you upload — never from a browser redirect. Credit from promo codes, refunds or adjustments by our team is recorded as its own ledger entry.
What passes through the gateway, and what it keeps.
The gateway records token counts, cost, model, provider, region, time and the IP address a request came from — what billing and your usage history need. It does not write the text of your prompts or the model’s replies anywhere.
Nothing that passes through the gateway is used to train any model. The model provider you route to has its own terms, which we do not change.
Honest limits
So you can weigh the rest properly. We will update this list when any of it changes.
AWS holds ISO 27001, SOC 2 and other certifications for the infrastructure we run on. IC Lueur Ai itself is not certified to any of them.
The measures above are our own. They have not been assessed by an outside security firm.
The database has a standby; some other components, such as the cache, still run as a single copy. We do not offer an SLA.
The FAQ covers tax, payment and data questions. For anything else, contact us directly.
