Optional Lumo read/write integration with Proton Calendar
Hello,
I'd like to suggest a feature for consideration: allowing Lumo to access Proton Calendar data associated with the signed-in account, on an opt-in basis, with read and write permissions controlled separately.
The proposal
Two independent user-controlled toggles: one for read access, one for modify/write access.
Both off by default. Nothing happens unless the user enables it deliberately.
Scoped to the specific account and accessible only in that authenticated session.
Why I'm suggesting it
I recently worked with Lumo to design a full weekly schedule system — recurring family commitments, volunteering shifts, and health-related appointments whose times and frequencies vary from week to week. Lumo was excellent at the planning stage: structuring calendars, identifying scheduling conflicts, accounting for travel and recovery time, and building a sustainable weekly review routine.
The gap came at the implementation stage. Lumo produced a precise specification, but I had to manually recreate everything in Proton Calendar — dozens of recurring events across five calendars, each with specific reminder defaults. It's essentially transcription work the assistant already computed.
With read access, Lumo could have verified my work, spotted errors, checked for conflicts with newly booked appointments, and answered questions like "how full is next week really?" With write access, it could have created the events directly — respecting Proton Calendar's per-calendar defaults and recurrence options.
Concrete example
In my schedule, I book the next mental health appointment before leaving the current one. Times vary, and each requires a block that includes the session itself plus travel both ways and roughly 30 minutes for recovery. Doing this manually — entering every detail accurately, attaching the right reminders, ensuring it lands inside an appropriate window — consumes time and mental energy. On days when energy is already diminished from treatment or commuting, those fifteen minutes of calendar setup become another drain. That's time and cognitive load that could otherwise go to family, rest, or the recovery process itself.
On the privacy question
I recognize this is the hard part. Proton Calendar's end-to-end encryption is the reason I use it — my calendar contains sensitive information I specifically don't want readable by anyone else. So I want to be clear: if this feature can't be built without weakening that guarantee, I'd rather it not be built. But a client-side, user-toggled, per-session permission model — where decryption happens locally in my authenticated session, and where revoking the toggle cuts access instantly — seems like it could preserve the encryption model while enabling a genuinely useful capability. Users with complex scheduling needs, including those managing disability-related or accessibility requirements, would benefit significantly, and there are likely broader accessibility benefits as well for people with limited time or energy budgets.
Thank you for considering it, and thank you for building products that make privacy the default rather than an afterthought.
Kind regards,