Model and payment permissions are shown in your account. Account console
VIMUROUTE / SERVICE INFORMATION

Terms, acceptable use and privacy

Current account services, user responsibilities and data handling. Updated November 5, 2026.

Service terms

1. Service name and contact

VimuRoute (VM) is the public operating name and service brand used on this website. It is not a representation that a company is registered under that name. Questions about the service or these terms can be sent to the contact below.

Support, privacy requests, reports and appeals: support@vimuroute.com

2. Current service scope

Registration, email/password sign-in, Google/GitHub sign-in, account settings, project-key records and the account ledger are available. Email accounts require verification. Model and feature access depends on the permissions shown in your account. The directory includes model information and quoted rates; it does not guarantee that every model, client or feature is available to every account.

3. Account and key responsibilities

Provide accurate account information and use materials you are entitled to process. Protect your password and keys, and notify support if access may be compromised. Do not impersonate others, use stolen credentials, share access without authorization, interfere with the service or bypass security restrictions. Each complete project key is shown only when created; later responses show a masked identifier. Keys can be paused or permanently revoked.

4. Prices, payments and refunds

New accounts start with zero balance. Available top-up amounts and model permissions are shown in the account console. The console shows the permitted purchase amount, and the hosted checkout shows the final charge and applicable taxes. VimuRoute selling rates are listed on the pricing page. Any supplier reference prices are separate from those selling rates. No recurring subscription or automatic top-up is enabled. Contact support for refund or cancellation enquiries; handling is manual and depends on the verified order and payment-platform result.

5. Violations and responsibility

Use the service in accordance with the acceptable-use policy below. Depending on the facts and severity, we may issue a warning, request an explanation or correction, restrict affected workspace access, pause or revoke involved project keys, or suspend the affected account service. Serious or repeated abuse may result in termination of that access.

Where practicable, we explain the relevant rule and action. Immediate access restrictions may be necessary for security threats or legal obligations. A report alone does not establish wrongdoing. Users are responsible for unlawful conduct and proven resulting losses as determined by applicable law; these terms do not exclude rights or liabilities that cannot lawfully be excluded. Appeals can be sent to the support address.

6. Service information and updates

The current account service carries no guaranteed uptime or model-output commitment. Information may change as features are verified. Material changes to service scope or data processing will be explained before the changed feature opens, and any consent required by applicable law will be obtained. Publishing model information does not open a paid service.

Read the acceptable-use policy · Read the privacy notice

Acceptable use and content policy

1. Prohibited content and conduct

The following categories are prohibited, including attempts to request, publish, distribute or facilitate them through the service:

Malware, phishing, fraud, credential theft, unlawful surveillance and attempts to bypass safeguards are also prohibited. Do not misrepresent AI-generated material as authentic evidence or authorized professional judgment. Do not submit material belonging to others without the rights needed for the intended use.

2. Current feature boundaries

VimuRoute currently provides model information and account management. It does not accept model prompts or perform live text, image or video generation. A listed Images API model does not create an available image-generation feature. Input/output safety checks, any required Prompt Sift integration and relevant upload-rights checks must be implemented and verified before generation features can open; they are not represented as operational today.

3. Reporting a concern

Send reports to support@vimuroute.com

Provide a page or model ID, time and timezone, any available request identifier, a short description and evidence you are entitled to share. For child-safety or other urgent concerns, state the urgency in the subject. Do not send unlawful material itself, complete API keys, identity documents or bank details. This mailbox is not an emergency-response service.

4. Review and enforcement

Reports are reviewed manually: receive and triage the report, check relevant records, decide whether a rule was violated, and apply an appropriate warning or access/key restriction. Unnecessary personal information is not shared with other users. We explain decisions where practicable and may request further evidence. Confirmed mistakes can be corrected, including restoring access when appropriate. There is no claim of an automated moderation pipeline or a continuously staffed review team for the current account service.

5. Appeals

For reconsideration, email support@vimuroute.com

Identify the disputed decision, give your account email and explain the facts you want reconsidered. We review the explanation and relevant records and communicate the outcome where practicable. We do not promise a separate reviewer or a fixed response time that is not currently staffed.

Privacy notice

1. Service contact

VimuRoute (VM) is the public operating name used for this service and for receiving privacy requests. The brand name is not presented as a registered company name.

