Lumo by Proton

I started using Lumo because I wanted an AI assistant that felt more private than the usual mainstream options, but the most interesting test was not a solo productivity session. I tried to imagine how it would work around a household: one person planning a meal, another checking a school-related explanation, and someone else using the same device for a quick piece of research. That shared setting exposes both the appeal and the limits of Proton’s approach.

Lumo is a free productivity app from Proton AG, built around the idea of a private AI assistant. It is available for Everyone, runs on Android ten and later, and the current version is 2.0.5-gms. The app has passed the early curiosity stage with more than one hundred thousand installs, although its average of 3.7 from roughly three thousand ratings suggests that the experience is useful for some people while still leaving room for improvement.

My overall impression is that Lumo makes the most sense for people who already care about privacy and want a conversational tool for drafting, explaining, organizing, and brainstorming. It is less convincing as a complete household information hub or as a replacement for a dedicated notes, calendar, parental-control, or collaboration app. That distinction matters before anyone installs it on a shared phone or tablet.

How Lumo fits into a shared household

A practical shared-device scenario

Imagine a family tablet in the kitchen. One person asks for a simple shopping-list structure, another wants help turning leftovers into a meal plan, and a teenager asks for a clearer explanation of a difficult science topic. Lumo can be useful in each moment because the interaction is conversational rather than menu-driven. I can begin with a broad request, read the answer, and refine it without learning a complicated productivity system.

The strength here is flexibility. A household does not need everyone to use the assistant in exactly the same way. One person may treat it as a writing partner, another as a study aid, and another as a quick planning scratchpad. That makes it easier to introduce than a specialized application that expects everyone to understand the same workflow.

There is also a subtle advantage to using an AI assistant for coordination: it can turn a vague request into a usable starting point. Instead of asking, “How do we organize dinner this week?” I can ask for a short plan based on available ingredients, then request a version grouped by shopping aisle or preparation time. The value is not that the first answer is perfect. The value is that the conversation helps shape an imperfect idea into something actionable.

Still, I would not confuse conversational help with shared task management. Lumo may help me write a list, but a generated list is not automatically a live household checklist. It does not replace a calendar when several people need reminders, and it does not become a family message board simply because everyone can ask questions on the same device. For coordination, I would use Lumo to prepare information and a dedicated app to assign, track, and confirm responsibilities.

Why separate conversations matter

On a shared device, the first habit I would establish is keeping each person’s use separate. A conversation about a private work issue should not sit next to a child’s homework discussion or a shopping request. Even when no one is trying to snoop, casual browsing can expose context that was meant for someone else.

This is one of the most important practical boundaries with any conversational assistant. The app may be private in its design, but privacy also depends on how people use the device. I would avoid treating one open conversation as a communal notebook. Instead, I would start a fresh thread for a different person or purpose, close the app when finished, and avoid entering sensitive household details just because the assistant makes typing easy.

That advice is especially relevant when a tablet stays unlocked in a common room. A private assistant still needs private handling. Lumo’s privacy-focused identity is a reason to consider it, not a reason to ignore ordinary device-sharing habits.

Setup without overpromising boundaries

Getting started is straightforward in the sense that the app presents itself as an assistant rather than a complex productivity suite. I can approach it with a normal question instead of configuring projects, folders, labels, or a team structure first. That low barrier is helpful for a household where some people are comfortable with AI and others are not.

At the same time, a simple setup can create an expectation that the app will manage every boundary for me. I would not assume that installing it creates separate household profiles, child accounts, approval flows, or shared permissions. Those are different product responsibilities, and I would use only the account and device arrangements actually available to me rather than imagining a family-control system around the assistant.

For a shared device, I would decide in advance who is allowed to use it, whether the device itself has separate user access, and which kinds of information should never be typed into a general-purpose AI chat. That preparation is more valuable than trying to solve privacy concerns after a conversation has already been saved or viewed.

The same principle applies to account boundaries. If several people use one account, their conversations and habits can become mixed together. If each person uses an individual account, the household has clearer separation, but it also has more sign-ins to manage. Lumo can be part of that arrangement, but it should not be expected to define the arrangement on its own.

Using it for household coordination

I found the best coordination role for Lumo to be preparation. It can help turn scattered thoughts into a message, a plan, a set of questions, or a clearer explanation. For example, before a family meeting, I could ask it to organize several concerns into a short agenda. Before contacting a school or service provider, I could use it to make my wording calmer and easier to understand.

That use is different from asking the assistant to make decisions for everyone. Household planning often includes preferences that are not obvious from a short prompt: allergies, budgets, transport limits, personal schedules, or disagreements. Lumo can help structure those details, but I would review every suggestion before treating it as a plan.

A useful workflow is to ask for alternatives rather than a single answer. If I need a weekend plan, I might request a low-cost option, a weather-independent option, and a version that requires very little preparation. Comparing those drafts exposes trade-offs more clearly than accepting the first response. This is one of the better ways to use an AI assistant in a family setting: let it widen the options, then let people make the final choice.

Another practical tip is to request output in a format that matches the next step. A paragraph may be fine for an explanation, but a short checklist is better for shopping, and a table-like sequence may be easier to copy into another tool. Lumo becomes more useful when I tell it who will read the result and what I intend to do with it.

