Effective date: 16 July 2026
lucid processes documents selected by the user, including PDFs, printed scanned pages, Markdown, plain text and saved HTML. Document parsing, OCR, reading-order detection, highlighting, annotations and speech generation take place inside the Chrome extension on the user's device.
lucid does not send document contents, extracted text, document titles, document identifiers, notes, highlights, comments, reading positions or listening activity to the publisher.
When local resume is enabled, Chrome extension storage may contain reader preferences, document titles, a locally generated document identifier, resume positions, recent-opening time, source references, reusable file permission handles, highlights, comments, notes and selected OCR word coordinates. Voice-model files are cached by Chrome.
For Chrome Web Store disclosure purposes, document material is classified as Website content; a selected remote document URL and its recent-opening time are classified as Web history; and reading positions and user-created reader state are classified as User activity. These categories are handled locally for the reader features described here and are not transmitted to the publisher.
The user can keep an individual document private. Private documents are removed from recent reading and do not retain reusable access, OCR results, annotations or resume state after the tab closes. Settings can remove reading history, voice files or all locally stored lucid data.
Document bytes and generated audio are not stored in lucid's settings storage. lucid does not write annotations into the original document.
lucid uses the network only to fetch a remote PDF directly from the website selected by the user and to download required voice-model files when they are not already cached.
The remote PDF website receives the normal request needed to download its file. The voice-model host can receive ordinary connection information such as the user's IP address and browser headers, but lucid does not include document data in model requests.
The open beta has no publisher-operated accounts, advertising, behavioural analytics, telemetry, payment processing, trial limit or paid features.
lucid uses Chrome storage to retain the local information described above. It uses activeTab only after the user clicks the extension. Remote-site access is requested for the selected PDF's origin when needed. Direct access to a downloaded PDF already open in Chrome requires the user to enable Chrome's “Allow access to file URLs” setting; selecting a file through lucid uses a narrower user-granted file permission.
Users can deliberately export a support report. It includes the lucid version, browser and platform description, capability flags, reader settings, storage estimates, numeric playback indexes and structural counts. It excludes document names, URLs, identifiers, text, highlights, comments and notes. It remains on the user's device unless they choose to share it.
Locally stored data remains until the user removes it, uninstalls lucid, clears the Chrome profile, or Chrome removes it. It is protected by the user's operating-system account and Chrome profile. lucid does not claim to encrypt local extension storage against a person who already controls either one.
lucid's use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information handled by lucid is used only to provide or improve its private document-reading purpose. It is not sold, used for advertising, used for creditworthiness or lending, or transferred for unrelated purposes.
Material changes will be reflected in this policy and lucid's release notes before release. Privacy and support questions can be sent through the publisher contact or support channel shown on lucid's Chrome Web Store listing.