Lumo by Proton
Hosted AI assistant using a changing selection of open-source models on Proton-controlled servers.
Score calculation
(2 + 9 + 5 + 1 + 7) ÷ 5 = 4.8
5 of six dimensions rated. Unrated dimensions are excluded from the average.
Full scoring method ↗Setup details
Lumo consumer service; web search and explicit feedback use separate disclosed routes.
What fits your needs
Hosted assistant with saved history encrypted at rest and optional web search.
Private chat controls
The service supports guest sessions, saved history, web search, and explicit feedback with distinct data handling.
See the evidence
Tradeoffs to expect
Hosted inference
Prompts are sent to Proton servers for processing; optional web search sends a simplified request to partner APIs.
See the evidence
How to switch
Try with a guest session
Open Lumo as a guest or sign in to use saved chat history; check web search is enabled only when wanted.
See the evidence
Practical questions
Feedback and model route
Do not submit feedback on Apertus unless you accept the policy’s stated sharing; confirm current model and plan.
See the evidence
For the Lumo consumer web and app service boundary, public documentation establishes the service or route but not its request-level physical footprint. The reviewed Lumo sources do not document a user-facing token/task budget, selectable compute tier or measured resource-saving control. Electricity sourcing is not mapped to this route.
See the evidence
This practices/transparency assessment covers the Lumo consumer web and app service boundary. The sources establish how the service or endpoint is exposed and don’t confirm a documented resource-saving control; they do not give a measured per-request energy, emissions or water value. The disclosure point reflects the stated operating boundary, not a product footprint, and company-wide electricity reporting is not attributed to this route.
1 + 1 reporting + 0 electricity + 0 controls = 2/10. This grades documented practices and transparency.
The reviewed sources don’t confirm request-level electricity, emissions or water; the actual serving facility and its power mix are also not mapped to Lumo consumer web and app service.
- Reporting1/3
- The reviewed documentation defines the Lumo consumer web and app service boundary. It gives an operating-scope description, not a dated quantitative energy, carbon or water report for this route.
- Electricity sourcing0/3
- No reviewed source maps Lumo consumer web and app service to a disclosed electricity mix or time-and-location-matched clean-power supply. The route's actual electricity use and emissions therefore remain unestablished.
- Resource controls0/3
- The reviewed Lumo sources do not document a user-facing token/task budget, selectable compute tier or measured resource-saving control.
Water disclosure
Water reporting has not been assessed for this choice.
Lumo uses multiple model families and may change the model selected per task; rights must be checked for the actual model version. Prompt no-training is a separate policy.
See the evidence
Proton’s no-training promise addresses Lumo conversation data, while the hosted models include multiple upstream families whose training data provenance is not fully established by that service promise. Feedback on Apertus has a specific opt-in path.
Exact model selection, release version, source inventory, permissions, post-training data, and creator-remedy scope remain unresolved.
Proton says Lumo does not retain plaintext chat logs after inference, does not use chats to train models, and encrypts saved history with zero-access encryption; explicit feedback may be shared for Apertus evaluation/training.
See the evidence
The Lumo-specific privacy policy describes processing, saved-chat encryption, and a narrow feedback exception for the Apertus model. These are concrete product controls, but chats still reach Proton-controlled servers for inference and optional web search sends a simplified query to selected search APIs.
No numerical score assigned because the reviewed evidence doesn’t confirm the route-specific controls needed for one.
The selected model, account plan, web-search behavior, and future model changes should be checked; the privacy policy can change.
Proton says Lumo’s code is open source and names open-source model families, but the hosted product is not a user-operated local runtime.
See the evidence
Lumo discloses source access to its app and a set of open-source models that it hosts. The user still relies on Proton’s servers and cannot infer that the inference environment or all model data are locally reproducible.
The score reflects service-level inspectability and control, not usefulness or model quality.
Verify current source repositories, model releases, and applicable licenses separately.
Company-level worker conditions and supply-chain safeguards are not assessed from product terms alone.
See the evidence
The reviewed product material describes access and features but doesn’t show labor conditions for the company’s model-development, data-labeling, moderation, or infrastructure workforce. This is an evidence boundary, not a claim about worker treatment.
1 + 0 + 0 + 0 = 1/10. Documented worker protections; missing disclosure is an evidence gap.
Current worker conditions, voice, grievance outcomes, contractor scope, and independent assurance were not established in these product sources.
- Pay & conditions0/3
- No qualifying worker-conditions disclosure was found in the reviewed product sources; this is a limited evidence gap.
- Worker voice & remedy0/3
- No worker-voice or grievance outcome evidence was found in the reviewed product sources.
- Evidence & follow-through0/3
- No independent worker-safeguard audit was found in the reviewed product sources.
No military or intelligence relationship is established by the reviewed product sources.
See the evidence
The official sources reviewed define product behavior and service terms but do not identify a military contract, deployment, or military-specific restriction for Proton AG. This is “not established” within this source set, not evidence that no relationship exists.
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.
Undisclosed contracts, downstream hosting, customer deployment, end-use, and enforcement are outside the reviewed product sources.
- Use restrictions0/4
- No product-specific military-use restriction was identified in the reviewed materials.
- Enforcement & oversight0/3
- No military-specific enforcement or oversight mechanism was identified in the reviewed materials.
- Relationship disclosure0/2
- The product sources provide no military customer or deployment disclosure.
No company military relationship was established in the reviewed product sources; the source set is not a customer-complete investigation.
Military rubric ↗Proton AG (Lumo) was not named in the BNC consumer-target guide or its No Tech target list when. This status covers those named lists only.
See the evidence
I checked the BNC consumer-boycott and pressure guide and the No Tech target list for Proton AG (Lumo). The company was not named in either list on 2026-10-24; this does not assess unrelated suppliers, customers, investors, or every BNC publication.
The result is limited to the two linked BNC target lists as; additions or other BNC publications may change the assessment.