8 min read
Privacy and security
Learn what local-first means, what the browser stores, and where its security boundaries are.
Local-first processing
For Lumli’s currently available image, PDF, color, and QR workflows, the selected content is read and processed in your browser. The core operation does not require uploading the original file to a cloud editing service.
What can leave the device
The website, code, fonts, workers, and model assets must be downloaded when not already cached. The anonymous completed-actions counter receives an increment request, but Lumli does not include the selected file, file name, generated output, email, or account details in that request.
Browser storage
- Temporary file handoffs and previews used to continue a local workflow.
- Theme and interface preferences.
- PWA assets, workers, and AI model files cached for performance or offline use.
- Downloaded results remain in the download location you choose and are controlled separately.
Clear local data
- 1Open your browser’s privacy or site settings.
- 2Find stored data for lumli.io.
- 3Clear site data, cache, local storage, and permissions as needed.
- 4If installed, remove the Lumli PWA separately.
- 5Delete downloaded outputs from your device if you no longer need them.
Security boundaries
Local-first design reduces unnecessary transfer; it does not secure a compromised browser or device. Browser extensions, malware, shared profiles, screen capture, backups, download folders, operating-system permissions, and external links remain outside Lumli’s control.