1. Scope and single purpose
SiteEgress helps users inspect and understand browser-visible privacy and data-flow behavior on websites they visit. It reports destinations, known services, form metadata, permission requests, browser-fingerprinting-related signals, Cookie names, browser-storage key names, security context, and optional country-level network-location estimates.
SiteEgress is an inspection and transparency tool. It is not an antivirus product, legal compliance certification, proof of malicious intent, or guarantee that a website does not collect data.
2. Information processed
To produce an audit, packaged content scripts and the extension service worker may process the current page origin and hostname; destination hostnames; resource types and transfer channels; request methods; form action, method, field count, password-field presence, and broad field-name categories; Cookie names; Local Storage and Session Storage key names; permission events; fingerprinting-related API events; and selected page-security metadata.
SiteEgress does not intentionally retain typed form values, passwords, Cookie values, browser-storage values, authorization headers, request or response bodies, complete query strings, or URL parameter values.
Reports contain evidence metadata, not the private values users type into websites.
3. Privacy Checkpoints and receipts
Privacy Checkpoints compare two minimized browser-visible evidence windows for the same origin, commonly before and after a privacy or Cookie choice. The user makes the choice manually; SiteEgress does not click consent controls or store the wording of the selected option.
A checkpoint stores bounded metadata such as origin, capture/window timestamps, score, coverage, destination hostnames, known service names and categories, aggregate signal counts, optional country-code aggregates, and browser-reported GPC or DNT state when visible. It excludes typed values, page text, request or response bodies, URL parameter values, Cookie or storage values, and raw destination IP addresses.
The local store is limited to eight checkpoints per site and forty sites. A Privacy Receipt is created only after an explicit export action and remains on the user's device unless the user chooses to share it. A comparison is technical evidence, not proof that a legal consent choice was honored or violated.
Version 1.2 adds no new Chrome permissions. Checkpoints use existing local storage and the existing Side Panel.
3. Geo Insights
Geo Insights is optional and disabled by default. When a user enables it, SiteEgress may use Chrome's browser-visible response metadata to obtain a destination server IP address. Local and private addresses are classified on the device. A unique public destination-server IP may be sent to ipwho.is solely to obtain a country code and continent code.
The lookup request does not include page text, form values, the full page URL, Cookie values, report contents, or user account information. The raw destination IP is kept only transiently in service-worker memory, is deduplicated to reduce lookups, and is not written to reports, local history, exports, or persistent extension storage.
A displayed country is an estimate of the network server location observed by Chrome. CDN routing, anycast, proxies, caches, load balancers, and multi-region infrastructure can change the apparent country. Geo Insights does not prove legal data residency or where an organization ultimately stores or processes data.
Third-party lookup: ipwho.is. Geo Insights stays off until the user explicitly enables it.
4. Local storage and retention
Live reports are stored in chrome.storage.session and normally disappear when the browser session ends or the tab report is removed. User preferences are stored in chrome.storage.local.
Local history is optional. If enabled, compact snapshots may include the site origin or hostname, score, destination hostnames, known service names and categories, aggregate signal counts, country-code aggregates, and save time. Raw IP addresses and private field values are not included. Users can clear history at any time.
5. Reports and exports
A user can export the current report as JSON, CSV, standalone HTML, or a printable page that can be saved as PDF. Exports are created on the user's device and are not uploaded to SiteEgress.
Exports can contain site hostnames, third-party destinations, known service names, evidence labels, scores, and country-code aggregates. Users should review an export before sharing it outside their device.
7. Permissions and website access
storage keeps session reports and user-controlled local settings. sidePanel displays the audit beside the page. webRequest observes non-blocking response metadata required for optional Geo Insights. HTTP and HTTPS host access lets packaged content scripts inspect normal websites from document start and lets webRequest receive response metadata.
SiteEgress does not request webRequestBlocking, declarativeNetRequest, notifications, cookies, history, downloads, tabs, or remote-code permissions. It cannot inspect Chrome internal pages or the Chrome Web Store.
8. User choices and deletion
Users can leave Geo Insights and local history disabled, pause or reset an audit, clear local history, disable Geo Insights, delete their own export files, or uninstall the extension. Disabling Geo Insights clears current location aggregates from the report.
Uninstalling the extension removes Chrome-managed extension storage.
9. Contact and policy changes
Privacy questions can be sent to [email protected]. Material changes to data handling will be reflected in this policy and, where required, disclosed before the new processing begins.
Runtime data minimization
SiteEgress classifies only bounded, sanitized URL query parameter names. Parameter values are not inspected for personal-data, credential, token, email, or phone patterns.
Page-world events are projected into event-specific schemas, allowlisted, sanitized, and bounded before they enter extension state. DOM mutation discovery is incremental, debounced, and capped.
The Geo response observer is registered only while Geo Insights is enabled. Turning the feature off removes the observer, aborts active lookups, clears bounded in-memory lookup state, and rejects late results.
Version 1.2.1 adds no Chrome permissions.
Optional SiteEgress Security Suite bridge
SiteEgress can connect locally to the separately installed Agent Guard extension. The bridge is disabled by default in both products and requires explicit opt-in on each side.
Shared fields are limited to normalized origins or destination hostnames, known service/action categories, aggregate scores and counts, policy outcomes, confidence, and bounded evidence metadata. Page text, typed values, passwords, secrets, Cookie or Storage values, request bodies, URL parameter values, and raw destination IP addresses are excluded.
Agent Guard context cannot change a SiteEgress audit. SiteEgress context cannot approve, grant, block, or otherwise control an Agent Guard action. The products remain independently installable and usable.
The bridge adds no Chrome API permission and sends no bridge data to a developer server.
Contact
This page explains product practices and is not a certification or legal opinion.