617 results found

1. RTL Text Direction Support Request for Lumo UI

   Lumo currently doesn't support right-to-left (RTL) text direction in the UI, neither in the input nor output fields.

   It would be ideal if the app automatically detects and applies the correct text direction based on the first word of each paragraph. For example, if a sentence begins with an English word, it would display left-to-right; if it starts with an Arabic word, it would switch to right-to-left.

   This feature (automatic direction detection) is already implemented in Telegram, and adopting similar functionality would greatly improve the experience for multilingual users.

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Add Kimi K3 as an available model for Lumo 2.0 Max

   Kimi K3, developed by Moonshot AI, is currently one of the highest-ranked models on the Artificial Analysis Intelligence Index (score: 57), placing it among the top 5 LLMs worldwide. Integrating it into Lumo 2.0 Max would significantly strengthen the range of available models.

   Arguments in favour of this integration:

   • Superior performance — Its Intelligence Index score of 57 surpasses the majority of direct competitors and usefully complements GLM-5.2 (score: 51). This model diversity would enable finer routing based on the nature of each request.

   • Extended context — With a native context window of 1 million tokens, Kimi K3 offers capabilities equivalent to GLM-5.2 for processing long documents, which is essential for academic research and the analysis of complex reports.

   • Alignment with Proton's strategy — Moonshot AI has expressed its intention to publish the model's weights (2.8T parameter version), which aligns perfectly with Proton's commitment to open-source and transparency.

   • Complementarity with existing models — Kimi K3 excels particularly in agentic tasks and long-horizon reasoning, areas where its combination with GLM-5.2 would enable intelligent routing tailored to each use case.

   Recommendation: Integrate Kimi K3 into the selection of models available through the Lumo 2.0 Max interface, while maintaining the optimised automatic routing or allowing manual selection by the user.

   Expected impact: This integration would improve Lumo's competitiveness against competing solutions while respecting Proton's confidentiality and Swiss respectively European infrastructure principles. Professional users would benefit from enhanced response quality for demanding tasks without compromising data protection.

   Kimi K3, developed by Moonshot AI, is currently one of the highest-ranked models on the Artificial Analysis Intelligence Index (score: 57), placing it among the top 5 LLMs worldwide. Integrating it into Lumo 2.0 Max would significantly strengthen the range of available models.

   Arguments in favour of this integration:

   • Superior performance — Its Intelligence Index score of 57 surpasses the majority of direct competitors and usefully complements GLM-5.2 (score: 51). This model diversity would enable finer routing based on the nature of each request.

   • Extended context — With a native context window of 1 million tokens, Kimi K3 offers capabilities… more

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. download pdf

   recently was using gemini ai pro..they have at top of chat, right corner, "download pdf"..simple and effective. many parts of the world internet is expensive and not available always, this would be useful to user of lumo so they can access chat offline as pdf ( since this is widely used). Any particular reason for not being implemented till now?

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Manual control of per-chat project knowledge

   As an alternative to Lumo chats ingesting project knowledge automatically from the files available to the project, it would be great if there was a "Manual" mode.

   The user could selectively add and remove which files are used, as the automatic features sometimes needs a few tries to get everything right. This is especially helpful to avoid the chat auto-ingesting metadata files from external project configurations.

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Lumo Integration to Read Encrypted Emails, Calendar, via On-Device Processing

   I want an AI assistant (Lumo) that can automatically read my Proton Mail inbox and execute actions based on preset rules (e.g., sorting, summarizing, drafting replies, flagging urgent items, consolidating multiple emails into one for review). I understand this requires on-device processing to maintain zero-access encryption. Currently, I have to manually copy/paste emails. An automated, privacy-preserving workflow would be a game-changer for productivity. Lumo needs more gemini like functionality in the Proton product space.

   5 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Direct save of chats as Docs on Drive (+ Lumo-folder on Drive?)

   Integration between Lumo and Docs to allow Lumo users to save chats as Docs on Drive, directly from Lumo.

   Purpose: to ease UX of organising projects in Lumo and save time and effort for users.
   Value:
   1) Nudging users to support their own data security, by not using alternative tools outside of Proton Suite.
   2) Supporting user loyalty to Proton product suite, especially Lumo.

   User scenario:
   After finishing chat with lumo I press the "save as docs"-button next to "copy" and "try again features" in the bottom right corner of the screen. Dialog opens and asks: "Do you want to save this chat as a doc?" Possibillities: "Yes/No". I press "Yes" and Docs opens with the current chat content, ready to be named and saved. When named and saved in a folder of my choice in my Drive, I can upload it to my relevant folder in Lumo Projects.

   Or:
   After finishing chat with lumo I press the "save as Docs"-button next to "copy" and "try again features" in the bottom right corner of the screen. Chat is named (by Lumo as usual) and saved as doc in dedicated Lumo-folder on my Drive. Dialog opens in Lumo: "I have saved the chat as a doc in your Lumo folder on Drive. Do you want me to upload it to your Lumo Project folder X?" (the chat being an x-topic) I can answer "Yes/No" depending on, whether I want this or not.

   This is just from the top of my head, so please be critical about unnecessary complexity, best data flows and architectural robustness and scalability

   Integration between Lumo and Docs to allow Lumo users to save chats as Docs on Drive, directly from Lumo.

   Purpose: to ease UX of organising projects in Lumo and save time and effort for users.
   Value:
   1) Nudging users to support their own data security, by not using alternative tools outside of Proton Suite.
   2) Supporting user loyalty to Proton product suite, especially Lumo.

   User scenario:
   After finishing chat with lumo I press the "save as docs"-button next to "copy" and "try again features" in the bottom right corner of the screen. Dialog opens and asks: "Do you want to… more

   11 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Search not just Lumo chats titles but also content

   The sidebar allows searching in chat titles, but I am unable to easily find on how to search in the chats content (in my questions and Lumo replies). I am aware that i can use browser Ctrl+F to search in current chat, but not in all available chats).

   Ideas:
   - after you type the search query, maybe hitting enter can execute search in content.
   - content search included by default, only the matches in chat titles will be displayed on the top of the search results

   clicking on a content search result, should jump to a correct place in the corresponding chat where is a 1st match, maybe allowing some action buttons to jump to next matches.

   The sidebar allows searching in chat titles, but I am unable to easily find on how to search in the chats content (in my questions and Lumo replies). I am aware that i can use browser Ctrl+F to search in current chat, but not in all available chats).

   Ideas:
   - after you type the search query, maybe hitting enter can execute search in content.
   - content search included by default, only the matches in chat titles will be displayed on the top of the search results

   clicking on a content search result, should jump to a correct place in the… more

   48 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. allow copying history conversation into the projects that we create.

   currently there isn't an option to copy old chats into new projects. why? this is quite disturbing and prevent us from organizing our old conversations.

   10 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Lumo Scheduling Automation

   I went down the rabbit hole of trying to create a scheduled web search on specifict topics. Lumo repeatedly told me it had automation to do this but when I tried to set it up it ended up apologising each time saying it got a bit excited but can't do what it said it could...
   Functionality request - automation that will run a scheduled task/search/etc

   11 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  New feature  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Think and respond in the user's English variant, with full regional settings for Lumo (units, currency, time zones + more)

    Lumo has language selection, but no regional settings governing how it formats measurements, currency, dates and times in its responses, or how it reasons within them. For users outside the US this is constant friction. Critically, these settings should shape how Lumo thinks, not just how it writes: drafting a document in British English should mean composing it in British English from the first word, rather than generating American English and converting the spelling afterwards.

    Requested options, ideally as one Region preference with independent sub-settings:

    1. English variants with full grammar, punctuation, vocabulary and idiom rules (en-GB, en-AU, en-NZ, en-IE, en-CA, en-IN, en-ZA, en-US), rather than one undifferentiated English that defaults to American.

    2. A separately selectable spelling and proofreading variant, independent of interface language.

    3. A temporal awareness toggle (choose whether Lumo knows the current date and time, for privacy), with a user-set default time zone including fractional offsets (UTC+5:30, +5:45, +12:45), correct daylight saving rules per region, a 24-hour or 12-hour clock, and unambiguous offset rendering for cross-zone times.

    4. Measurement units: user-selectable metric or imperial, governing both how Lumo expresses quantities and how it interprets input.

    5. Temperature scale (Celsius or Fahrenheit) as an independent setting.

    6. Default display currency, so financial figures do not assume USD.

    7. Date format independent of language variant (DD/MM/YYYY, MM/DD/YYYY, ISO YYYY-MM-DD, YYYY/MM/DD, D.M.YYYY), plus alternative calendar systems (Hijri, Hebrew, Japanese era, Thai Buddhist, Persian, Indian Saka, Chinese lunisolar among others). This prevents consequential misreadings such as 09/01/2026, two entirely different dates eight months apart depending on the reader's convention.

    8. Calendar week-start day (Monday, Sunday or Saturday, per the user's convention), with ISO week numbering as an option.

    9. Holiday awareness: regional terminology (public, bank, federal, statutory holidays), sub-national variation, correctly named Lunar New Year variants (Spring Festival, Seollal, Tet, Losar, Tsagaan Sar, Imlek), other East and Southeast Asian observances, religious observances across all major traditions (with an option to surface global ones), school holidays and academic terms per jurisdiction (academic year boundaries differ between hemispheres), and moon phases and lunisolar calendar display. Multi-jurisdiction families and remote students should be able to subscribe to several calendars at once.

    10. Financial year conventions: calendar year, 1 July to 30 June (Australia, NZ), 1 April to 31 March (India, Japan), 6 April to 5 April (UK personal tax), 1 October to 30 September (US federal), and a custom start date for anywhere else, so financial year reasoning stops assuming the calendar year.

    11. Number formatting: regional decimal and thousands separators (1,234.56 / 1.234,56 / 1 234,56 / 1'234.56), Indian lakh and crore digit grouping, Arabic-Indic numerals, and East Asian myriad grouping.

    12. Paper size conventions: ISO A and B series, US Letter and Legal, JIS B and traditional Japanese sizes, ANSI, and Latin American formats.

    13. Region-appropriate cultural references in examples (pricing, quantities, institutions) rather than US defaults.

    14. Academic citation styles (Harvard, APA, MLA, Chicago, Oxford) as a selectable preference.

    15. Toggles controlling whether each setting also applies in Ghost Mode chats, so ephemerality does not cost users their regional settings.

    Ideally these would be managed at Proton Account level and available across all applicable Proton apps, applied either globally or per app, configured once and synced everywhere.

    The examples above are illustrative, not exhaustive: the underlying request is that these options cover the conventions in use by everyone in every country globally, with custom options catching the remainder. No Proton user should find their regional reality unrepresentable.

    Competitor landscape: Apple's Language and Region settings already allow independent configuration of these conventions at OS level, inherited by Siri and Apple Intelligence. No major AI assistant (ChatGPT, Gemini, Claude, Copilot) currently offers structured regional settings natively; users resort to character-limited custom instructions that are inconsistently honoured. Proton would be the first AI assistant to ship them.

    Full detail for every item, with regional examples, is posted in the comments below. Please vote if you would like to see these features added :)

    Lumo has language selection, but no regional settings governing how it formats measurements, currency, dates and times in its responses, or how it reasons within them. For users outside the US this is constant friction. Critically, these settings should shape how Lumo thinks, not just how it writes: drafting a document in British English should mean composing it in British English from the first word, rather than generating American English and converting the spelling afterwards.

    Requested options, ideally as one Region preference with independent sub-settings:

    1. English variants with full grammar, punctuation, vocabulary and idiom rules (en-GB, en-AU, en-NZ, en-IE, en-CA,… more

    2 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Custom Lumos usability (quick selection and/or prompt)

    In order to make the use of custom Lumos more efficient (I still catch myself prompting instructions every time instead of selecting the relevant custom Lumo) present custom Lumo icons in the tool bar of the prompt window so i can activate them with one click.
    Maybe allow to 'pin' certain custom lumos for folks that have too many ...
    Mentioned in other posts: a prompt that activates a specific custom lumo would be great too.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Lumo integration in meet for meeting summaries & transcriptions

    It would be great if the upcoming meet app would have an option to summarize and transcript meetings.
    Making this possible with a trustful AI like Lumo would be amazing (and I think no one else has a meeting transcription feature with a trustful AI)

    23 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. saving on proton drive

    Adding an option to connect a Proton Drive and save your chat there so it won't get deleted automatically after a few days. I know that chat history might be long, but if someone has a subscription, it would be amazing to at least archive the chat to Proton Drive, even if it's in another section where you can't download it.

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Ability to edit chat names (especially in projects).

    The automated chat names often aren't relevant to the topic. The ability to edit them would be helpful, especial for projects.

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Bring real-time encrypted voice interaction to Lumo using existing MLS/WebRTC infrastructure

    Live Voice Conversation Mode for Lumo — Powered by Proton Meet's Proven Architecture

    Summary: Enable bidirectional voice conversation in Lumo's mobile apps — speak through a Bluetooth headset, receive spoken responses via text-to-speech — creating a Gemini Live-style hands-free experience. Proton Meet already solves the hardest engineering challenges for real-time encrypted audio. Extending this to Lumo is a natural evolution, not a fundamental R&D problem.

    The Opportunity
    Lumo's mobile app supports voice input (speech-to-text) but lacks voice output (text-to-speech) and continuous conversation mode. Users who want hands-free, private AI interaction — while driving, walking, cooking, exercising, or working — have no privacy-preserving alternative to Gemini Live, Siri, or Google Assistant. All of those services harvest voice data for training and profiling.

    This is both a feature gap and a market differentiation opportunity: Proton could offer the only AI voice assistant where your spoken conversations are encrypted, never logged, and never used for training.

    Technical Feasibility: Proton Meet Already Did the Hard Part
    Proton Meet currently delivers real-time, end-to-end encrypted audio for up to 250 participants using a proven, battle-tested architecture:

    Component Proton Meet Implementation Applicability to Lumo Voice Mode
    Audio capture & encoding WebRTC stack with Opus codec Same stack would power Lumo voice capture/playback
    Real-time encryption AES-256-GCM, encrypted on-device before transmission Same encryption protects voice data in transit to/from Lumo backend
    Key management MLS (Messaging Layer Security, RFC 9420) — IETF standard co-developed by Proton team members Adapts directly for 1:1 user-to-AI session (simpler than group calls)
    Forward secrecy Automatic key rotation per MLS epoch Ensures each voice session is independently secured
    Authentication Secure Remote Password (SRP) protocol Same system already used for Proton Account logins and Meet access
    Server architecture Selective Forwarding Unit (SFU) via LiveKit Cloud — forwards ciphertext only, never decrypts Lumo backend could process only encrypted requests, same zero-knowledge principle
    No-log policy No meeting content, metadata, or participant graphs retained after call ends Same standard applies — voice sessions leave no trace
    Infrastructure Distributed European data centers, outside US jurisdiction Same infrastructure hosts Lumo
    Bottom line: The cryptographic pipeline for real-time encrypted audio already exists, is audited, is open source, and is in production. Adapting it for a 1:1 user-to-AI voice session is architecturally simpler than what Proton Meet already handles for 250-person group calls with dynamic key rotation.

    Proposed Implementation
    Phase 1 — Core Voice Mode (6 months):

    Tap-to-talk: press to speak, release for response
    Streaming TTS output through device speaker or Bluetooth headset
    Audio encrypted on-device using MLS-derived keys before sending to Lumo backend
    Lumo processes the transcribed text (or encrypted audio) and returns a text response
    Response converted to speech via on-device TTS engine
    Zero audio or transcription retained after session ends
    Phase 2 — Continuous Conversation (12 months):

    Hands-free mode: wake word or button activation for back-and-forth dialogue
    Conversation state maintained across exchanges within a session
    Interruptible responses (user can speak over the AI, like Gemini Live)
    Voice activity detection (VAD) to know when the user has finished speaking
    Phase 3 — Advanced Features (ongoing):

    Voice customization (select TTS voice, speed, language)
    Multilingual voice support (leveraging Lumo's existing 11-language support)
    Offline TTS via on-device models (no audio leaves the device for output synthesis)
    Optional local speech-to-text via on-device Whisper or similar model (input never leaves device)
    Voice biometric authentication (optional, user-opt-in, for hands-free session access)
    Privacy Architecture: Where Proton Differentiates
    Competing voice assistants (Gemini, Siri, Alexa, Google Assistant) share a fundamental flaw: they collect, transcribe, and retain voice data on corporate servers for training, advertising profiling, and analytics. Users have no meaningful control over what happens to their voice after it leaves their device.

    Proton's architecture offers a fundamentally different model:

    1. Local Processing Where Possible

    Speech-to-text can run on-device (Android provides native STT APIs; Whisper models run locally on Pixel-class hardware)
    Text-to-speech runs locally via Android's native TTS engine or third-party on-device models (e.g., Piper)
    When both STT and TTS are local, raw audio never leaves the device — only encrypted text is sent to Lumo's backend for processing
    2. Encrypted Transit When Cloud Processing Is Needed

    If cloud-based STT/TTS is required (for accuracy, multilingual support, or low-resource devices), audio is encrypted on-device using MLS-derived AES-256-GCM keys before transmission
    Lumo's backend processes only encrypted data and discards it immediately — same zero-knowledge architecture as Proton Meet
    3. No Retention, No Training

    Voice sessions are ephemeral — no audio, transcriptions, or metadata retained after the session ends
    Voice data is never used to train models (consistent with Lumo's existing zero-training policy)
    No voice fingerprints or biometric profiles stored
    4. Transparent and Auditable

    All client code is open source (consistent with Lumo's existing open-source mobile apps)
    MLS implementation is a public IETF standard — anyone can verify the cryptographic protocol
    Independent security audits (Proton is ISO 27001 certified and SOC 2 Type II attested)
    Market Positioning
    This isn't feature parity with competitors — it's a privacy protection opportunity. Every user who currently uses Gemini Live, Siri, or Alexa because they need hands-free AI is accepting surveillance as the price of convenience. Proton can offer the same convenience with zero surveillance.

    Target audiences:

    Privacy-conscious consumers who avoid voice assistants because they don't trust Big Tech with their voice data
    Professionals handling sensitive information (lawyers, journalists, healthcare workers, executives) who need hands-free AI but can't risk voice data being harvested
    Accessibility users who depend on voice interaction and deserve privacy without compromise
    Enterprise Lumo for Business customers where voice data retention creates compliance risk under GDPR, HIPAA, and similar regulations
    Revenue Potential
    Lumo Plus differentiator: Live voice mode as a premium feature driving Plus subscriptions
    Lumo for Business upsell: Encrypted voice AI for enterprise — a capability no competitor offers with zero-access encryption
    Future hardware partnership opportunity: Licensed secure audio SDK for certified Bluetooth headset manufacturers, bundling with Lumo Plus subscriptions ("Proton Audio Suite")
    Community Need
    Real-world use cases where private voice AI matters:

    Driving: Ask questions, get directions, hear summaries — without sending voice to Google or Apple
    Physical work: Cooking, gardening, repairs — hands occupied, need voice interaction
    Health and medical: Asking sensitive health questions aloud — voice data is especially intimate
    Professional: Dictating notes, drafting documents, brainstorming — work product shouldn't be mined
    Accessibility: Visually impaired users or those with motor limitations who rely on voice and deserve privacy equal to sighted users who can type
    Recommendation
    Prioritize Phase 1 in the current mobile app development cycle. The architecture is proven (Proton Meet), the market demand is demonstrated (Gemini Live adoption), and the privacy differentiation is unmatched. This is a case where Proton can leapfrog competitors by applying existing internal expertise to a new modality.

    I am willing to participate in beta testing and provide detailed feedback throughout development.

    Live Voice Conversation Mode for Lumo — Powered by Proton Meet's Proven Architecture

    Summary: Enable bidirectional voice conversation in Lumo's mobile apps — speak through a Bluetooth headset, receive spoken responses via text-to-speech — creating a Gemini Live-style hands-free experience. Proton Meet already solves the hardest engineering challenges for real-time encrypted audio. Extending this to Lumo is a natural evolution, not a fundamental R&D problem.

    The Opportunity
    Lumo's mobile app supports voice input (speech-to-text) but lacks voice output (text-to-speech) and continuous conversation mode. Users who want hands-free, private AI interaction — while driving, walking, cooking, exercising, or working — have… more

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Lumo and big projects

    Lumo + big projects - when working inside the project, all of the files added should be added to the project, not to the chat. I have a very large self reference files that when added imediately consume 1/2 od the available tokens.
    There should also exist an option to share a local directory with all the files needed so they don't use space in the chat.

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Calendar Booking buffers

    Calendar Booking. I just found this feature on Proton and LOVE it I've been trying to use 3rd party booking tools. The enhancement it needs is to be able to set buffers before/after events on the calendar so they are not back to back. Other booking tools have this feature and found it very helpful.

    10 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Local agent June powered by Lumo

    Please integrate with a local agent like June

    https://www.opensoftware.co/june

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  New feature  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Subject: User Leaving Due to Lumo v2.0 Image Generation Feature

    I've been a loyal Proton customer across multiple services (Mail, Drive, VPN, Pass, etc.) because I trusted your commitment to privacy-first technology. Unlike other AI providers, Proton was positioned as genuinely different — not collecting data, respecting boundaries, and prioritizing ethics over features.

    The Issue
    Lumo's v2.0 update introduced image generation capabilities. This fundamentally changed what made Lumo trustworthy to users like myself. Before this update, there was one clear distinction between Lumo and mainstream AIs: you didn't offer tools that could be used to create potentially harmful content. Now, that line has blurred.

    Why Filters Aren't Enough
    Safety filters on prompts and generated pixels don't solve the core problem:

    Workarounds exist. Determined bad actors routinely find jailbreak techniques that bypass guardrails on every major AI platform
    Capability itself is the risk. Having the ability to generate images — even when filtered — means the possibility exists. You knew this would be the case
    Real-world harm documented everywhere else. Deepfake ***********, graphic violence, child exploitation imagery — these happen on platforms with similar "safeguards." Adding the same vector here carries the same risk
    What Makes This Worse for Proton Specifically
    This contradicts Proton's own founding identity. Other Big Tech companies chasing revenue through surveillance capitalism? Expected. But Proton built its reputation on standing apart from them. Saying "other AIs have image gen so we need it too" isn't an argument — it's surrendering to the exact pressure model you claimed to reject.

    Two interpretations remain:

    Proton knowingly compromised stated ethical principles despite understanding the risks
    Success bred overconfidence — believing we can do something unethical "better" than everyone else
    Either outcome damages trust.

    Broader Harm Beyond Privacy
    Image generation isn't just about risky content. It also:

    Enables mass production of "AI art" that profits while devaluing human creators struggling to earn honestly
    Floods markets with machine generated visuals at near-zero cost, pricing out professionals who invested decades in skill
    Creates legal grey areas around copyright, attribution, and consent AI in today’s world has gotten so realistic with image and video creation that at times it’s hard to know what’s real
    None of this aligns with Proton's public stance on protecting digital freedom and privacy.

    Current Alternative
    I'm moving to DuckDuckGo.ai, which offers text chat + image sending (analysis) — but deliberately avoids image generation entirely, while also having the same idea of privacy that proton have with no data being stored or shared, Proof that competitive AI doesn't require crossing this line. Their restraint validates that this was a choice, not inevitability.

    To end this complaint I’d just like to say as a customer of proton I hope going into the future the company keeps its promise and ethics so proton doesn’t just become another Google or Amazon
    To company’s customers are numbers and to customers company’s are tools for day to day life but the relationship between proton and its users is always has been and I hope continues to be one word “hope”

    Reconsider whether this feature aligns with nonprofit-led mission values under Proton Foundation oversight
    Not asking for perfection. Asking for alignment between what you stand for and what you build.

    Thank you for past work. Hoping this helps shape future decisions better than recent ones did.

    I've been a loyal Proton customer across multiple services (Mail, Drive, VPN, Pass, etc.) because I trusted your commitment to privacy-first technology. Unlike other AI providers, Proton was positioned as genuinely different — not collecting data, respecting boundaries, and prioritizing ethics over features.

    The Issue
    Lumo's v2.0 update introduced image generation capabilities. This fundamentally changed what made Lumo trustworthy to users like myself. Before this update, there was one clear distinction between Lumo and mainstream AIs: you didn't offer tools that could be used to create potentially harmful content. Now, that line has blurred.

    Why Filters Aren't Enough
    Safety filters… more

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. LUMO+ with Access to Multiple AI Models

    I’d like to suggest an improvement to LUMO+. Currently, LUMO+ is great, but it would be even more powerful if it worked more like Perplexity Pro, where subscribers can access multiple AI models like GPT-5 or Gemini 2.5 Pro, including those for image and video generation.

    The key idea is that LUMO would remain the secure privacy layer between the user and these external models. This way, LUMO could either answer directly or automatically choose another model when it’s better suited for the request—without exposing any private data or the user’s identity. Everything would remain protected under Proton’s privacy-first approach.

    Free users would continue to have access to the standard LUMO, while LUMO+ subscribers would get the added benefit of multi-model access, making it a more versatile and competitive tool.

    This feature would combine Proton’s unique strength in privacy with the flexibility users appreciate in platforms like Perplexity.

    I’d like to suggest an improvement to LUMO+. Currently, LUMO+ is great, but it would be even more powerful if it worked more like Perplexity Pro, where subscribers can access multiple AI models like GPT-5 or Gemini 2.5 Pro, including those for image and video generation.

    The key idea is that LUMO would remain the secure privacy layer between the user and these external models. This way, LUMO could either answer directly or automatically choose another model when it’s better suited for the request—without exposing any private data or the user’s identity. Everything would remain protected under Proton’s privacy-first approach.

    … more

    40 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Changes to existing features  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating