EEveryLLM

Legal

Privacy Policy

Effective 1 September 2026. Applies to everyllm.app and the EveryLLM gateway.

Who we are

EveryLLM is an AI router. You attach provider credentials you already pay for. We route your agents through those backends. We do not sell model tokens or another party’s quota. Contact: [email protected].

What we collect

Account. Email, password hash, optional display name, role (user or operator), verification time, and plan fields (unused until billing is enabled).

Backends you configure. Provider type, URLs, headers, and encrypted secrets: API keys and OAuth access/refresh tokens. Encryption is AES-256-GCM at rest. We never share OAuth tokens across accounts. Operators cannot open another user’s secrets.

Keys, endpoints, connectors. Names, hashes of client API keys (not the plaintext after creation), routing rules, and connector registration metadata.

Request logs. Timestamp, endpoint, backend, API key name/prefix, models, status, token counts when the upstream reports them, latency, and error text. We store this so you can debug routing. We do not use prompt bodies to train models.

Email. Verification and password-reset messages are sent via Resend from [email protected]. Catch-all inbound mail for everyllm.app is forwarded to our operator mailbox.

Analytics. The public site and console load Firebase Analytics (Google) for page views. That may set cookies or similar identifiers on your device.

What we do not collect on purpose

We do not sell prompts, completions, or tokens. We do not build advertising profiles from your routed traffic. Payment card data, when Stripe is enabled later, would be handled by Stripe — we would store customer and subscription ids, not full card numbers.

Who can see what

Each account’s backends, keys, logs, and connectors are isolated. Two accounts may both use the endpoint slug main; the client API key selects the owner. An operator can list users and disable an account (which blocks dashboard login and that account’s keys). Operators cannot browse another tenant’s OAuth tokens or API keys.

Retention and deletion

You can delete your account in Settings. That removes the account, backends, keys, and connectors. Request-log rows are detached from the account (foreign keys nulled) rather than used to reconstruct your configuration. Email-verification tokens expire (24 hours for verify, 1 hour for password reset).

Processors

Hosting and the database run on our Coolify origin. DNS and TLS are on Cloudflare. Email sending is Resend. Analytics is Firebase/Google. Upstream model providers (Anthropic, OpenAI, xAI, Moonshot, and others you attach) receive the traffic you send through your backends under their terms.

Your choices

Correct email and password in Settings. Resend verification. Sign out other sessions. Delete the account. For access or deletion requests, email [email protected].

Terms of Service · Docs