Privacy
Privacy Policy
This page explains how Lumeo PDF Workspace approaches document privacy, local browser processing, preferences, and future data flows.
Last updated: October 4, 2026
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 supported workspaces.
- Not stored
- PDF contents, page images, output documents, document text, document passwords, and sensitive document metadata.
Analytics and diagnostics
Lumeo may record optional privacy-preserving product-use events to understand real audience activity, reliability, and which PDF tools need attention. When analytics is enabled, Lumeo uses random first-party visitor and session tokens. The server converts those tokens into pseudonymous identifiers before analytics data is stored, and separates known test/bot traffic from the default real audience view.
Approximate city, region, and country may be derived from Cloudflare request metadata. This is network-level approximation, not GPS or a precise address. A raw network address may be used transiently to derive a one-way rate-limit key, but the raw address is not stored in product analytics.
Analytics events do not include documents, filenames, document contents, exact file sizes, extracted text, passwords, emails, authenticated account identifiers, raw IP addresses, or precise coordinates. Do Not Track disables optional analytics.
Cookies
Public PDF processing does not require an account. If optional analytics is enabled and Do Not Track is not enabled, Lumeo may set a random first-party visitor token for up to 180 days and a short-lived session token for about 30 minutes. These tokens are HttpOnly, are not document identifiers, and are not combined with email or account identity. Authentication and other product features may use additional operational cookies where required.
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 live public PDF, document-conversion, and image-conversion workflows are designed to run in the browser and do not require a remote document-processing service.
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.