Privacy Policy
## Privacy Policy
**Effective date: November 7, 2026**
Max Router ("Max Router", "we", "us", or "our") operates [maxrouterai.com](https://maxrouterai.com/) and its associated API and account services. You can contact us about privacy at [support@maxrouterai.com](mailto:support@maxrouterai.com).
This policy explains the information we process when you visit the website, create an account, use our API or contact us. The information we process depends on the features you use and the model or service provider that handles your request.
### 1. Information we process
- **Account and authentication information:** username, display name, email address, account settings and identifiers. If you use a password, we store a password hash rather than the plaintext password. We also process session and authentication information to sign you in and secure your account.
- **Third-party sign-in information:** if you choose Google or GitHub sign-in, we receive information from that provider as described in Section 2. Whether a login method is available depends on its deployment status.
- **API requests and outputs:** the prompts, messages, files or file URLs, images, audio, video, parameters, responses and other content you choose to send or generate. The particular content depends on your request and the selected model. Task records and diagnostic traces may retain request parameters, text, results or links to generated content; do not assume all content is immediately discarded after a request.
- **Usage, transaction and security records:** model and channel used, timestamps, request and task identifiers, usage measurements, charges, account balance and transaction history, response status, error details, and, depending on the feature or configuration, IP address, browser and device information.
- **Communications:** information you provide when contacting us for support or to exercise privacy rights.
Please avoid including sensitive personal information or another person’s information in prompts and files unless you have an appropriate reason and the required permissions to do so. Model outputs may contain personal information and can be inaccurate.
### 2. Google and GitHub sign-in
If you choose **Google sign-in**, we request the OpenID Connect `openid`, `email` and `profile` scopes. Google may provide your Google account identifier, verified email address, display name and basic profile information. We verify the response and use the information needed to create or recognize your Max Router account, authenticate you, maintain account security and communicate about your account. We store the account identifier and, where used for your account, your email and display name with account records. We do not receive your Google password. We do not use Google account data obtained for sign-in to train AI models or serve advertising. We do not send your Google sign-in profile to a model provider merely because you sign in; if you include such information in an API request, it will be handled as request content.
If you choose **GitHub sign-in**, GitHub may provide your GitHub account identifier, username, display name and public or authorized email information. We use the information needed to identify and authenticate your account and protect account security. We do not receive your GitHub password.
Google and GitHub also process information under their own policies when you use their services. You can manage the access you have granted from your [Google account permissions](https://myaccount.google.com/permissions) or [GitHub authorized applications](https://github.com/settings/applications). Revoking access prevents future authorization but does not itself remove copies already stored by Max Router; see Section 7 for a deletion request.
### 3. How we use information
We process information to provide accounts and requested API functionality; route and fulfill requests; return and display task results; measure usage and apply charges; communicate verification codes, security messages and service notices; diagnose failures; prevent abuse and unauthorized access; maintain and restore the service; respond to requests; and meet applicable legal obligations.
Where data protection law requires a legal basis, the basis depends on the processing: providing the service or taking steps you request before using it; legitimate interests such as operating and securing the service, subject to your rights; complying with legal obligations; or your consent where consent is required. You may withdraw consent where applicable without affecting processing before withdrawal.
### 4. Model providers and other recipients
To fulfill a request, Max Router sends the request content and the parameters needed to process it to the selected or automatically routed upstream provider. Our current integrations include **KIE**; depending on the selected channel, KIE or another provider may involve additional model or infrastructure providers. Their treatment of input and output, including retention and possible model training or improvement, is governed by the relevant provider’s terms, settings and agreements. We cannot promise that all upstream providers exclude your content from training. Review the terms for the model and provider before submitting sensitive information.
We also use service providers as needed to operate the service, including **Cloudflare** for website infrastructure and encrypted object-storage backups, **Resend** for transactional email, hosting and infrastructure providers, and **Google** or **GitHub** when you select their sign-in service. A provider receives the information needed for the service it performs; for example, Resend receives the recipient address and message content for account emails. Payment service providers may receive transaction information if a payment feature is used. We may also disclose information when legally required or reasonably necessary to protect users, the service or legal rights.
### 5. Cookies and local storage
We use necessary cookies and similar browser storage for sign-in sessions, authorization security and interface preferences. You can manage cookies through your browser; blocking necessary cookies may prevent sign-in or other features from working. Third-party services you choose may apply their own cookies or policies.
### 6. Storage, retention and security
We retain account information, usage and transaction records, task data and security records according to their purpose, including providing the service, resolving disputes, security, and legal or accounting requirements. Current production configuration does **not** set a general automatic deletion schedule for all such records. A fixed retention period has not yet been established for every category.
The self-service account deletion action deactivates the account and revokes access, but it does **not** immediately erase every record: account information, usage and task records, and copies in encrypted backups may remain. Encrypted production database backups are stored locally and in a private Cloudflare R2 bucket. The backup process normally retains only the latest successful encrypted production database backup on the server. A verified copy is uploaded to a private Cloudflare R2 bucket. Older cloud backups are protected by a 30-day deletion lock and may remain until that protection expires or cleanup succeeds. A request to erase information will be reviewed against the applicable retention requirements and the technical handling of active records and backups. Do not assume all copies are removed immediately when you close an account.
We use HTTPS for the website, access controls, password hashing and encrypted database backups. No method of storage or transmission is completely secure.
### 7. Your choices and privacy rights
You can review or change available account information in your account settings. You can initiate account deletion there, subject to identity verification; see Section 6 for the effect on retained records and backups. To request access, correction, deletion, restriction, objection, portability or withdrawal of consent where available under applicable law, contact [support@maxrouterai.com](mailto:support@maxrouterai.com). We may need to verify your identity and may retain or restrict handling of information where permitted or required by law. Depending on your location, you may also complain to the relevant data-protection authority.
**Right to object:** where applicable law gives you the right to object to processing based on legitimate interests, you can exercise it by contacting us at the address above.
### 8. International transfers
The service and its providers may process information in countries or regions different from your own. The location depends on the hosting, routing, backup and provider services used. Where applicable law requires transfer safeguards, the operator must identify and apply the relevant safeguards before the transfer.
### 9. Children
The service is not directed at children. If you believe a child has provided personal information without required authorization, contact us so we can review the situation under applicable law.
### 10. Changes and contact
We may update this policy as the service or its data practices change. The current version and its effective date will be displayed on this page. Where required, we will give additional notice or request consent before a material change. For privacy questions or requests, contact [support@maxrouterai.com](mailto:support@maxrouterai.com).