Privacy
What Lumo stores, what it sends, and what it never touches. No account, no relay server.
Lumo is local-first. Both products store their data in your browser. Model requests go directly from your browser to the provider you configure, using the key you provide.
Last updated Nov 1, 2025
What we collect
Settings, conversations, generated files and script metadata are stored locally in extension storage. The website itself is static and does not set analytics cookies.
What we do not collect
No account, no email, no advertising identifiers, no analytics profile, no relay of prompts or page content to Lumo servers.
Where data lives
Small settings live in chrome.storage.local. Conversations, files and script bodies live in IndexedDB. The website stores only your theme and language preferences in localStorage.
Permissions
Each permission is requested for a named capability and listed in the documentation. Optional capabilities are requested only when you enable the feature that needs them.
Third-party providers
When you send a message, the request goes to the model provider you configured. Their terms and retention policy apply. You can use a local model to keep everything on-device.
Deleting your data
Clear a conversation, delete a script, empty the recycle bin, or remove the extension. Removing the extension deletes its storage. The website can be reset by clearing site data.