The short version
We do not train on your prompts or completions. We do not sell or share them. Content is not logged in the request path. The only content retention is a per-tenant response cache that expires within 24 hours. Billing metadata is kept for accounting.
What we collect
Account data: your login identifier (email address or connected wallet address), your Privy account id, and the embedded wallet address created for billing. Usage metadata: model id, token counts, charge amounts, timestamps, and settlement status for every call. This is what powers metering, your dashboard, and on-chain settlement. Operational logs: standard service logs (status codes, latencies, error details) that do not include prompt or completion content.
Prompts and completions
Request and response content is processed in memory to serve your call. It is not written to logs, not used for training, and never reviewed by humans. One exception, built for your benefit: our exact-match response cache stores a completion for up to 24 hours so identical repeat calls can be served instantly at half price. Cache entries are isolated per account (one tenant's cached response is never served to another) and expire automatically. Streaming responses are never cached.
On-chain data
Settlement happens in USDG on Robinhood Chain. Like all public-chain activity, settlement transactions (addresses, amounts, timestamps) are publicly visible on-chain by design. Prompt and completion content never touches the chain.
Third parties
Authentication and embedded wallets are provided by Privy (privy.io), which processes your login identifier under its own privacy policy. We do not use advertising trackers or analytics that profile you across sites.
Retention and deletion
Cached completions: up to 24 hours. Billing and usage metadata: retained while your account exists, as required for accounting. Account deletion: contact us and we delete your account data within 30 days, except records we are legally required to keep.
Contact
Questions or deletion requests: reach us on X at @ArcenCompute.