However, I would always verify details that affect money, safety, health, school requirements, or travel. A fluent answer can sound settled even when the situation needs current or expert information. Lumo is most valuable as a thinking and drafting partner, not as the final authority for consequential household decisions.

Age context and trust

The Everyone age classification makes the app approachable for a broad audience, but that label should not be treated as a substitute for supervision or judgment. A general AI assistant can respond to many kinds of questions, and a younger user may not know when an answer is incomplete, outdated, or too confident.

For schoolwork, I would encourage a child or teenager to ask for an explanation, a worked example, or questions to test understanding rather than simply requesting a finished answer. That encourages learning and makes it easier for an adult to see how the assistant is being used. I would also remind them not to enter names, addresses, passwords, private school messages, or personal details about friends.

Trust needs an adult side as well. I would not rely on an assistant to interpret a medical concern, settle a family conflict, or judge whether an online claim is true. In those situations, the responsible use is to create a list of questions for a qualified person or to clarify terminology, then verify the important information elsewhere.

This is where Lumo’s privacy positioning is appealing but nuanced. I appreciate the attempt to make privacy part of the product’s identity, especially compared with assistants that are strongly associated with broad data ecosystems. Yet privacy and accuracy are separate questions. A private answer can still be wrong, and a correct answer can still be unsuitable for a child or a shared screen.

Where it differs from familiar alternatives

Compared with a standard search engine, Lumo is better suited to back-and-forth refinement. Search is often faster when I already know the exact page or current fact I need. Lumo is more comfortable when I am starting with a messy idea and need help shaping it into a request, outline, explanation, or draft.

Compared with a notes app, it offers more active assistance but less dependable structure. A notes app is the better choice for storing a household inventory, keeping a permanent reference, or maintaining a document that several people edit over time. Lumo is better for generating a first version or reorganizing material before I place it somewhere more stable.

Compared with a calendar or task manager, it is more flexible but less operational. I can ask for a schedule or a task breakdown, but a dedicated planning tool remains the right place for recurring events, notifications, assignments, and completion tracking. I would use Lumo before those tools, not instead of them.

Compared with a general AI service from a larger platform, Lumo’s main attraction is its privacy-oriented focus and Proton connection. The trade-off is that I should not assume it has the same breadth of integrations, ecosystem conveniences, or specialized features that I may already receive elsewhere. If my household depends on deep connections with email, calendars, documents, or smart-home services, I would compare the actual workflow rather than choosing based on branding alone.

Costs and the point where the decision changes

Lumo is free to install, which makes trying it low risk. There are in-app purchases ranging from $12.99 to $119.88 per item, so I would pay attention to the plan screen before committing to anything beyond the basic experience. For a household, the important question is not only whether one person likes the assistant, but whether the paid arrangement makes sense for the way the household actually uses it.

I would begin with a few repeatable tasks: rewriting a message, explaining a topic, planning meals from ingredients already available, or turning a long note into a checklist. If the free experience handles those jobs comfortably, I can decide whether additional spending is justified. I would not subscribe merely because the app is interesting for a day.

The current release, 2.0.5-gms, shows that the app is being actively presented as a usable product rather than a forgotten experiment. Even so, the rating of 3.7 indicates that expectations and experiences are mixed. I would read that as a reason to test it personally, especially on the device and network conditions I use every day, rather than assuming the privacy angle automatically guarantees a smooth experience.

Who should use it and who should skip it

I would recommend Lumo to someone who wants a privacy-minded conversational assistant for drafting, learning, brainstorming, and light household planning. It is particularly appealing if I prefer Proton’s approach to online services and do not mind reviewing answers carefully. It also suits people who want to ask follow-up questions naturally instead of learning a rigid productivity application.

I would be more cautious if I needed a polished family workspace with clear ownership, assignments, reminders, and shared editing. In that case, a task manager, calendar, document suite, or family organizer would be a better foundation. Lumo could still help prepare the content, but it should not be the central system of record.

I would also skip it if my main requirement is authoritative advice in areas where mistakes carry serious consequences. An AI assistant can help me prepare for a conversation with a professional, but it should not replace that professional. The same caution applies to children using it independently: the Everyone label makes access broad, not judgment automatic.

My household verdict

After looking at Lumo through the lens of shared use, I see a capable idea with a clear personality. Its strongest quality is the combination of conversational convenience and Proton’s privacy-focused positioning. It can help a household think, draft, explain, and prepare without forcing every request into a formal productivity workflow.

Its limits are just as important. I would not treat one shared conversation as a family archive, one account as a complete permission system, or one AI answer as a verified decision. Good boundaries still come from the device, the account setup, the people using it, and the tools chosen for final coordination.

My recommendation is to try Lumo for a defined set of everyday tasks and judge it by the quality of the resulting workflow, not by the novelty of chatting with it. If privacy matters and you want an assistant that helps turn rough thoughts into useful drafts, it is worth exploring. If you need dependable shared records, reminders, integrations, or strong age-specific controls, pair it with more specialized tools instead.

Lumo works best as a private-minded helper at the beginning of a household task, not as the household’s entire operating system. That is a modest role, but it is a genuinely useful one when everyone understands the boundaries.