Pangent Browser Companion Privacy Policy Effective date: November 10, 2026 Pangent Browser Companion connects a user-installed Pangent Code desktop application to the user's Chrome browser. It is a local companion, not an advertising, analytics, or cloud-sync service. What the extension accesses Pangent Browser Companion accesses tab URLs, titles, and identifiers when Pangent Code requests browser automation or the user opens a supported HTTPS site. It accesses page content needed to produce an accessibility-oriented snapshot or screenshot only when Pangent Code performs a browser task requested by the user. After the user grants the optional cookies permission, the extension reads only host-only, non-partitioned Cookies for the exact HTTPS hostname and applicable path represented by a short-lived, single-tab authorization. How data is used Data is used only to carry out an action initiated through the local Pangent Code application. The extension sends data only to the loopback address of that local application. For a browser task requested by the user, the local application may provide the resulting page snapshot or screenshot to the Agent runtime configured by the user so that the requested task can be completed. Cookie names and values are excluded from Agent tool results and remain within the local browser components. The extension does not sell data, serve advertising, or use data to determine creditworthiness or eligibility. Storage and retention Cookie values are held in memory and transferred over a loopback connection. They are not written to extension or application logs or persisted by the extension. A login-state grant expires after at most 15 minutes and is cleared on navigation, tab closure, Chrome profile or extension-generation change, or revocation. Other browser snapshots are transient task results. Permissions The tabs, scripting, debugger, and HTTP(S) host permissions support user-requested browser navigation, page snapshots, screenshots, and DOM actions. The nativeMessaging permission discovers the locally installed Pangent Code application. The optional cookies permission is requested only for the current real HTTPS tab. The storage permission keeps random local profile and generation identifiers. The offscreen permission maintains the local connection while the Manifest V3 service worker is idle. Remote code No remote code is loaded or executed. All JavaScript and markup are packaged with the extension. Sharing and disclosure The extension does not sell or rent user data and does not transfer data for personalized advertising, credit, or lending. Page snapshots and screenshots are disclosed to the user's configured Agent runtime only when necessary to perform the browser task requested by the user. Cookie names and values are not disclosed to the Agent runtime or unrelated third parties. User choices Users can decline or revoke Cookie access in Chrome at any time. Removing the extension or disconnecting Pangent Code stops access. Pangent Code also provides a control to stop synchronization and clear the current built-in browser login state. Contact For privacy questions, use the support contact published on the Chrome Web Store listing.