Xiaomi MiMo Chat
The MiMo product site currently advertises a browser chat route alongside its API and desktop products.
Score calculation
(1 + 6 + 2 + 1 + 7) ÷ 5 = 3.4
5 of six dimensions rated. Unrated dimensions are excluded from the average.
Full scoring method ↗Setup details
Xiaomi MiMo’s no-setup browser chat entry point; the separately documented API and desktop products are excluded.
What fits your needs
Xiaomi MiMo’s no-setup browser chat entry point; the separately documented API and desktop products are excluded.
Fit
Try MiMo in a browser without wiring a client or managing API credentials.
Tradeoffs to expect
Tradeoff
The product index separates chat from the API and desktop app; the chat route’s exact model and quota are not stated on that page.
How to switch
Getting started
Open MiMo Chat from the product site and verify current access and account requirements in the live interface.
Practical questions
Model selection
The public product page confirms a Chat route but does not specify its exact model selector or route-specific quota.
This grades published energy practices, not the service’s actual footprint.
See the evidence
The reviewed materials define the MiMo browser chat and its functions but provide no service-specific reporting on electricity, emissions, water, sourcing, or resource-reduction controls. Missing measurements don’t show high consumption.
1 + 0 reporting + 0 electricity + 0 controls = 1/10. This grades documented practices and transparency.
No comparable service-level electricity, emissions, water, location mix, or independently reviewed footprint is established in these sources.
- Reporting0/3
- No service-specific operating boundary or footprint disclosure appears in the reviewed product material.
- Electricity sourcing0/3
- No route-specific clean-electricity sourcing or hourly power evidence is established.
- Resource controls0/3
- No route-specific measured efficiency or documented resource-reduction control is established.
Water disclosure
Water reporting has not been assessed for this choice.
The hosted route does not identify one fixed model and training data.
See the evidence
This MiMo browser chat can expose multiple models or change its model selection over time. The product page is not a source-specific training-data and permissions record for every model served through the route.
Select the exact model and version, then review its training sources, permissions, creator controls, and any API-specific data terms.
The published MiMo policy covers its services and names prompt processing, a no-training-without-consent rule, and retention principles.
See the evidence
Xiaomi’s MiMo privacy policy describes processing of user-provided text and media to respond with the selected model and says prompts will not be used for model training or other purposes without prior consent. It also permits analytics cookies and partner sharing and retains data for service purposes or legal requirements rather than one fixed period.
The policy offers concrete limits and user control, but broad retention, telemetry, and unspecified chat-model routing temper the rating.
The site index does not identify the exact model used by each chat session, a fixed conversation deletion period, or any separate consumer-chat exceptions to the policy.
This is a hosted product route; its interface documentation does not disclose the hosted model implementation or grant access to its weights.
See the evidence
The reviewed MiMo browser chat materials describe a hosted service, without publishing the service implementation or checkpoint weights for this route. Its openness rating concerns access to this product surface, not any separately released model family.
A hosted interface is documented, but source code, training artifacts, and route-specific downloadable weights are not established in these sources.
The exact model checkpoint and any route-specific release artifacts may change; this rating covers the named service route.
No model-specific worker safeguards are established for Xiaomi MiMo in the reviewed model sources.
See the evidence
The model release pages describe weights and technical properties, not conditions for employees, data annotators, evaluators, moderators, or infrastructure contractors. This is a source-bounded disclosure gap, not evidence of mistreatment. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
1 base + 0 conditions + 0 worker voice/remedy + 0 evidence/follow-through = 1/10; this is a disclosure finding, not proof of abuse.
Worker locations, pay and conditions, supplier coverage, voice mechanisms, labor audits, and remediation outcomes are not established by these model-release sources.
- Pay & conditions0/3
- No worker-level conditions or supply-chain safeguards are established in this model-family source set. This is a disclosure gap, not proof of mistreatment.
- Worker voice & remedy0/3
- The model sources do not document a worker voice or remedy mechanism for data, evaluation, or infrastructure labor.
- Evidence & follow-through0/3
- No independent worker-level audit or remediation outcome is established in the reviewed model sources.
No route-specific military relationship or end-use oversight was established for this Xiaomi MiMo’s no-setup browser chat entry point; the separately documented API and desktop products are excluded..
See the evidence
The reviewed Xiaomi MiMo Chat materials describe user access, features, or account rules but don’t show a military customer, military deployment, or a model-specific restriction on military use. This route finding does not resolve the wider company’s government work.
7 base + 0 safeguard adjustment = 7/10 (0 of 9 safeguard points; every 3 adds 1). No military relationship was established in the cited sources. This ranks above known defense ties without claiming a verified clean record.
A separate, current company-level review is needed for defense contracts; downstream deployments and any customer-specific safeguards are not established here.
- Use restrictions0/4
- The cited route terms don’t spell out a specific restriction on military or surveillance use.
- Enforcement & oversight0/3
- The cited route terms don’t show route-level enforcement of military end-use restrictions.
- Relationship disclosure0/2
- The cited route material does not disclose a military customer or deployment for this route.
The cited Xiaomi MiMo Chat documentation covers product/API terms, but does not identify a military customer, deployment, or end-use restriction.
Military rubric ↗Xiaomi MiMo is not named in the two official BNC campaign lists checked. This is a limited list check, not BDS approval.
See the evidence
The official BNC consumer boycott/pressure guide and No Tech campaign page do not name Xiaomi MiMo among their current targets. BDS uses selective campaigns, so absence from these lists is neutral and should not be read as a clean record or approval. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.
This check covers only named targets in the two cited BNC campaigns; it does not cover all BDS campaigns, local groups, investments, suppliers, or downstream hosts. Lists and ownership may change.