Feature Request: Controlled & Secure Email Thread Access for Lumo AI

Summary

Lumo's privacy-first approach is exactly why I wanted to use it — I was actually planning to build something similar myself, so I genuinely appreciate what Proton has created here. That said, I'm hitting a wall that prevents me from getting real value out of Lumo: there's currently no way to share email content with it in a controlled, secure manner.

The Problem

Lumo correctly states it has no access to my mailbox — which is great in principle. But email is where most of my communication lives. Without being able to work with email threads, I can't use Lumo to draft replies, summarize conversations, or act on my correspondence. Manually copy-pasting individual emails defeats the purpose entirely, and I certainly don't want to grant blanket access to my entire mailbox.

What I'm Asking For

A way to selectively and securely pass email threads or conversations to Lumo — without Lumo having standing access to my mailbox. Some ideas on how this could work:

Forward-to-Lumo:
A dedicated, private Proton Mail address for Lumo (e.g. lumo.username@...) where I can forward specific threads I want it to work with — keeping it ephemeral and scoped.

In-app "Send to Lumo" action: A button in Proton Mail that lets me select a thread and push it to Lumo in one click, without any persistent mailbox access.

Session-scoped sharing: A UX flow where I explicitly share one or more threads for a single Lumo session, after which access is revoked.

Why This Matters

The core value proposition of an AI assistant in an email context is helping with email. Without some form of controlled thread sharing, Lumo is effectively cut off from the most important part of my workflow. This one capability would be the difference between Lumo being a tool I use daily and one I can't really adopt.
I'd love to see this prioritized — the privacy-preserving framing is already there, it just needs a UX bridge between my inbox and Lumo.