Privacy Policy
Effective date: 12 November 2026
Last updated: 12 November 2026
This Privacy Policy explains how Studio Router ("Studio Router", "we", "us") collects, uses and shares personal data when you use studiorouter.com, api.studiorouter.com, the Studio Router API, the MCP server and related services (the "Service").
We are the data controller for the account, billing and usage data described below. For data that a model provider receives and processes for its own purposes, that provider may be an independent controller; its privacy policy applies.
If you have questions or want to exercise your rights, contact support@studiorouter.com.
1. What we collect
Account and sign-in data
- Your name, email address and profile image from Google, through our authentication provider.
- Your authentication provider user ID, Google account identifier, email verification status, and sign-in metadata such as timestamps and IP address.
- Account settings, including your default project and preferences.
We do not receive or store your Google password.
Payment and billing data
- Your payment processor customer ID, payment method brand, last four digits and expiry date.
- Billing and tax information, where you provide them.
- Top-up history, amounts, currency, service fees, refunds and chargebacks.
- Card fingerprint and risk signals used for fraud prevention.
- Dispute and chargeback records.
Card numbers are entered on our payment processor's checkout and are not stored by us. Our payment processor may act as an independent controller for fraud prevention and payment processing; see its privacy policy.
API keys and usage data
- API key names, prefixes, creation and last-used times. We store a SHA-256 hash of the key, never the key itself.
- The requests you make: model, mode, parameters, prompts, the provider chosen, fallback attempts, status, timings, estimated and actual cost, and error details.
- IP address, user agent, request IDs and similar technical data.
- MCP and OAuth connection data, where you connect an agent.
Content
- Inputs you submit: prompts, images, videos, audio and files, including copies we make of media you link to.
- Outputs we generate and store for you.
- Projects, saved settings, webhook URLs and metadata you attach to jobs.
- Moderation decisions, probabilities and the model version that made them. For requests that moderation blocks or flags as borderline, we also keep the prompt and the links to its inputs, so a person can review the decision.
Support and community
- Emails, Discord messages and other communications you send us.
- Information you choose to share when reporting a problem or a content violation.
2. Why we use it, and our legal bases
| Purpose | Data | Legal basis |
|---|---|---|
| Create and manage your account, authenticate you, and provide the Service | Account, usage, content | Performance of a contract (GDPR Art. 6(1)(b)) |
| Route requests, generate outputs, store files, and show your job history | Usage, content | Contract |
| Process top-ups, keep invoices, and manage credits and refunds | Payment, account, usage | Contract; legal obligation (Art. 6(1)(c)) for tax and accounting |
| Prevent fraud, card testing, abuse and unauthorised access | Account, payment, usage, technical logs | Legitimate interests (Art. 6(1)(f)); legal obligation where required |
| Moderate prompts and outputs, enforce our Content Policy, and keep the Service safe | Content, moderation records, account, usage | Legitimate interests; legal obligation for reporting certain content |
| Provide support and respond to complaints | Account, support communications | Contract; legitimate interests |
| Debug, secure and improve the Service, including error tracking, operational alerts and basic usage analytics | Usage, technical logs, error data, analytics events | Legitimate interests |
| Comply with legal requests and protect legal rights | Any relevant data | Legal obligation; legitimate interests |
| Send service emails (receipts, security alerts, material changes) | Account, payment | Contract; legal obligation |
| Send product news or marketing (if you opt in) | Account | Consent (Art. 6(1)(a)), which you can withdraw at any time |
We do not sell your personal data. We do not use your Content to train our own models. We do not use your Content for advertising.
Where we rely on legitimate interests, we have considered whether those interests are overridden by your rights. You can object at any time (see section 7).
3. Who we share it with
Model providers. To fulfil a request, we send the prompt and inputs to the model provider that serves it. The providers we use are listed on our models page. They process the request under their own terms and privacy policies, and may keep it for their own purposes, including abuse detection and model improvement. We do not send your email, payment details or billing details to model providers unless a provider needs them to process a payment or comply with law.
Moderation provider. We send prompts and, where relevant, input images to a third-party moderation service that checks them against our Content Policy. We log the decision, probabilities, latency and model version in our moderation log. For blocked or borderline requests, the log also keeps the prompt and input links for 90 days so a person can review the decision.
Service providers. We use providers for authentication, payment processing, cloud hosting and storage, database hosting, email and support. They process data on our instructions or, in some cases (such as our payment processor's fraud screening), as independent controllers under their own terms.
Problem reports and requests. When you report a problem or request a model or feature, from the website or through your agent, we store it with your account id and post it to a private channel of our team's Discord workspace, which only our team can read. We do not include your email there. Discord processes it under its own terms.
Community. If you join our Discord server, Discord processes your data under its own privacy policy.
Professional advisers and authorities. We may share data with lawyers, accountants, auditors and insurers where necessary, and with regulators, law enforcement or other authorities where the law requires it or where we believe disclosure is necessary to protect someone's safety or our rights.
A successor. If we merge with, are acquired by, or sell our business or assets, personal data may be transferred to the successor, subject to this Privacy Policy.
Aggregated information. We may publish aggregated, non-identifying statistics about usage of the Service.
4. International transfers
Some of our providers process data outside your country. Where required, we use appropriate safeguards, such as an adequacy decision or standard contractual clauses approved by the relevant authorities. You can ask us for more information about the safeguards we use.
5. How long we keep data
| Data | Retention |
|---|---|
| Account and profile data | While your account is active, then deleted within 30 days of closure |
| Billing, invoice and tax records | 10 years after the end of the relevant tax year, as required by applicable tax law |
| Jobs, prompts, inputs and outputs | Until you ask us to delete them or close your account; deleted within 30 days of a valid request |
| Content above your storage quota | Deleted after reasonable notice |
| Uploads that no generation uses | Deleted automatically after 24 hours |
| Upload links | Deleted 7 days after they expire |
| Moderation and safety records | Up to 2 years, or longer if needed for a legal claim or an ongoing investigation. The prompt and input links of a blocked or borderline request: 90 days |
| Analytics and error-tracking events | Up to 1 year |
| Operational alerts | Up to 1 year |
| Support communications | Up to 2 years after the conversation ends |
| Problem reports and model or feature requests | Up to 2 years |
| Server and security logs | Up to 90 days, unless needed for a security investigation |
| Backups | Up to 90 days |
| Dispute and chargeback evidence | 2 years after the dispute is resolved |
| Cookie and local-storage data | Until the cookie expires, you clear it, or you sign out |
We may keep data longer where the law requires it, where a legal claim is pending, or where we need it to protect the Service or someone's safety. When we no longer need data, we delete it or anonymise it.
6. How we protect it
We use HTTPS in transit, access controls, hashed API keys, least-privilege access for staff, and encryption at rest where our providers offer it. We monitor for abuse and security incidents. No system is completely secure, and we cannot guarantee that unauthorised access will never happen.
If we become aware of a personal-data breach that is likely to result in a risk to your rights, we will notify the competent supervisory authority within 72 hours where required, and tell you without undue delay if the breach is likely to affect you.
7. Your rights
If you are in the EEA, the UK or another jurisdiction with similar laws, you have the right to:
- Access the personal data we hold about you.
- Correct inaccurate or incomplete data.
- Delete data we no longer need, in the circumstances the law provides.
- Restrict how we use your data while a dispute is resolved.
- Port data you gave us in a structured, machine-readable format.
- Object to processing based on our legitimate interests.
- Withdraw consent at any time, without affecting processing that already happened.
- Complain to a supervisory authority.
To exercise a right, email support@studiorouter.com from the email address on your account. We may ask for information to verify your identity. We will respond within one month, and may extend that by two months for complex requests, telling you why.
Moderation may automatically block a request. If we suspend or terminate your account, you can appeal and a person will review the decision, as described in the Content Policy. Where a decision is based solely on automated processing and produces legal or similarly significant effects for you, you can ask us for human review.
You can also ask us to delete individual jobs, inputs or outputs, or to close your account, by emailing support@studiorouter.com.
If you are in the EEA or the UK, you can complain to your local supervisory authority.
8. Cookies and local storage
We use only essential cookies and local storage to run the Service:
- Our authentication provider sets cookies to keep you signed in and to protect your session.
- We store your light or dark theme choice in your browser's local storage.
- Our payment processor sets cookies on its checkout page when you pay.
We do not use advertising cookies, cross-site tracking pixels, or analytics cookies. Our website analytics runs in cookieless mode. We will never send prompts, uploads, outputs or API keys to an analytics provider.
Your browser may let you block or delete cookies. Blocking essential cookies will prevent you from signing in.
9. Children
The Service is for adults. You must be at least 18 to use it, and we do not knowingly collect personal data from anyone under 18. If we learn that we have collected data from a child, we will delete it. If you believe a child has used the Service, contact support@studiorouter.com.
Generating any sexual content involving a minor is strictly prohibited and is treated as a serious safety matter under our Content Policy, independently of this section.
10. Changes to this policy
We may update this policy from time to time. The current version is always on this page, with the effective date at the top. For material changes, we will give notice by email or in the Service at least 14 days before the change takes effect, unless the change is required by law or is urgent for security reasons. If you do not agree, you may stop using the Service and request a refund of unused credit that has not expired.
11. Contact
Studio Router
support@studiorouter.com
Discord: discord.gg/FcbrZwYCD