Skip to content

Privacy

Privacy Policy

This page explains how Lumeo PDF Workspace approaches document privacy, local browser processing, preferences, and future data flows.

Last updated: July 11, 2026

This privacy page is a practical product disclosure and is not a substitute for legal review.

Privacy at a glance

  • Current supported PDF workflows are browser-first.
  • Files are processed on the user's device for supported tools.
  • Current tools do not require document upload for processing.
  • No account is required for current tools.
  • The active workspace can be cleared by the user.

Files and document content

Current supported browser-first tools process files locally in the browser. Files are not intentionally transmitted to Lumeo servers for those workflows, and document contents are not stored in localStorage.

Generated object URLs and temporary in-memory data are cleared when the workspace is reset or the page session ends, subject to browser behaviour. Downloads remain on the user's device according to the browser's download settings.

Local storage

May be stored
Non-document UI preferences such as layout choices within Compose.
Not stored
PDF contents, page images, output documents, document text, document passwords, and sensitive document metadata.

Analytics and diagnostics

Lumeo may record optional anonymous product-use events to understand reliability and which PDF tools need attention. These events use a temporary browser-session ID and coarse categories only.

Analytics events do not include documents, filenames, document contents, exact file sizes, extracted text, passwords, emails, or account identifiers. Do Not Track disables optional analytics.

Cookies

Current browser-first tools do not require account cookies. Hosting platforms, browsers, or future product features may use cookies or similar storage for operational purposes.

Third-party services

Lumeo uses web hosting and deployment infrastructure to serve the public site. Fonts are loaded through the framework's font system. Current Compose, Distill, Capture, and Render workflows run entirely in the browser and do not require remote PDF processing services.

Security limitations

Browser-first processing reduces unnecessary file transfer, but no online service can guarantee absolute security. Users should keep browsers updated and handle highly sensitive documents according to their organisation's policies.

Future features

Optional accounts, cloud history, sync, team workspaces, or remote processing may use different data flows in future. Such features should receive updated disclosures and user choice before release.

Children's privacy

Lumeo is intended for general document work and is not designed to collect information from children. If a future account feature changes that model, this page should be updated.

Changes and contact

Material updates will be reflected on this page with an updated date. Privacy questions can be routed through the contact page.

Privacy Policy - Lumeo PDF Workspace | Lumeo PDF