/ privacy

privacy

// last updated 2026-04-14

// what we store

  • ·Your handle (whatever you picked at signup) and a hash of your password(argon2id, salted). We never store the password itself.
  • ·The provider tokens you paste (Claude Max OAuth, OpenAI key). Encrypted at rest with AES-256-GCM using a key only the server holds; we can decrypt them to route your requests, but not display them back to you.
  • ·Usage metrics per call: model name, input/output token counts, latency, cost estimate, timestamp, which of your API keys was used. Used to render the dashboard.
  • ·One session cookie (mr_session, HttpOnly, Secure, SameSite=Lax) — a JWT that proves you're logged in.
  • ·Subscription state if you pay: NOWPayments invoice ID, amount, currentPeriodEnd.

// what we don't store

  • ·Your email, name, phone, address, country, or IP address (not persistently).
  • ·The bodies of your API requests or responses. We pass them through to Anthropic/OpenAI without logging them. (A dev-only LOG_REQUESTS=1debug flag exists; it's off in prod.)
  • ·Any third-party analytics, tracking pixels, or advertising cookies. There are none.

// who sees your data

  • ·Anthropic / OpenAI — they see every request you route through us, because that's where we forward it. Their privacy policies apply to the content of your calls.
  • ·Railway — our hosting provider; they see encrypted traffic to the api and web services plus database connections. They don't see plaintext tokens or passwords.
  • ·NOWPayments — if you pay via crypto. They receive the payment details (amount, wallet addresses); we receive only an invoice ID and a confirmation event. See their privacy policy.
  • ·No one else. We don't sell, share, or trade any of this data.

// deletion

Go to /settings, hit the delete-account button. Your row, your tokens, your usage events, and your subscription row all go with it. There's no email to unsubscribe from because we don't have your email.

// security reports

If you find a vulnerability, please use the GitHub private security advisory flow on the repo hosting this code rather than posting publicly. We'll credit you in the fix commit if you want.