Security
Security and browser-first processing
Lumeo is designed to reduce unnecessary document movement. For supported browser-first tools, PDF processing happens locally inside the browser rather than through a remote document-processing server.
Security approach
Browser-first processing is an architectural choice intended to reduce avoidable document transfer for current supported tools. It does not remove every risk, but it keeps the active workflow closer to the user's device.
Current processing model
- Processing location
- User's browser
- File upload
- Not required for current supported browser-first tools
- Document storage
- Not intentionally stored by Lumeo for current supported workflows
- Account required
- No
Browser isolation
Current tools use browser APIs and client-side PDF libraries. Browser sandboxing provides an important security boundary, while actual protection also depends on the browser, device, extensions, and operating system.
Temporary data and cleanup
Files may be held in memory or browser-generated temporary URLs during the active session. Start New and cleanup actions clear active workspace state. Temporary data may also end when the tab or browser session closes. Browser downloads remain under user control.
Dependencies
Browser PDF libraries are used for current document processing. Dependencies are reviewed for compatibility and bundle impact, but no software supply chain can be described as perfectly risk-free.
What current tools do not do
- No required server upload for current Compose, Distill, Capture, or Render workflows.
- No remote PDF processing for current Compose, Distill, Capture, or Render workflows.
- No cloud document storage for current supported workflows.
- No forced account.
- No document-content analytics.
- No external OCR for current supported workflows.
User security recommendations
- Use a current browser.
- Avoid untrusted browser extensions.
- Use trusted devices for sensitive documents.
- Review downloaded output before sharing.
- Follow organisation-specific document policies.
Responsible disclosure
Security concerns should include the affected page or tool, clear reproduction steps, impact, and non-destructive proof. Please do not send confidential PDF files unless specifically requested through an approved secure channel.
Security limitations and future architecture
No system is perfectly secure. Browser-first does not remove every risk, and device compromise or malicious extensions remain outside Lumeo's control. Cloud or account features, if introduced, should receive separate security and privacy disclosures.