Last updated: September 2026
This extension and its backend are operated by Qingyun Dong, an individual developer (“the author”).
When you invoke the extension (toolbar icon or page context menu) on the webpage or PDF you are viewing, it reads the visible article/body text of that page. What happens next depends on how analysis is run:
api.info-lens.app.This happens only when you invoke the extension on the page you are viewing at that moment. The extension does not access any other tabs or pages.
Separately, and without page content: the author uses an anonymous client id (a random UUID). It is stored as a first-party cookie on info-lens.app (shared with the Info Lens website and other Info Lens extensions) and cached in the extension’s local storage. Installing, updating, uninstall events, optional survey answers, and analysis-run usage pings may include this id together with the extension id and version so the author can estimate usage frequency and reconnect the same browser after reinstall. Install and update events also report the browser UI language and system time zone for aggregate user-distribution statistics. If you submit the uninstall survey, the author receives the reasons and comment you typed. The id is not linked to your name, email, or Google account.
If you send a note from the options About section, the author receives the message you typed, any contact you chose to include, the anonymous client id, and the extension version. That note does not include page text.
Separately, for paid cloud credits: the author stores the API key used for cloud access, credit/balance records linked to that key, and order/payment-status records needed for billing. Card and bank details are handled by third-party payment providers; the author does not receive them.
Also without page content: after each analysis run (up to 32 text segments, including when you cancel mid-run or the run fails), the extension sends a small usage ping—extension id, version, anonymous client id, whether analysis used on-device or cloud, outcome, how many segments were attempted / succeeded, and how many were served from the local analysis cache (no new inference). This ping never includes page text or the page URL.
The author does not upload page content. To improve the product, after an analysis the author may upload the site domain (a category for local and private-network pages, not the specific address), content size, how the text was split, whether analysis succeeded, how the run was started, and similar details. This does not include a user identifier, a URL path, or the page text.
Also without page content: when an on-device model setup finishes (success, failure, or cancel), the extension may send a one-shot setup log—extension id, version, outcome, duration, download source (Hugging Face or ModelScope), and a short error string if it failed. No page text.
The page text is used solely to compute information-density scores and return a heatmap overlay on that page. On-device analysis does the same computation locally and does not send the page text to the backend server. Version events, optional survey answers, anonymous analysis-run counts (including the anonymous client id used only to operate and improve the product), on-device setup logs, and optional feedback notes are used only for that purpose. API keys, credits/balances, and order records are used for access control, metering, and billing. No other use is made of this data.
The author does not ask you to create an account with a name or password, and does not track your browsing history across pages or sessions. The author does not collect card or bank details, or health information. If you type a contact into optional feedback, the author stores that text with the note.
info-lens.app resets the anonymous client id cookie.The author does not share, sell, or transfer page content to third parties. The author does not use your data for advertising. Third-party payment providers process payments; they do not receive page text. If you agree to on-device analysis, the extension contacts Hugging Face or ModelScope only to download model weights; those services do not receive the page text.
All data sent to the backend server is transmitted over HTTPS.
The extension requests the minimum permissions needed for its single purpose (highlighting informative words on the active page):
Optional host access is requested only when needed: file:// for local PDF files, and Hugging Face or ModelScope origins to download model weights after you agree. Cloud analysis does not use host permissions; page text is sent to the backend by the extension’s background service worker via a standard cross-origin HTTPS request. The page you are viewing never talks to the backend server directly.
If the author's data practices change, the author will update this policy and the Chrome Web Store listing accordingly.
For questions about this policy, please contact [email protected].