Privacy Policy
Infimal (formerly Airglow) is an inference cloud operated by Metastable Lab. Its control plane manages accounts, keys, credit and the request ledger. This page says exactly what we hold, why we hold it, and how long.
Effective 20 September 2026
Who we are
Metastable Lab operates the Infimal inference cloud and its control plane. Metastable Lab is the controller of the data described here. For any question about privacy, or to ask for deletion, write to [email protected].
The company is in Singapore, and so is every machine that serves Infimal.
Account data
When you create an account we store your email address, the display name you choose, and how you signed in.
- If you sign in with Google or GitHub: the provider’s subject identifier for you, and the email address that provider reports. We never receive your password.
- If you sign in with an email code: your email address and a one-time code, which is single use and expires after ten minutes.
- Session records: when a session was created, when it expires, when it was last seen, and the browser user-agent string it was created from. You can see and revoke your own sessions in your account settings.
- API keys: the name you gave a key and its short prefix. Key material itself is hashed and never stored in a form we can read back, so we cannot show you a key again after it is created.
Service data: what a request leaves behind
Every request that is served writes metadata: the model, the token counts, the latency, the cost, and the outcome. That metadata lives in two places. The ledger records the money and is append-only — entries are never edited or removed, because your balance is derived from them and accounting depends on the history staying intact. A bounded ring of recent requests is kept so that you can see your own last requests in the console and so that we can investigate a failure while it is still fresh; it is bounded, so older entries fall out of it as new ones arrive.
Whole days of the operational tables are archived out of the database into a private object-storage bucket after 90 days, and then pruned from the database. The archive is not public and is not shared.
Request and response content
Chat, completion and transcription content — what you send and what the model returns — is recorded to a private bucket as a transcript archive. We keep it for three purposes only: operating the service, investigating abuse, and debugging failures.
It is never used to train models, ours or anyone else’s. It is deleted when your account is deleted.
Audio you submit for transcription is forwarded to the upstream provider that serves the model you asked for. What that provider does with it is governed by that provider’s own terms; the model catalogue shows the source kinds for every model, so you can see before you send whether a model is served by our own hardware or bought from someone else.
Where your data is
All Infimal infrastructure runs on Railway in Singapore. Object storage is Railway buckets, also in Singapore. We do not replicate account or request data to another region.
Who else processes it
| Subprocessor | What it handles |
|---|---|
| Railway | Hosting and object storage, in Singapore |
| Stripe | Payments. Card details go to Stripe and never touch Infimal |
| Google, GitHub | Sign-in, and only if you choose that provider |
| Maileroo | Transactional email, such as sign-in codes |
| Cloudflare | DNS and edge |
| Upstream model providers | The provider a request is routed to when the model you called is served externally |
There is no advertising network, no data broker and no analytics vendor in that list, because we use none.
Browser storage
The site keeps one thing in your browser: a session token in localStorage, so that reloading the page does not sign you out. There are no advertising cookies and no analytics cookies. Clearing your browser storage signs you out of this browser.
Why we hold each thing
- Account and session data: to sign you in and to let you see and revoke your own sessions.
- Request metadata and the ledger: to charge you correctly, to show you your balance and spend, and to keep accounting records.
- The transcript archive: to operate the service, to investigate abuse, and to debug failures.
- Email through Maileroo: to send the codes and service notices your account needs.
Your choices
You can change your display name and revoke any session from your account settings, and you can revoke an API key at any time. To ask for a copy of your data or to delete your account, write to [email protected].
Deleting an account deletes its transcript archive. Ledger entries are retained, because they are the accounting record of money that moved, and the archived operational days are retained for the same reason.
Changes to this policy
If this policy changes, the effective date at the top changes with it, and we will say what changed. If a change means we would handle content in a way this version does not describe, we will tell account holders by email before it takes effect.
Contact
Metastable Lab, Singapore. Privacy and legal: [email protected]. The terms that govern use of the service are on the Terms of Service page.