Everything we store, exactly
#| We keep | Which is | Because |
|---|---|---|
| Template submissions | The video, prompt, title, optional credit and your account ID. Published once approved, with no account details shown. Kept until removed; refused submissions are kept 13 months and their video is deleted | To show approved templates in the library |
| Request debug traces | Prompts, responses, tool content and stream diagnostics; bounded and redacted, with 30-day expiry | Investigating request failures and incorrect responses; restricted administrator access with audited views |
| Aggregate page analytics | Page, referrer, country, browser, operating system and device class processed by Vercel Web Analytics; no account, wallet, key, prompt or completion fields | Understanding aggregate site traffic. Vercel documents this as cookie-free and uses a site-specific visitor hash that expires after 24 hours |
| Product analytics (on by default) | A random HMAC pseudonym, public and first landing pages, bounded campaign codes, referrer hostname, browser sessions, coarse country/region and device/browser/OS families, experiment assignments, key reveal/copy and setup milestones, model identifiers, settled credit and usage amounts, and an immutable local acquisition link to the account created from that visit | Measuring whether an offer leads to a key, credit, and successful request; on unless you turn it off under Privacy choices |
| Google Ads measurement (on by default) | Website visits, account sign-ups, confirmed top-up amounts with a random payment reference, advertising cookies and identifiers, and browser and network information processed by Google, including your IP address | Measuring advertising effectiveness; controlled alongside product analytics under Privacy choices |
| Usage records | Token counts (in / out / cached), model id, serving upstream, timestamps, latency, cost, and a short error code when a request fails | Billing, the per-request receipts we show you, and spotting requests that keep failing |
| API request observations | Request, account and key identifiers; endpoint, protocol, model, coarse client or SDK family, streaming mode, timestamps, HTTP status, error category and duration. When available, network country, region, city, timezone, network number (ASN), edge location and the source of those location fields | Understanding API traffic, investigating failures and supporting accounts. Retained for up to 400 days; separate from optional website analytics. These observations do not contain raw IP addresses, full user agents, credentials or request content |
| Request counts and setup diagnostics | Daily request counts by coarse client family, refused requests, and the earliest retained authenticated request attempt, including its model, client hint, outcome and error category; no raw user agent or request content in these summaries | Understanding setup failures and providing account support; retained for up to 13 months |
| Signup context and optional setup preferences | Signup route, authentication method, coarse browser and country, timezone, language, key issuance origin, and optional answers about your intended use and how you found MiniRouter | Showing relevant setup instructions and understanding account activation. Questions are optional; answers are kept separately from observed referral and client data |
| Public model usage rankings | Fixed daily model-level token and successful-request aggregates; no account identifiers, API keys or request content | Helping visitors understand model adoption. Only linked accounts with product analytics enabled can contribute, and explicitly excluded internal/test accounts are omitted. Model/day groups require at least 10 eligible requests and three accounts. Opting out excludes future publications; already published aggregates are not rewritten |
| Ledger entries | Every credit and debit, double-entry | Your balance is a sum over this ledger; you can export it as CSV |
| Deposit transactions | Chain, transaction hash, amount, sending and receiving addresses | Crediting your deposit and answering “I sent it but don’t see it” |
| API keys | A hash of the key and its prefix — never the key itself | Authentication; the plaintext key is shown once and not kept |
| Sign-in sessions | IP address and user agent | Account security |
| Terms acceptance | Terms version and when you accepted | Knowing which terms apply to your account |
| Account context | Sign-up method, referral code, language, country, timezone and last dashboard visit | Account email |
| Email (optional) | A verified email address, your account-message preferences, and — only if you separately opt in — the time and source of your product-update consent plus its Resend contact-sync status | Authentication, account recovery, requested alerts, important service messages, getting-started tips for new accounts and account help and tips (both on until you turn them off), and optional product updates |
| Account summary | Figures derived from the records above: weekly spend, main model, client software, refused and failed request counts, timezone and last dashboard visit. No request content | Choosing at most one help or tip message at a time, by email, browser push or dashboard notice; turn them off in Settings |
| Email engagement | Delivery, open and click times | Improving account email |
| Feedback and FAQ questions | What you send us | Answering you and improving MiniRouter |
| Supplier introductions | Company, website, work email, offering, optional models, regions and notes, a submission reference and timestamp | Maintaining a private supplier interest list and discussing potential inference supply; joining does not subscribe you to product updates |
| Screening results | Pass/fail of sanctions-list checks on direct deposits | The legal floor for operating the direct rail; see /pay/no-kyc |
That table is exhaustive. If a category is not in it, we do not hold it — there is no name, no phone number, no ID document, no device fingerprint collected for accountless access. Request content may itself contain personal information supplied by the caller.
Third parties
#Cloudflare R2 stores template videos. Cloudflare Turnstile protects public forms from abuse. Verification sends a challenge token and, when available, the request IP address to Cloudflare. Supplier form answers are not included.
Public pages send page-view data to Vercel Web Analytics. Vercel documents this as cookie-free, first-party analytics that cannot track a visitor across different sites. We do not attach an account identifier, wallet, email, key, prompt, completion, or billing record to those events.
Separately, unless you turn it off under Privacy choices, public pages and key/setup screens send a small allowlisted product event to our own domain. We keep the pseudonymous source record in MiniRouter’s database and, when remote reporting is enabled, project it server-to-server to an EU-resident Mixpanel project. This product event pipeline uses no Mixpanel browser SDK, session recorder, or fingerprinting script. We do not send Mixpanel an IP address, full user agent, raw referrer URL, account identifier, wallet, email, key, prompt, or completion.
Google Ads measurement is also on by default. Its Google tag measures advertising effectiveness and can read or write advertising cookies. Google receives visit, browser and network information, including your IP address. When you create an account or a top-up is confirmed, the tag reports it to Google; a top-up includes its amount, currency and a random payment reference. We do not attach account identifiers, wallets, emails, API keys, prompts or completions to Google tag events. Turning analytics off under Privacy choices also denies Google advertising storage, advertising user data and ad personalization. A tag already loaded on the page may still send cookieless signals. See how Google uses information from partner sites.
When a measured visit creates its first account and API key, we store an immutable account-to-visitor acquisition link in MiniRouter’s own database for the retention window. It is used to derive signup, key, payment, successful-request, and billed-usage events. Financial analytics records actual settled credit and consumed credit separately. Location is coarse platform-provided geography; browser information is limited to product families, without versions. The local account ID and that linkage are never exported to Mixpanel.
We use Resend to deliver email. Resend processes the recipient address and delivery status for account email, getting-started tips and account help and tips. If you separately opt in to Product updates, we also send it your subscription, campaign-delivery, and unsubscribe state. Resend may retain a suppression record after you unsubscribe so the address is not accidentally mailed again.
If you send the model ID minirouter/fusion, a classifier run by TypeSafe reads a shortened copy of your system prompt, your latest message and your tool names to choose the model. Tool results, images and replies are not sent. No other model ID is classified. Detail on /docs/fusion.
To decide whether an account tip is worth sending, the same TypeSafe classifier reads your account summary. It never receives your email address, account ID, keys or request content.
Your requests necessarily reach the upstream provider that serves the model; the provider sees the prompt content, under its own policy. On the aggregator payment rail, Relay screens transactions against Chainalysis — that is their infrastructure, stated precisely on /pay/no-kyc. We do not sell or rent stored data, and do not disclose it beyond the processors and payment infrastructure named above, or what you ask us to publish as a template.
Retention, requests and changes
#Usage and ledger records are kept for as long as the balance they account for exists, because they are the balance. Deposit transaction records are kept as long as the law governing payments requires. There is deliberately little account information for accountless keys. API request observations expire after 400 days and are removed when their account is deleted. Network location can describe a VPN, proxy or server rather than your physical location. Website Privacy choices do not disable these operational observations. Private request traces expire after 30 days and are deleted by the retention worker; backups follow their infrastructure retention settings. We keep a one-way digest of prompts for text-to-video jobs with those job records for 13 months. It is used to check a template’s prompt made its video. Request content may contain personal information supplied by callers. Request trace capture has no opt-out. The Privacy choices control lets you turn off MiniRouter product analytics and Google Ads measurement, which are on by default, or delete MiniRouter’s local pseudonymous record and request deletion from its Mixpanel reporting projection. Mixpanel processes that request asynchronously and says it may take up to 30 days; we retain the pseudonymous completion evidence for 13 months, while pending or failed deletion work is never aged away. Other product analytics records expire after 13 months. The control does not disable aggregate Vercel page views. Deleting analytics data requests deletion of MiniRouter and Mixpanel records; it does not delete data already held by Google. Google’s linked privacy information explains its data controls. This does not delete financial or usage records kept for billing and payment obligations. You can turn Product updates off in dashboard settings or use the unsubscribe link in an email. We then remove the address from MiniRouter’s product-update audience; Resend may keep the suppression record described above.
Supplier introductions remain in our private supplier list until removed. They have no automatic expiry and are not published or sent to product analytics. Contact the address below to request correction or removal, including your submission reference if available. Backup copies follow infrastructure retention settings.
Questions or requests: privacy@minirouter.sh. Material changes to this policy are dated in the changelog.