Home · Product Evidence Lens
Browser extension
Product Evidence Lens: privacy policy
Last updated: 22 November 2026. Developer contact: yjs121256@gmail.com.
Summary: Product Evidence Lens does not collect, store, transmit, sell, or share any personal or website data.
This policy describes the Chrome extension Product Evidence Lens (Manifest V3). It is based on what the shipped code actually does.
1. What the extension reads
Only after you click the toolbar icon and then Inspect active page, the extension runs a bundled function in the active tab. That function reads the text of <script type="application/ld+json"> elements on that page. It does not read form fields, cookies, passwords, local storage, browsing history, or any tab you did not inspect.
The extension’s declared permissions are activeTab and scripting only. It does not request host_permissions, so it cannot run on a page until you click it.
2. Where processing happens
The collected JSON-LD text is passed back to the extension popup and analysed there, in your browser, to build a checklist of Product structured-data fields (name, image, offer, price, currency, and a few recommended fields). The extension makes no network requests of its own. It contains no analytics, advertising, crash reporting, or remotely hosted code. Its content security policy allows scripts only from the extension package (script-src 'self').
3. Storage
Nothing is saved to chrome.storage, to your computer’s disk, or to a server. The checklist disappears when you close the popup.
4. Sharing and sale
No data is transferred to the developer or to any third party, and no data is sold. The extension does not use data for creditworthiness, lending, advertising, or any purpose other than showing you that on-demand checklist.
5. Links in the popup
The popup includes a link to Google’s public merchant-listing documentation. That page opens only if you click the link. Google’s own privacy policy applies to Google’s site.
6. Restricted pages
The extension cannot inspect built-in Chrome pages (for example chrome://) or the Chrome Web Store, because the browser blocks extensions there. That is a browser restriction, not a network call.
7. Changes
If this behaviour changes, this policy will be updated before a release that includes the change, and the date above will change.
Contact
Relevant policy: Chrome Web Store Program Policies — user data.