Hello Proton team,

I am writing with a product suggestion prompted by a conversation I had with Lumo 2.0.

Lumo told me that it can already work with Proton Calendar, discuss and prioritise tasks and habits, use Projects and persistent context, and read files supplied from Proton Drive. However, it cannot write changes back to a structured file or maintain a durable task database in Proton Drive.

This means Proton appears to be extremely close to offering something that does not currently exist as a complete privacy-first product: a genuine personal digital assistant whose AI, calendar, tasks, files and long-term structured state all live within one trusted ecosystem.

I have been building a local macOS version of this myself. It uses:

• an AI conversation interface for natural-language intake and planning;
• an MCP server that lets the AI read and write calendar events and reminders;
• a structured SQLite database containing tasks, intentions, goals, habits, tags, priorities and relationships;
• synchronisation between the database and the calendar/reminder applications;
• stable identifiers so every item can be updated safely;
• confirmation and readback checks for destructive or important actions.

A user can say anything that occurs to them, and the assistant can decide with them whether it should become:

• a specific calendar event;
• a concrete task or reminder;
• an intention that is not yet actionable;
• a goal;
• a habit to build, maintain or reduce;
• a note or idea to preserve;
• something requiring clarification.

The assistant can then see the full operational picture, identify related items through tags and relationships, help prioritise them, suggest habit stacking, and avoid filling the calendar or reminders with vague aspirations.

Proton already has most of the required components:

• Lumo;
• Proton Calendar;
• Proton Drive;
• Proton Docs and Sheets;
• Projects and personalised Lumo configurations;
• encrypted synchronisation and storage;
• a privacy model suited to highly personal life-management information.

The major additions I would suggest are:

1. A Proton Tasks or Reminders product

It should support lists, tags, priorities, due dates, recurring tasks, completion history, notes and notifications. Lumo should have permission-controlled read, create, edit, complete and delete access.

1. Writable structured storage for Lumo

Lumo should be able to read and write an encrypted structured store rather than merely analyse a temporarily attached file. This could initially be:

• a Proton Sheet;
• a structured Proton Drive file;
• a dedicated encrypted personal-assistant database;
• or a new Proton data object designed for tasks, goals, habits and notes.

Users should be able to export the data in open formats such as CSV, JSON or SQLite.

1. Bidirectional integration across the Proton suite

Lumo should be able to read current and past Calendar events and Tasks, maintain a structured overview, and write confirmed changes back to the appropriate product.

The system should preserve distinctions between:

• operational calendar and task state;
• broader goals and intentions;
• habits;
• internal tags and relationships that do not need to clutter visible calendar or task entries.

1. A safe action model

Before deletions, cancellations or large changes, Lumo should show the exact affected objects and request confirmation. After writing, it should read the result back and report whether the operation was actually successful.

1. Either a dedicated “Lumo Assistant” or integrated assistant mode

A dedicated Lumo Assistant could have a focused interface, clearly scoped permissions and predictable tools for Calendar, Tasks and structured storage.

Alternatively, ordinary Lumo could expose these capabilities whenever the user enables an “Assistant” mode or grants the necessary product permissions. This would avoid fragmenting users between two AI products.

My preference would be one Lumo product with an optional assistant mode, while keeping the action permissions explicit and reversible.

1. Essential chat-interface features

Lumo should also have the standard interaction controls expected from a modern AI assistant:

• speech-to-text in the message box;
• text-to-speech for Lumo’s answers;
• copy buttons for both Lumo responses and the user’s own prompts;
• reliable export of individual conversations and Projects.

This would be particularly valuable for users with ADHD, executive-function difficulties, disabilities, complicated schedules, or simply many ideas and obligations. Privacy is especially important for such a system because it may contain health information, personal plans, finances, relationships and daily behavioural patterns.

I would genuinely prefer to build my personal digital-assistant workflow entirely inside Proton rather than assembling it locally from an AI interface, an MCP server, Apple applications and a separate database. I would switch more of my digital life to Proton and pay for Proton Unlimited – and an appropriate Lumo tier if required – if Proton made this possible.

Proton is unusually well positioned to create the first broadly accessible, privacy-first digital-assistant ecosystem. The individual products already exist. The missing step is to connect them through safe, writable, permission-controlled AI actions and add a proper task/reminder layer.

Please pass this suggestion to the Lumo, Calendar, Drive and product-strategy teams.

Best regards,

Per Christian Frankplads