Last updated: April 17, 2026
ReadEasy ("the extension") provides a distraction-free reader view by extracting article content from the current page. It also supports saving user-selected highlighted text from webpages into the Reading List, using a floating webpage launcher that offers quick actions (Switch to reading view / Open side panel), managing extension display preferences from the side panel, optional Google sign-in, and feedback collection links in the reader/side panel that open our Featurebase portal. This privacy policy explains how data is handled.
ReadEasy complies with applicable privacy laws including GDPR. As the extension does not collect personal data on external servers, GDPR data subject rights (access, deletion, portability) are managed entirely through your browser's built-in controls.
We do not collect, transmit, or sell any personal data to external servers. The extension processes the current page's website content (text, images, links) entirely on your device to render the reader view, manage your Reading List, and generate exports (HTML / EPUB). Text-to-speech playback uses your browser's built-in speech engine, which runs locally on your device.
When you use the Reading List, "Add to List", or "Save Selection" features, article/selection content (including images converted to base64 PNG data URIs when available) is stored locally in your browser's IndexedDB. No data is sent to any server during this process — images are fetched directly from the originating website and stored in your browser only.
ReadEasy may also display a small floating launcher on regular webpages so you can quickly open a two-option menu (Switch to reading view / Open side panel). The launcher itself does not transmit page data anywhere. Its visibility setting and last dragged position are stored only in Chrome sync storage so the extension can restore your preference across pages and signed-in Chrome profiles. When you change the launcher enabled/disabled setting, the extension propagates that preference to open tabs so the launcher can hide/show immediately.
When you click "Beta View", the current article's HTML and styling are sent to the web app URL you choose to open. This is an explicit user action; no data is sent automatically.
When you click "Merge EPUBs" in the reader header, your browser opens https://merge-epubs.vercel.app/ in a new tab. ReadEasy does not attach article content to this action automatically.
When you click "Feedback" or "Share feedback & ideas", your browser opens https://readeasy.featurebase.app/ in a new tab. ReadEasy does not attach article content to this action automatically.
All data is stored only in your browser, never on external servers:
Text selections are only processed when you explicitly click "Save Selection" in the side panel. The extension does not continuously record what you select or type on webpages.
For Google sign-in, the extension uses Chrome's identity APIs. Access tokens are used only in-memory by the extension service worker during auth/profile retrieval and are not persisted in extension storage.
When you save an article to your Reading List, the extension fetches images directly from the original website (e.g. cdn.example.com) in order to embed them locally as PNG data URIs. This fetch is performed by the extension itself (not by injecting code into the page), using the host_permissions: <all_urls> permission. No data from these fetches is sent anywhere other than your local IndexedDB.
We do not share or sell data with third parties. The only outbound data transfer occurs when you explicitly use:
postMessage to the web app you open. You can disable this feature by not using the Beta View button.mailto: link; the EPUB is attached client-sidehttps://merge-epubs.vercel.app/ in a new tab. Any content you submit there is provided directly by you on that website.https://readeasy.featurebase.app/. Any data submitted there is provided directly by you on that website.The extension does not load or execute remote code. All JavaScript is bundled with the extension package.
activeTab — Access the current page when the user explicitly clicks the extension icon to open Reader Viewscripting — Inject the Readability content extraction script into the active tab when triggered by the userstorage — Save preferences, Reading List metadata, and temporary article data to your browseridentity — Enables extension-native Google sign-in via chrome.identity.getAuthToken() when you explicitly click the sign-in iconsidePanel — Display the Reading List side panel where users can view, manage, and access saved articlesdeclarativeNetRequest — Set Referer headers on image requests to certain CDNs (e.g. Substack, Medium) so article images load correctly. No content is inspected or modified.contextMenus — Add a right-click context menu option for quick access to the Reading List side panelhost_permissions: <all_urls> — Required so the extension can fetch images from any CDN domain to embed them locally for Reading List / highlighted selections and export features. Without this, cross-origin image fetches would be blocked.content_scripts on <all_urls> — Enables the sidepanel-based "Save Selection" feature and the floating webpage launcher. When you highlight text on a webpage and click "Save Selection", the content script extracts the selected text locally and returns it to the extension. The floating launcher only opens extension UI actions (reader view or side panel) and stores its own enabled/position preferences locally; it does not automatically send page content anywhere.ReadEasy stores all article data locally in your browser using Chrome's built-in storage APIs. The extension does not transmit passwords, login tokens, or sensitive payment information. Images are fetched from publicly accessible URLs only.
You have full control over your data:
If you have questions, contact: vashishta.pulkit@gmail.com