What we store
- Your account. You sign in with Google. We store your email address, an account ID, and when you signed up and were last active. Google's sign-in service, Firebase Authentication, also keeps your name and profile photo for the sign-in.
- Connected subscriptions. When you connect Claude, Codex or Gemini, your provider gives us login tokens. For Kimi, you paste an API key. We store these encrypted, together with the account ID and email your provider reports. The provider, the nickname you give it, its plan, quota and status are stored unencrypted, so the dashboard can show them. We never see your provider password.
- API keys. We don't store your keys. For each key we keep a one-way check value that recognizes it, plus its ID and nickname. That's why a lost key can't be recovered.
- Request logs. For each API request we record the time, the model, which key and subscription handled it, token counts, timing and status. If a request fails, we keep the error message, which can quote your provider's response.
- Usage totals. Daily totals of those requests, for your usage charts.
- Your plan. Which plan you're on, its status, and when it renews or ends. Your payment details stay with Stripe.
- Server logs. Our API servers keep access logs with the time, path and status of each request, for security and debugging. These can include your IP address and are deleted on a rolling basis.
We never store your prompts, outputs, files or images. They pass through our servers to your provider and back.
Why we use it
- To run Plan2API for you: signing you in, keeping your subscriptions, routing your requests and showing your usage and logs. We need this to provide the service.
- To keep it secure and working: rate limits, abuse prevention and debugging. This is our legitimate interest.
- To improve the product: cookieless analytics that show which pages and features get used. Also our legitimate interest.
Emails we send
We email the address on your account with alerts about your subscriptions and your plan, such as when a subscription needs reconnecting or gets paused. When you sign up, we send ourselves a notification with your email address.
How your logins are protected
Your subscription logins are encrypted with AES-256-GCM and sealed to your vault with HPKE (X25519). Only your API key can unlock the vault. We never store that key, so nobody can unlock your logins from our database alone, including us.
When a request arrives with your key, our server unlocks the login in memory to call your provider. A leaked database or backup doesn't expose your logins, but someone with your key, or with control of our live servers, could use your subscriptions. Keep your key secret, and revoke it if it leaks.
Traffic between your app, our servers and your provider is encrypted with TLS.
Who processes your data
We use a few service providers to run Plan2API, and each gets only what it needs:
- Google Firebase signs you in.
- Cloudflare hosts this website, sits in front of our API and stores our encrypted backups. Your traffic and IP address pass through it.
- OVHcloud runs our API servers and database in Germany.
- Clicktag provides our cookieless analytics.
- Stripe handles payments for Pro and Scale as merchant of record. It receives your email address from us and your payment details directly from you.
- Postmark delivers our emails, so it receives your email address and the alerts we send you.
Your requests go to the provider of the subscription that handles them (Anthropic, OpenAI, Google or Moonshot AI), under your own account. Their privacy policies cover what they do with them.
We don't sell your data, show ads, or use anything you send through the API to train models. We only share data beyond this when the law requires it.
Where your data is stored
Our servers and database are in Germany. Cloudflare, Google, Stripe and Postmark operate worldwide and may process data outside the EU, under the safeguards the GDPR requires, such as the EU's Standard Contractual Clauses.
How long we keep it
Everything above stays for as long as your account exists, except server logs, which roll over on their own.
- Deleting your account in Settings deletes your account, vault, keys, subscriptions, usage and logs from our database straight away. We remove your Firebase sign-in record on request.
- Resetting your vault deletes your keys and connected subscriptions. Your usage and logs stay.
- Backups are encrypted and only used to recover from failures. Deleted data can remain in older backups, where your subscription logins stay locked under a key we never had.
Your rights
You can ask for a copy of your data, have it corrected or deleted, restrict or object to how we use it, and take it elsewhere. Email support@plan2api.com from the address on your account. You can also export your usage and logs from the dashboard, and delete your account in Settings at any time.
If you're in the EU or UK and think we've mishandled your data, you can complain to your local data protection authority.
Changes
When this policy changes, the date at the top changes with it, and we'll point out significant changes on this page.
Contact
Questions, requests or a security issue to report: support@plan2api.com.