Privacy Policy
Last updated:
How Mouter handles account, tool-task and payment information, and how to exercise your privacy rights.
Contents
1. Scope and contact
This policy explains how Mouter (“we”, “us”) collects, uses, retains and discloses personal information when providing mouter.ai, accounts, APIs, MCP connections and related tools. Mouter is the operating name used for this service.
We are responsible for the account administration, service operations and related personal-information processing described here. Send privacy questions, rights requests and support enquiries to support@mouter.ai. Describe your request and include the email address or account ID needed to identify your account.
This policy explains our data practices. Reading it or continuing to use the service does not, by itself, consent to optional marketing or any processing that requires a separate choice.
2. Information we process
The information involved depends on the features you use. Public pages can be browsed without signing in; accounts, payments and tool calls require the relevant information.
| Category | Information and sources |
|---|---|
| Account and verification | The email address and password you submit for email-and-password registration, sign-in or reauthentication, together with your account ID, display name, creation time, login sessions, API credentials and linked login details. Mouter stores password hashes, not plaintext passwords. Email-and-password registration does not currently verify ownership of the email address. If you choose Google sign-in or account linking, we receive the identity identifier, Google-verified email address and basic profile you authorize. |
| Tool tasks and content | Prompts, text, links, identifiers, images, audio, video or other parameters submitted by you or an authorized client, together with task IDs, status, results, errors, timestamps and usage. The fields depend on the selected tool. |
| Payments and credit | Top-up selections, order identifiers, amounts, currency, payment and refund status, transaction times, available credit and usage records. Some information comes from the payment service. Card details are processed in its checkout environment; Mouter web pages do not collect full card numbers or security codes. |
| Device, access and security | IP addresses, browser and operating-system information, device type, request times, page addresses, referrers, error and security logs, and usage statistics. Approximate location may be inferred from network information; we do not request precise device-location permission. |
| Communications, reports and preferences | Support emails, feedback and attachments you send, content reports, appeals and records of their review and handling, necessary identity-verification information supplied for account recovery, language preferences, and the choices and associated records when you voluntarily subscribe to marketing. |
3. Purposes and legal bases
We use personal information for the purposes below. Where the GDPR or another law requires a legal basis, the basis depends on the activity. When relying on legitimate interests, we consider your reasonable privacy expectations and the effect on your rights.
| Purpose | Legal basis |
|---|---|
| Creating accounts, verifying identity and delivering APIs, MCP connections and tool tasks | Performing the service contract you request, or taking necessary steps before entering it. |
| Processing top-ups, confirming payments, measuring usage and maintaining billing records | Performing a contract; meeting applicable financial, tax or other legal duties. |
| Answering enquiries, troubleshooting and resolving disputes | Performing a contract; legitimate interests in resolving service issues and protecting the service and legal rights. |
| Sending billing, security and important service notices | Performing a contract, meeting legal duties, or legitimate interests in account and service security. |
| Preventing fraud, abuse and unauthorized access, investigating content reports and handling appeals | Legitimate interests in protecting users and the service; applicable legal duties. |
| Understanding website use and improving reliability and experience | Legitimate interests in improving the service; consent where required by law. |
| Sending optional product updates or offers | Your separate subscription consent, which you may withdraw. |
4. Tools, AI and authorized clients
Completing a task may require sending relevant inputs to the model, content or data provider used by that tool and receiving its results. Data flows differ by tool: a generation task may involve prompts and reference media, while a lookup may involve a public-content link or account identifier. Submit only information necessary for the task that you are entitled to use.
Mouter does not use your task inputs or results to train models. This commitment concerns Mouter's own processing; it does not mean every upstream service has identical retention or training rules. To understand a tool's providers and data-use arrangements, contact support@mouter.ai before submitting content.
A client connected through MCP, an API key or another authorization can submit tasks and read relevant results within its permissions. It may separately retain content you provide and results it receives under its own policy. Protect your credentials and authorize only clients you trust.
If a task contains someone else's personal information, ensure you may submit it and have met any applicable notice or authorization requirements. Do not include identity documents, full payment-card details, health records or other sensitive information unrelated to the task.
5. Cookies and browser storage
Browser settings can manage cookies and site storage, which may affect some functions.
Google sign-in and Cloudflare verification may generate network requests to third parties. Their services and policy links are described below.
| Purpose | Use and choices |
|---|---|
| Sign-in and security | Session cookies keep you signed in. Temporary browser storage supports login return paths, authorization and payment retries. Restricting these necessary functions may prevent sign-in, authorization or payment flows from completing. |
| Language preference | Your language is reflected in the address of the page you visit. Switching language changes the address; no language record is written in your browser. |
| Registration source | When a link contains exactly one valid utm_source parameter, local browser storage records the normalized source label (trimmed and lowercased) and the time it was recorded. The record is kept for 30 days from that time and later sources do not replace it. Nothing is recorded when browser storage is unavailable, and invalid, duplicated, corrupted or implausibly dated records are discarded. If you register, sign in or start Google sign-in during this period, the label is submitted with the request. It is saved to your account record only when a new account is created; existing accounts are not changed. It is used only to understand registration channels and does not affect account permissions, prices or quota. You can clear this record in your browser settings. |
6. Sharing and disclosure
We do not sell your personal information, including a sale as defined by applicable law. We disclose relevant information to deliver the service, meet legal duties, protect legal rights or follow your authorization.
Information provided to a service provider should match the service it performs. Payment and identity providers may also process information for their own applicable security, financial or legal responsibilities.
When handling a content report or appeal, we review relevant inputs, results, task records and reporting material only as necessary to investigate the issue, with access limited to the people handling it. If an upstream tool provider needs to assist, we share only the necessary task or content information. We do not disclose a reporter’s identity or contact details to the reported user or unrelated third parties without consent, a legal requirement or a lawful necessity to resolve a dispute.
- Legal requirements: necessary disclosures under applicable law, a court order or a valid request from a competent authority.
- Protecting rights: necessary and appropriate disclosures to investigate abuse, resolve disputes or protect users' and the service's legal rights.
- Business changes: necessary information may be shared in a merger, acquisition or asset transfer, with legally required notice and continued applicable protection obligations.
- Other purposes: your separate consent will be obtained where required.
| Recipient | Purpose and information |
|---|---|
| Lemon Squeezy | When you check out through Lemon Squeezy, it processes the payment-method and transaction information needed for checkout and returns order and payment status to Mouter. Full payment-card details are handled by the payment service. The provider for your transaction is identified in your checkout and order information. |
| Waffo Pancake | When you check out through Waffo Pancake, it provides checkout and payment-related services, processes payment-method and transaction information, and returns order and payment status to Mouter. Full payment-card details are handled by the payment service. |
| Tencent Cloud and Amazon Web Services (AWS) | Support hosting, storage and infrastructure operations, processing account, task and technical data needed to run the service. |
| Verifies identity when you choose Google sign-in or linking. | |
| Cloudflare | When Turnstile verification is enabled, processes the device, network and interaction signals needed to help prevent fraud and automated abuse. |
| Relevant tool providers and clients you authorize | Receive the inputs, task status and results necessary to execute the selected task or exercise the permissions you grant. |
7. Information security
We protect data through measures including HTTPS transmission, account verification, and session and API-key access controls, and restrict unauthorized operations. Tool execution uses the relevant credentials; account operations are protected by session and request-verification mechanisms.
No network or storage system can guarantee absolute security. Keep passwords, API keys and other credentials private. If you notice unusual access, contact us promptly and disable affected keys.
If a personal-data security incident occurs, we will investigate, take steps to contain its effects and notify relevant authorities and affected people as required by applicable law. Notification recipients and deadlines depend on that law and the incident's risk, rather than the general data-cleanup period in this policy.
8. Retention and account deletion
Retention depends on the time needed to provide the service, the purpose of a record, dispute-resolution needs and applicable law. Indefinite retention of personal information is not our default purpose.
Request account closure or deletion of personal information at support@mouter.ai. After necessary identity verification, account details, task inputs and results, related logs and backups are normally deleted or irreversibly anonymized within 1–3 months. A shorter period applies where the law requires a faster response or deletion; this cleanup period does not extend statutory rights-request deadlines.
- Where a legal duty or specific dispute requires limited data to be retained, retention and use are restricted to what is necessary. The data is deleted or anonymized when that basis no longer applies.
- Data awaiting backup cleanup is not used for ordinary operations. If a backup is restored, confirmed deletion requirements must be reapplied.
- Records independently retained by a payment service or a third-party client you use are subject to that party's duties and policy. We will assist with relevant requests within our responsibilities.
| Data | Retention approach |
|---|---|
| Account and authorization records | Kept while needed for your account and authorized services, then handled within the closure timeline above, except for portions that must be retained by law. |
| Task inputs, results and execution records | Kept to execute tasks, provide results, reconcile usage and resolve related issues; included in the cleanup following account closure. |
| Transaction and billing records | Kept to reconcile payments, handle refunds or disputes and meet the financial, tax and other duties that actually apply, then deleted or anonymized when those needs and duties end. |
| Support, reports and appeals | Necessary records and evidence are kept as needed to handle enquiries, reports, appeals and related investigations or disputes, then deleted or anonymized. Account-related records are assessed as part of an account-deletion request. |
| Security and backups | Kept to the extent needed for security investigations, operations and recovery. Account-linked information within a deletion request's scope and backups are cleaned up within the timeline above. |
9. Your privacy rights
Depending on your location and applicable law, you may request information about and access to your data, a copy, correction, deletion, restricted processing, a portable format, objection to certain processing or withdrawal of consent. Withdrawal does not affect the lawfulness of consent-based processing before withdrawal.
- Email support@mouter.ai and explain the right you wish to exercise. We request only information needed to verify identity and handle the request. An authorized agent may act for you where permitted by law.
- Where the GDPR applies, we act without undue delay and generally reply within one month of receiving a request. If a lawful extension is needed, we explain its reasons and duration within the original period.
- Where the California CCPA applies, requests to know, delete or correct generally receive a response within 45 calendar days, with notice of any legally permitted extension. Other requests follow their applicable deadlines. You may also have rights to opt out of sale or sharing, limit certain uses of sensitive information, and avoid unlawful discrimination for exercising privacy rights.
- If a request cannot be fully met, we will explain the applicable reason. You may challenge our response by contacting us or complain to the competent data-protection or privacy authority. Other applicable appeal and remedy rights remain available.
10. Marketing communications
We send marketing emails, such as product updates, feature announcements or offers, only after you separately choose to subscribe. Subscription is not required to register, sign in or use core services.
Withdraw your subscription by contacting support@mouter.ai or by using an unsubscribe link provided in a marketing email, if available. The corresponding marketing will stop; transaction receipts, security alerts and necessary service or policy notices may still be sent.
11. International processing
Mouter serves users including those in the United States, Europe, Japan and Singapore. We use Tencent Cloud overseas services and AWS infrastructure located in Singapore. Payment, identity and tool providers may also process data outside your country or region.
Data-protection laws differ between locations. Cross-border processing remains subject to this policy and applicable law. Personal data requiring transfer safeguards should be transferred only after the relevant legal conditions are met, such as an applicable adequacy decision, standard contractual clauses or another legally permitted mechanism.
Contact support@mouter.ai to learn about processing locations, recipients or applicable safeguards relevant to your account or a tool you use.
12. Children
The service is intended only for people aged 18 or older. We do not knowingly collect personal information from anyone under 18.
If you believe a minor has provided personal information to us, contact support@mouter.ai. Once verified, we will stop the relevant processing and delete information that should not be retained, as required by law.
13. Third-party policies
When you visit a third-party checkout, use third-party identity verification or connect a client of your choice, the other party's independent processing is governed by its own policy. This policy does not replace those policies or reduce Mouter's responsibility for its own processing.
The links below provide the main providers' policies.
14. Policy updates
We may update this policy when the service or our data practices change and will revise the date shown on this page. For changes materially affecting your rights, we will provide appropriate notice through the website or your account email before they take effect, except where the law requires immediate action.
If new processing requires your consent, we will seek it separately rather than treating continued use as a substitute. Contact support@mouter.ai with questions about this policy.