Lumo

A face for a private conversation

AI assistants tend to converge visually. A text box, gradient, starburst, or sparkle can signal the category, but it rarely gives a particular product a personality. Proton’s Lumo takes the opposite route. The product is named for its mascot, and the purple cat-like figure gives the assistant a recognizable presence before a user submits a first prompt.

Proton’s own account of designing Lumo makes the character a deliberate answer to the problem of making private AI approachable. That pairing is important. Privacy is an abstract property that usually appears as policy language, security diagrams, or lock icons. A companion character cannot prove a privacy claim, but it can provide a humane doorway into a product whose differentiation depends on that claim.

On the Lumo product, the name and figure form one identity. Users do not have to remember which generic “AI” tab belongs to Proton. They can remember Lumo. In a category full of similar interaction patterns, that mnemonic advantage is substantial.

Why a cat-like companion fits the interface

Lumo’s rounded body, ears, tail, and deep purple palette give the character enough specificity to be identified at small sizes. The design can read as alert without becoming intrusive. Cats also carry a useful degree of independence: a cat-like assistant can feel present and curious without necessarily suggesting a relentlessly cheerful servant. That interpretation is analysis, not an attributed statement from Proton, but it fits the tension a privacy brand must manage between help and autonomy.

The character offers expressive range that a sparkle mark cannot. It can attend, wait, react, or guide while preserving the same silhouette. Those states are especially valuable in conversational software, where processing, uncertainty, and empty screens need feedback. A mascot can make those pauses feel like parts of a relationship rather than gaps in a machine.

Color creates continuity with the broader Proton environment while the animal form separates Lumo from a suite icon. This is a productive balance for product families: inherit enough visual material to indicate ownership, then add a shape that gives the new product its own memory hook.

Differentiation beyond the feature checklist

Private AI competes on technical and policy details that many people cannot evaluate at a glance. Lumo’s character gives marketing a second register. Proton can explain protections in precise language while using the mascot to keep the experience welcoming. The character should not replace the explanation; it helps more users reach it.

The US App Store listing extends that identity to a constrained storefront. Where products compete through similarly sized icons and screenshots, a distinct figure is more ownable than a decorative burst. The 478 ratings recorded for this directory show an emerging mobile audience, but the count is a popularity snapshot, not proof that the mascot caused installs or that the assistant has reached category scale.

The 2025 launch caveat matters. A young mascot has not yet accumulated the repeated exposure that turns a design into a durable brand asset. Lumo’s effectiveness will depend on consistent use across the web product, mobile surfaces, documentation, announcements, and future interaction states. Recognition grows from repetition more than from a single polished reveal.

Trust cannot be illustrated into existence

There is a particular risk in putting a cute companion beside privacy claims. Warmth can make a product easier to approach, but it must never substitute for verifiable information about data handling and product behavior. Users should be able to distinguish the emotional promise—Lumo feels safe to talk to—from the operational promise that Proton describes in its materials.

Anthropomorphism can also overstate understanding. A responsive face may encourage users to read empathy, judgment, or certainty into generated output. Product teams need interface language and feedback patterns that preserve the difference between a friendly presentation and a human confidant. The more companion-like the mascot becomes, the more carefully the product should communicate limits.

Finally, a character can compete with serious tasks. People using an assistant for focused research or writing may prefer a quiet interface. Lumo needs to scale its presence with context: prominent during onboarding and brand moments, restrained while the user’s content takes priority. Mascot visibility should be a system, not a constant maximum.

A practical model for AI brands

First, assign the character a job that is narrower than “be cute.” Lumo’s job is to make the private assistant recognizable and approachable. Every new pose or animation should support that role—welcoming, waiting, orienting, or clarifying state—rather than decorate arbitrary screens.

Second, separate signals of trust. Let the mascot carry tone and continuity; let product copy, controls, and documentation carry evidence. That division protects both. The character remains likable without being asked to certify a technical claim it cannot demonstrate.

Third, design for quiet moments. Conversational products contain loading, empty, error, and handoff states. A flexible mascot can unify them, but only if expression, motion, and scale have clear rules. Lumo shows why AI products benefit from owning a silhouette, not just applying a fashionable effect.

The broader lesson is that sameness is itself a product problem. When interfaces and features converge, a character can make a utility easier to recall. The strongest result still depends on alignment: the mascot’s behavior, the brand’s privacy position, and the assistant’s actual conduct must tell the same story.

Sources and further reading

• Proton on the design of Lumo
• Lumo official product
• Lumo on the US App Store