Privacy Policy
Last updated October 12, 2026
This policy explains what personal information Mux collects when you use getmux.io and the Mux API, how we use it, and the choices you have.
What we collect
- Account data. When you sign in with Google we receive your Google account ID, email address, name, and profile picture URL. We do not receive your Google password.
- API activity. For each request we log the time, key used, model, status, latency, cost and any error. By default this log does not store your query text or the results. Our hosting provider and load balancer keep standard access logs (IP address, user agent, path).
- Provider keys (BYOK). If you add one, it is encrypted at rest and never shown again, only a short hint of the last characters.
- Payment data. Payments are handled by Stripe. We see your purchase amount, a Stripe customer/session ID and the status, but never your full card number.
- Cookies. We set a signed, HttpOnly session cookie to keep you signed in (7 days), plus a short-lived cookie during sign-in to protect against forgery. We do not use advertising or analytics cookies.
How we use it
- To run the Service: authenticate you, route and bill requests, enforce spend limits, and show your usage.
- To keep it safe: detect abuse, debug errors and prevent fraud.
- To contact you about your account, billing or important changes to the Service.
We do not sell your personal information or use your queries to train models.
Who we share it with
- Search providers. Your query and any filters you send are forwarded to the provider that handles the request (Exa, Parallel or Keenable). Their privacy policies apply to what they do with it. Avoid putting sensitive personal data in queries.
- Service vendors. Google (sign-in), Stripe (payments), Amazon Web Services (hosting) and our database provider process data for us under their own terms.
- Legal. We may disclose information if required by law or to protect rights, safety and the Service.
- If Mux is involved in a merger or sale, data may transfer to the new owner under this policy.
Retention
We keep account data while your account is open. Request logs and ledger entries are kept as long as needed to bill you, resolve disputes and meet accounting obligations. When you close your account we delete or anonymize personal data, except what we must keep by law.
Security
API keys are stored as one-way hashes, provider keys are encrypted, and all traffic uses HTTPS. No system is perfectly secure, so we cannot guarantee absolute security.
Your choices
You can ask us to access, correct, export or delete your personal data, or object to certain processing, by emailing support@getmux.io. Depending on where you live (for example the EEA, UK or California) you may have additional legal rights, and we will honor them.
International transfers
Mux and its vendors operate in the United States and elsewhere, so your information may be processed outside your country.
Children
Mux is not intended for anyone under 18 and we do not knowingly collect their data.
Changes
If we change this policy we will post the new version here and update the date above.
Contact
Privacy questions: support@getmux.io.