Privacy Policy
PureRead is provided by Logic Fusion, LLC. The extension is designed not to send your reading activity to PureRead servers and to keep its settings data in Chrome-managed storage on your device.
1. Overview
PureRead is a Chrome browser extension provided by Logic Fusion, LLC. This Privacy Policy explains how we handle information in connection with the extension and this website.
For extension usage, PureRead is designed not to collect personal data of its own. The extension's permissions, its Content Security Policy, and the absence of outbound API calls to PureRead servers mean it does not send your reading activity to us.
You can independently review the extension's permissions, Content Security Policy, and network activity in Chrome to confirm how it behaves.
2. What Data the Extension Collects
For extension usage, none.
Specifically, the PureRead extension is not designed to collect or send the following information to Logic Fusion, LLC or PureRead-operated servers:
- Your browsing history or the URLs you visit
- The content of any web page you view, in reader mode or otherwise
- Personal information of any kind (name, email address, age, location, etc.)
- Usage statistics, analytics events, or crash reports
- Device identifiers, IP addresses, or fingerprinting data
- The text you highlight or the notes you write
- Any data about which articles you read, how long you spend reading, or your reading habits
- Authentication tokens, cookies, or session data from any website
The extension does not include analytics or telemetry code for sending your reading activity to PureRead servers. Its extension pages also enforce a restrictive Content Security Policy that blocks outbound API connections from those pages.
3. How the Extension Works
When you install PureRead, a lightweight passive detector (content/detector.js) runs on all pages to determine whether the current page is likely readable, using Mozilla's isProbablyReaderable heuristic. This script does not transmit any data — it only communicates locally to update the toolbar badge. A background service worker (background.js) handles toolbar icon badge updates; it performs no network requests and retains no data.
When you click the PureRead icon (or press Alt+R) on a web page:
- PureRead receives temporary access to the current tab's HTML via the
activeTabpermission. - Mozilla's Readability.js runs locally in your browser to extract the article content from the page's HTML.
- A clean reading view is rendered using HTML and CSS, entirely within your browser.
- When you close or navigate away, the temporary access ends. Nothing is retained.
PureRead does not send article content, URLs, or reading activity to PureRead-controlled servers.
Outbound connections: PureRead's extension pages enforce connect-src 'none', which blocks outbound API-style connections from those pages. As with normal web browsing, the reader view may still display content that references resources hosted by the page you opened, such as remote images.
4. Chrome Storage
PureRead uses Chrome's built-in chrome.storage API to save your reading preferences on your device. This is local storage — functionally similar to a website's localStorage — managed entirely by your Chrome browser.
The following preferences may be stored locally:
- Selected reading theme (light, dark, or sepia)
- Font choice (System, Serif, OpenDyslexic, or Atkinson Hyperlegible)
- Font size preference
- Line spacing preference
- Reading width preference
If you use the free tier's local highlights feature, your highlights are stored in chrome.storage.local, which means they remain on your current device only and are never transmitted anywhere.
Chrome Sync: If you have enabled Chrome Sync in your Google account settings, Chrome may sync certain extension storage data across your devices as part of Google's own sync infrastructure. That sync is performed by Google, not by PureRead. Logic Fusion, LLC does not receive or access that synced data through PureRead servers.
PureRead servers are not used to store or access your extension settings or reading activity.
5. Permissions Explained
PureRead requests only three permissions. Here is exactly why each one is needed:
-
activeTab— Required to read the HTML content of the current tab when you click the PureRead icon, so that Readability.js can extract the article. This permission grants access only to the tab you're on, only at the moment you click the icon, and only for as long as PureRead needs to parse the content. It grants no persistent background access. -
storage— Required to save your reading preferences (theme, font, size, etc.) locally so they persist between sessions. Without this, you would have to reconfigure PureRead every time you use it. -
scripting— Required to inject the reader mode CSS and rendering logic into the current tab when you activate reader mode. This is a standard extension mechanism for modifying how a page is displayed in your browser.
PureRead explicitly does not request:
host_permissions(including<all_urls>) — which would allow background access to all pages you visithistory— which would allow access to your browsing historytabs— which would allow reading URLs and titles of all open tabscookies— which would allow reading authentication cookieswebRequest— which would allow intercepting network trafficidentity— which would allow access to your Google account
6. Technical Verification
We encourage you not to take our word for any of the above. You can:
- Review the
manifest.jsonto verify the requested permissions - Inspect the Content Security Policy to confirm
connect-src 'none' - Use Chrome DevTools' Network tab to verify that no outbound requests are made when PureRead activates
- Inspect the installed extension package for analytics libraries, tracking calls, or outbound API endpoints
We welcome responsible security reports and questions about the extension's behavior.
7. Third-Party Services
PureRead uses no third-party services of any kind within the extension itself. There are no analytics providers, no crash reporting services, no advertising networks, no CDN dependencies, and no external font services.
The only third-party code bundled with PureRead is Mozilla's Readability.js, which runs entirely within your browser and makes no network calls. It is included under the Apache 2.0 license.
Bundled fonts: OpenDyslexic and Atkinson Hyperlegible font files are bundled locally and served via chrome.runtime.getURL(). No CDN or external font service is contacted. Both fonts are included under their respective open licenses (SIL OFL 1.1 and Braille Institute License).
This website (pureread.app) may use standard website tooling, logs, or analytics to understand traffic and operate the site. Those website activities are separate from the extension experience. The extension itself does not send your reading activity to this website.
8. Children's Privacy
Because the extension is not designed to collect personal information, we do not knowingly collect personal information from children through the extension.
9. GDPR Compliance (EU/EEA Users)
Because the extension is designed not to send personal data to PureRead servers, PureRead's extension functionality is intended to minimize data processing by Logic Fusion, LLC. Specifically:
- The extension is not designed to send personal data to PureRead servers during normal use.
- Settings are stored in Chrome-managed storage on your device, and may be synced by Google if you enable Chrome Sync.
- Logic Fusion, LLC does not use the extension to build advertising profiles or cross-site behavioral tracking.
- If website logs or analytics are used for pureread.app, they apply to website visits rather than extension reading activity.
All data written by PureRead (reading preferences and highlights) is written to your local Chrome storage and remains under your direct control. You may exercise your rights to access, rectify, or erase this data at any time by clearing extension storage via Chrome DevTools → Application → Extension Storage, or by uninstalling PureRead.
10. CCPA Compliance (California Users)
PureRead does not "sell" or "share" personal information as defined by the California Consumer Privacy Act (CCPA) and its amendments (CPRA). We have no personal information about you to sell.
- We do not collect personal information from you.
- We do not sell or share personal information with third parties.
- We do not use personal information for cross-context behavioral advertising.
California residents' rights to know, delete, and opt out of sale/sharing are automatically satisfied because no personal information is collected.
11. Data Deletion
To remove all data PureRead has stored on your device:
- Open Chrome → chrome://extensions → PureRead → Details → clear Extension Storage, or
- Uninstall PureRead — Chrome removes all associated extension storage automatically.
There is no account to delete, no server-side data to request removal of, and no email unsubscribe needed.
12. Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be reflected in this document and anywhere this policy is published.
If we make material changes to how the extension or website handles information, we will update this page and revise the "Last updated" date.
13. Contact
If you have questions about this Privacy Policy, how PureRead handles data, or would like to discuss a security concern, please contact Logic Fusion, LLC at product@logicfusion.net.
For responsible disclosure of security vulnerabilities, please use that email address rather than posting sensitive details publicly.