The usage ledger stores
- Account identifiers
- API key prefix and irreversible hash
- Model and token counts
- Reservation, charge, and refund state
- Request ID and timestamps
This page documents the controls and data handling implemented by Kaista Cloud today, together with the published Private Beta policies. Qualified counsel should complete review before public checkout opens.

Kaista Cloud authenticates the key, reserves credits, and routes requests to approved fixed model endpoints.
Upstream and Supabase administrative keys remain in server environments.
Raw customer keys are shown once; the database stores a SHA-256 hash.
Credits are reserved first, settled on success, and released on failure.
Supabase RLS limits wallets, keys, and usage records to their owner.
The proxy only permits server-approved HTTPS model endpoints and routes.
JSON bodies are capped at 2 MB and upstream calls have a timeout.
These five documents currently govern the closed beta. Qualified counsel should review them against the registered business and sales jurisdictions before public checkout opens.
Accounts, payment, liability limits, suspension, and termination
Data categories, retention, service providers, and international processing
Sign-in sessions, language preferences, and future non-essential tracking
Prohibited uses, abuse response, and model-supply restrictions
Non-refundability, legal exceptions, disputes, and expiry
Support hours, response targets, maintenance, and incidents