Support, privacy requests, reports and appeals: support@vimuroute.com

2. Account information and purposes

We process your email address, chosen display name, account ID, password verifier, verification/recovery records, consent-version records and sign-in sessions to create and protect your account. Sessions may contain IP address and browser information. The account database also holds key metadata and hashes, status changes, timestamps, audit events and ledger records for account management and security. Queries are scoped to the signed-in account.

When you choose Google or GitHub sign-in, that provider supplies an identity identifier, email, display name and optional profile image. The site requests basic identity/email access, not access to email messages or code repositories. OAuth access and refresh tokens are encrypted before database storage. VimuRoute passwords and project-key verifiers are hashed; later account responses do not return full keys or their hashes.

Your browser stores the language preference and a secure sign-in session cookie. Hosting and network services process the access information needed to serve and protect the website. Messages you send to support are processed to answer and document the request. We do not sell personal information or use account data for model training.

3. Service providers

Waffo Pancake · Privacy notice

For model API features enabled in your account, VimuRoute sends the input and model parameters from its server to the configured inference provider, currently QC, and returns the result to your application or client. VimuRoute does not persist the raw prompt or answer text. It retains a keyed request fingerprint, prompt byte length, account and key references, request references, timestamps, usage, upstream metering, status and error codes for duplicate detection, budget control and reconciliation. QC processes these requests under its own terms and privacy rules; VimuRoute does not promise that QC retains no data. For account-enabled top-ups, VimuRoute sends the order identifier, a one-way account identifier hash, product, amount, currency and return URL to Waffo Pancake. Contact and payment information entered at its hosted checkout is processed by that provider. VimuRoute receives signed payment events and keeps order/payment references, amounts, tax, status, timestamps and a payload hash for reconciliation. It does not provide a card-entry form or store complete card numbers or card security codes. Merchant-onboarding information separately supplied by the operator is distinct from customer account information. Material changes to inference or payment providers will be reflected in this notice.

4. Retention and current limitations

Account, key, audit and ledger records remain in the account database while the account service is provided. The current release has no scheduled job that erases all records after a fixed number of days. Support emails remain in the support mailbox until manually removed; no separate automatic expiry is configured. Hosted backups and recovery copies are subject to the hosting provider’s configuration. We do not promise that revoking a key erases an account or its historical records.

Sign-in sessions have a seven-day validity window and may be renewed by active use. Verification and recovery codes expire after ten minutes. Expiry means the credential no longer works; it does not establish that every related database or email record has been physically erased.

To request erasure or closure, use the process below. Following verification, we assess what can be erased or de-identified and whether specific records must be retained for security, disputes or applicable legal obligations. We explain the handling scope and any necessary retention. There is currently no verified automatic account-erasure button or uniform completed deletion schedule. Payment orders, immutable receipts and ledger entries currently remain in the account database without a scheduled automatic deletion date; closure or erasure requests are reviewed manually.

5. Your requests and account closure

Send privacy requests to support@vimuroute.com

You may request access, a copy/export, correction, restriction, withdrawal of consent where relevant, account closure or deletion. Write from your registered email, state the requested action and identify the relevant account. We may verify control through proportionate checks; do not send an identity document or complete key by default. The console already supports key revocation and downloading an account summary.

Requests are handled manually. After checking identity and scope, we explain the processing steps, any information needed, the expected handling time and any lawful retention exception. Unresolved privacy concerns can also be raised with the competent authority where applicable. A deletion request does not itself authorize a charge or activate model/payment services.

6. International processing and safeguards

Our providers use international infrastructure. Resend’s published privacy notice describes processing in the United States. Cloudflare operates globally; the actual D1 database location depends on its creation configuration, and network handling is not the same as database residence. We do not represent that all information remains in mainland China or in one country.

The current controls include HTTPS, account-scoped queries, limited provider permissions, password/key hashing and OAuth-token encryption. Provider processing and safeguards are also governed by their published terms and privacy arrangements. We do not claim an unverified residency setting, contract, certification or deletion guarantee.

Cloudflare · Resend

7. Updates and contact

This notice describes the service currently available. Material changes to data categories, purposes or providers will be explained before the changed processing starts, with any required consent handled separately. For questions, contact the privacy/support address above.