Starveri API Privacy
Plain-language data handling notes for credits, keys, demo requests, and usage logs.
What Starveri API Stores
- Account and billing metadata needed to sell prepaid credits, issue API keys, apply limits, and reconcile Stripe Checkout sessions.
- API-key metadata such as key name, masked key, exact credit balance, flags, usage totals, and recent activity.
- Demo usage counters by IP so the public GPT 5.5 demo can enforce 5 requests, 2,000 demo tokens, and 1 concurrent request per user.
- Request usage metadata needed for billing and abuse protection, including token counts, tool-call counts, status, model, and approximate cost.
What Starveri API Does Not Intend To Do
- It does not ask public demo users to upload files or images.
- It does not expose private API keys, Stripe secrets, internal logs, or provider configuration on public pages.
- It does not advertise official OpenAI affiliation.
Operational Safety
Starveri API uses prepaid credits, exact per-token billing, a five-file request limit, demo limits, moderation for the public demo, and a provider-wide kill switch for temporary error responses during emergencies.