Privacy Policy

AgentLens processes webpage and PDF content inside Chrome so you can compare human-visible content with machine-readable extraction profiles. AgentLens has no publisher-operated server, account system, advertising, analytics, or telemetry.

When you scan a page, AgentLens may handle:

• Visible and machine-readable webpage text, DOM metadata, open shadow-root content, and layout/visibility evidence.
• PDF bytes, text, annotations, metadata, page geometry, and rendered pixels for a PDF you explicitly scan.
• The page URL, title, hostname, and favicon.
• Bounded evidence excerpts, hashes, locators, rule matches, risk labels, limitations, and user decisions such as Reveal, Strip, or Allow in copy.
• Local settings, website access choices, and rules that you create or import.

AgentLens does not read form values, passwords typed into webpages, cookies, browsing history from Chrome, or clipboard contents. Passwords entered to unlock an encrypted PDF are held only in that viewer’s memory and are not saved.

By default, AgentLens receives temporary access to the active tab only after you click its toolbar action or invoke its shortcut. You may separately enable Live protection for all HTTP/HTTPS websites or only websites you list. Chrome displays a permission request before granting that access. You can disable Live protection or change the allowed sites at any time.

If enabled, Live protection scans after supported page navigations and alerts only when medium- or high-risk instruction content is found. Automatic Strip is a separate, optional setting.

Current-tab scan state and reversible Strip state use chrome.storage.session. Chrome clears this memory-backed state when its tab closes or navigates, the extension reloads, or the browser session ends.

At first run, AgentLens asks whether to save scan history. When enabled, it stores the latest bounded report for up to 100 page addresses in chrome.storage.local, capped at approximately 5 MB. Saved history can include the URL, title, favicon, scan time, summary, bounded evidence excerpts, locators, rule identifiers, limitations, and hashes. It excludes complete webpages, DOM snapshots, PDF bytes, encrypted-PDF passwords, and sanitized Markdown output. You can disable history—which deletes saved history—or clear it manually from Scanned pages.

Settings, site lists, disclosure acknowledgement, and custom rules are stored locally until you change them, restore defaults, remove the extension, or clear extension storage.

For an HTTP or HTTPS PDF that you invoke AgentLens on, the extension may request that exact PDF URL from its existing host so bundled PDF.js code can analyze it locally. The browser may attach credentials already applicable to that host. AgentLens does not inspect those credentials or send the PDF to another destination. If retrieval fails, you can choose a local PDF; those bytes remain in the viewer tab’s memory.

AgentLens writes sanitized Markdown, evidence, or a locator to the clipboard only after you click the corresponding control. It never reads the clipboard and requests no clipboard permission.

Report and rule exports occur only after an explicit click. Exported .agentlens.json report files contain bounded evidence and hashes, not complete source content or PDF bytes. Imported rule bundles are validated and stored locally. Files that you export are under your control after download.

AgentLens does not transmit page content, PDFs, reports, settings, rules, browsing activity, or identifiers to AgentLens or any third party. It makes no analytics, telemetry, advertising, or rule-update requests. Its only content request is the exact user-invoked PDF described above. Favicons are read through Chrome’s local favicon API.

• activeTab: temporary access to a tab after your explicit invocation.
• scripting: run the locally bundled scanner in an authorized tab.
• storage: retain session scan state, optional local history, preferences, site lists, and custom rules.
• favicon: display a scanned page’s existing favicon in its report and local history.
• Optional http://*/* and https://*/* site access: support Live protection only after Chrome shows and you approve its permission prompt.
• AgentLens does not request debugger, downloads, cookies, history, webRequest, clipboard, or native-messaging permissions.

All executable code and detection rules are packaged with the extension. Untrusted strings are rendered as text rather than executable HTML. PDF JavaScript, active document actions, and arbitrary message-supplied fetch URLs are not executed.

AgentLens’s use and transfer of information received from Google APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. AgentLens does not sell user data, use it for advertising, creditworthiness, or lending, or allow humans to read it except where you explicitly choose to share an exported file for support.

You can turn Live protection and history off, restrict automatic access to selected sites, revoke AgentLens site access in Chrome, clear saved history, restore stripped content, restore default settings, remove imported rules, or uninstall the extension. Uninstalling removes Chrome-managed extension storage.

Use the support contact published on the AgentLens Chrome Web Store listing for privacy questions. Material changes to collection, retention, permissions, or network behavior will be reflected here and in the Store disclosure before release.