Account and billing information
The platform stores account details, password hashes, session records, payment references, wallet entries, API-key metadata, and request usage metadata. Customer API keys are hashed; recoverable supplier keys are encrypted.
Prompts and responses
The gateway forwards request content to the configured upstream supplier to provide inference. Prompts and responses are not saved in usage logs by default. The supplier and its model providers may have their own processing and retention practices, which must be disclosed and verified before launch.
Service providers and controls
Configured database, email, hosting, and payment providers process the information needed to operate their services. Card entry is hosted by the payment processor. Request metadata supports billing, fraud prevention, troubleshooting, and reconciliation.
Your choices
You can revoke API keys and change notification preferences in the dashboard. Contact the published support channel for account access, deletion, or data requests once the service launches.