Privacy Policy
Last updated: 2026-05-14. yolo-auto is designed to collect as little user data as practical and to avoid storing prompt or response content.
1. What we collect
We collect account information needed to operate the service, such as your Google or Discord identity, email address when provided by your sign-in provider, account name, plan, subscription status, API-key metadata, and billing identifiers from Stripe. We store API-key hashes and prefixes, not raw API keys after creation.
2. Prompts and responses
yolo-auto does not intentionally store your prompts, uploaded content, model responses, or conversations. The admin tools show request metadata such as time, model route, provider, token counts, status, latency, and error codes; they do not show prompt or response text.
Your request content is transmitted only as needed to fulfill the API request, including to the upstream model provider selected by the route. Operators are not provided a product UI to browse prompt or response content because that content is not stored by yolo-auto.
3. Usage and diagnostics
We store usage metadata to enforce limits, detect abuse, debug reliability, and calculate billing/plan state. This includes API key ID, user ID, route name, provider ID, provider key ID, request counts, token counts, latency, status, request ID, and timestamps.
4. Billing data
Payments are handled by Stripe. yolo-auto does not store card numbers, bank details, or full payment credentials. We store Stripe customer, subscription, invoice, price, and event identifiers so we can keep your account plan and billing history in sync.
5. Sharing
We do not sell your personal data. We share data only with service providers needed to run yolo-auto, such as Cloudflare for hosting/storage/security, Stripe for payments, Google or Discord for authentication, and upstream model providers to process API requests you initiate.
6. Security
Provider keys, Stripe secrets, and session secrets are stored as server-side secrets. API keys are hashed before storage. Access to admin tools is restricted. No system is perfectly secure, but we design yolo-auto to minimize stored sensitive content.
7. Retention
We keep account, billing, and usage metadata for as long as needed to provide the service, resolve disputes, comply with legal obligations, and maintain security. Since prompt and response bodies are not stored by yolo-auto, there is no prompt/response history to retain or sell.
8. Your choices
You can disable API keys from the dashboard, cancel subscriptions through Stripe when billing is enabled, or ask the operator to delete or correct account metadata where applicable.
9. Changes
We may update this Privacy Policy as the service changes. Continued use after the policy is updated means you accept the updated policy.
10. Contact
For privacy questions or data requests, contact us at support@yolo-auto.com.