ezy Reader Privacy Policy

Publisher: koProDev · Effective: October 2, 2026 · Version: 0.1.20

ezy Reader displays a user-invoked web page or selected text in a customizable reading view. No account or sign-in is required.

Information handled and purpose

The extension processes website content, including article text, selected text, titles, authors, and image/media URLs, locally in the browser. It uses the invoked page URL and tab/frame identifiers to display the article, link to the original, and manage the reader. On supported community boards, and on other pages you invoke, it reads the titles and post URLs shown in the page's post list locally and displays them beside the reader. On other pages, the default setting (“Supported boards and news front pages” under “List detection” in the toolbar) shows a list only for news front pages whose articles are spread over several sections; “Automatic” also shows other post lists. To find a list, it examines the links of the page you invoke locally; choose “Off”, or turn lists off for a site, to stop this. Known forms of action links, such as log out or delete, are left out of the list; unknown forms may not be. Read-state marks disappear when the reader closes. It does not use the history permission, access the full browsing history, or maintain a list of visited pages, except the list of sites where you turned automatic lists off (below).

Sites where automatic lists are off: when you choose “Turn off for this site” in the post list, only that site's origin (for example https://example.com — no paths, post titles, or visit times) is saved in chrome.storage.local on this device so that automatic detection is skipped there. Up to 200 origins are kept, and the oldest are removed first. Turning the site back on removes it. Nothing is saved from incognito windows, and the list is not synced or transmitted.

Reading preferences (including list detection) and settings metadata are saved locally. Metadata includes modification times and a randomly generated device-specific identifier for settings management. This identifier is not an account or advertising identifier and is not transmitted externally.

Retention and deletion

Extracted content, post lists, and page URLs are temporarily held in memory-backed chrome.storage.session and removed after rendering. A post chosen from the list is passed to the reader directly without storage. A copy of the post URLs of an automatically detected list, used to check the post you choose, is kept in the extension's isolated memory on the list page until the reader closes or the page is left (after an extension update or reload, until the page is left); the page's own scripts cannot read it. Links inside the article that are used to decide whether to show a list are used only during processing and are not stored. The displayed article remains within the open reader. Reader-management identifiers and the page's origin (used for per-site automatic-list settings and to check chosen posts) are removed during session cleanup; browser restart or extension reload clears session storage. Incognito article content is not written to persistent storage.

Preferences, settings metadata, and the list of sites where automatic lists are off remain in chrome.storage.local until removed with the extension. ezy Reader does not send article text, page URLs, or settings to a developer server. It has no remote account sync, advertisements, or analytics SDK.

External requests

• Fonts: Noto fonts, including the default sans-serif font, load CSS and font files from fonts.googleapis.com and fonts.gstatic.com. The Book font (Gowun Batang) is loaded from the same services only when it is selected. Article text is not included in font requests. Selecting System prevents Google Fonts requests.
• Posts chosen from the list: Only when you choose a post in the reader's list, the extension requests that post page from the same site (same origin) as the list page. For automatically detected lists, only posts shown in that list are requested; posts on other subdomains of the site are not requested and open in a new tab instead, like normal browsing. The request includes that site's cookies and ordinary browser request information, and the site may count it as a page view. Redirects within the same site are followed, so if the site redirects a post address elsewhere, that address is also requested with cookies. It does not prefetch other posts, and the fetched page is parsed locally without running its scripts.
• Opening automatically detected posts on the site: If the site marks a post you choose from an automatically detected list as subscriber-only (schema.org isAccessibleForFree: false), the article text is not taken from the fetched page; instead the original tab moves to that post. The same happens when you press “Open on the site in this tab” for a post that could not be read. This is like normal browsing, and any subscription or sign-in check happens on the site. On that page, only the amount of visible text is counted locally so the reader can reopen (at the latest a few seconds after the page loads) with the same list beside it. For this, the chosen post URL and the current list (post titles and URLs, up to 200) are kept in chrome.storage.session and removed when the reader reopens, after 5 minutes, or when the tab closes.
• KakaoPage episode lists: Only when you open the reader on a page.kakao.com series or episode page, the series' episode list (episode IDs and titles) is requested from bff-page.kakao.com without cookies. Episode text and purchase information are not requested. Choosing an episode does not fetch it; the original tab moves to KakaoPage's episode viewer, like normal browsing, and rental or purchase processing happens on KakaoPage. Choosing an episode you have not rented may cause KakaoPage to use an available rental pass without further confirmation, just as when you click the episode on KakaoPage. On that episode page, only the amount of visible text is counted locally so the reader can reopen once the episode text appears; the chosen episode URL is kept in chrome.storage.session for up to 5 minutes and removed when the reader reopens, the time passes, or the tab closes.
• Original media: Images and posters normally load from their original resource hosts without a Referer header. DC Inside images load after you grant optional access to its image servers, using only https://gall.dcinside.com/ as the Referer required by those servers. The Referer does not include the article URL or post ID. Audio and video are requested on playback. Page-turning views may preload images on the next spread.
• Optional embeds: Links only is the default. Choosing inline media loads YouTube and X content in isolated frames from youtube-nocookie.com and platform.twitter.com. YouTube requires an optional host permission. Its player request uses the extension ID as Referer, not the source article URL.

Resource providers receive network information such as your IP address, browser request information, and requested resource URLs. Cookies depend on your browser settings and the provider's policies. See the Google Privacy Policy, the X Privacy Policy, and the original media provider's policy.

Permissions and limited use

storage supports preferences, temporary article transfer, and the list of sites where automatic lists are off; activeTab and scripting extract the user-invoked page and its post list (including automatic detection), request posts chosen from that list on the same site, and display the reader; contextMenus enables right-click reading actions. declarativeNetRequestWithHostAccess only sets the Referer needed by optional permissions you grant (youtube-nocookie.com and DC Inside image servers).

User data is used only to provide reading features. It is not sold or used for advertising, creditworthiness, or lending. ezy Reader's use of data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Contact and changes

For questions, use ezy Reader GitHub support or the developer contact information on the Chrome Web Store. Do not include personal information or article content in public issues. This policy and its effective date will be updated when functionality or data handling changes.