Privacy Policy

Effective 2026-07-24 · applies to the Fugal website, API and paid credit

1. Who we are

Fugal is a research project demonstrating cost-aware LLM routing. The routing engine is open source at github.com/fugal-ai/fugal-subnet; the code for this website is not published (see the Terms, §7). For any privacy question or request, email support@fugalai.com — a private channel, which a public GitHub issue is not. You can also open an issue for anything non-personal.

2. What we collect

• Account info — if you sign in, we receive your email and, from your OAuth provider (Google/GitHub), your name and avatar. That's the whole profile.
• Chats (signed in) — your conversations are stored in our database so they follow you across devices. Access is enforced by row-level security: each account can only ever read or modify its own rows.
• Chats (signed out) — stored only in your browser's local storage. Messages you send are processed transiently to produce the routing result or answer, but are not kept in any database.
• Billing — if you buy credit, Stripe collects and holds your payment details and billing address; we never receive or store your card number. We keep only a Stripe customer reference, your credit balance, and a record of each purchase and each request's cost.
• Usage — for accounts with credit or an API key we record per-day request counts and cost, so the free allowance and your balance can be calculated. This is usage metering, not behavioural profiling.
• Local preferences — theme, sidebar state, and similar settings stay in your browser's local storage.
• Nothing else — no analytics scripts, no advertising or cross-site trackers, no fingerprinting. Ordinary short-lived server logs (IP, request path) may exist for debugging and abuse prevention, as on any web server.

3. How we use it

• To run the service — authentication, syncing your chats, and showing you your own history.
• To improve the router — only with your opt-in. In Settings → Data & privacy there is a toggle, "Help improve the router." It is off by default. Only if you turn it on may your chats be used to train the routing model. You can turn it off at any time.
• We do not sell, rent, or share your data with advertisers — ever.

4. Cookies & storage

We use only strictly necessary storage: an authentication session token (so you stay signed in) and browser local storage for your chats and preferences. There are no advertising, analytics, or third-party tracking cookies, which is why you don't see a cookie consent banner. If we ever add non-essential cookies, we will ask first.

5. Who processes your data

• Supabase — hosts authentication and the database that stores signed-in profiles and chats.
• Your OAuth provider (Google or GitHub) — handles the sign-in itself under its own privacy policy; we only receive the basic profile described above.
• Stripe — processes card payments and stores your payment details and billing address under its own privacy policy. We receive only a customer reference and confirmation that a payment succeeded, never the card itself.
• Model providers (Answer mode only) — Route mode never sends your message to any third party: the router runs on our own server. When you use Answer mode, your question and the recent messages in that chat are sent through OpenRouter (an API broker) to the language model chosen for your query. The models we currently use come from OpenAI, Anthropic, Google, Alibaba (Qwen), DeepSeek, Z.ai, Moonshot AI, Mistral, MiniMax, and Meta (Llama). These providers process your prompt under their own API terms; we send them no account information — only the message text needed to answer.

6. Your rights & controls

• Export — download all of your chats as JSON from Settings → Danger zone.
• Delete — delete your account and all synced data from Settings; deletion is immediate and permanent. Two honest caveats: if you hold unused credit, deletion is blocked until you spend it or ask for a refund (we won't close an account while holding your money — Terms §3), and accounting records of past purchases survive deletion, as described under Retention below.
• Opt out of training — the Settings toggle, off by default.
• Ask — for access, correction, or anything this page doesn't cover, email support@fugalai.com. Requests about your own data should go by email, not a public issue tracker.

7. Retention

Signed-in chats and profile data are kept until you delete them (per-chat, or the whole account from Settings). Deleting your account removes your profile, all synced chats, your API keys and your credit ledger via database cascade. Local-storage data lives in your browser until you clear it.

One thing deliberately survives deletion: accounting records of purchases. If you ever bought credit, we keep a record of the amount, currency, date and payment reference, because tax and anti-fraud rules require it and Stripe retains its own copy regardless. These records are kept deliberately thin — no name, no email, no IP address, and no message content — so nothing in them identifies you on its own. They are not readable by any user account, including yours; they exist for our books. Everything about you that is personal is deleted.

8. Changes

If this policy changes in a way that matters — new data collected, new processors, or a change to the training rules — we'll update the effective date above and note the change plainly here. This page previously pointed at a public repository for its revision history; that was wrong, because this policy lives with the website's code, which is not published. The effective date above is the authoritative record of when it last changed.