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 et reçus
Les Privacy Checkpoints comparent deux fenêtres de preuves minimisées pour la même origine, généralement avant et après un choix de confidentialité ou de cookies. L’utilisateur effectue le choix manuellement.
Un checkpoint conserve uniquement l’origine, les horaires, le score, la couverture, les destinations, services, compteurs de signaux, pays estimés et états GPC/DNT visibles. Les valeurs privées, le contenu des pages et les IP brutes sont exclus.
La conservation est limitée à huit checkpoints par site et quarante sites. Le reçu HTML est créé localement à la demande et ne prouve pas juridiquement le respect du consentement.
La version 1.2 n’ajoute aucune autorisation Chrome.
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.
Minimisation à l’exécution
SiteEgress classe uniquement les noms de paramètres URL nettoyés et limités ; les valeurs ne sont pas inspectées.
Les événements de page sont limités, nettoyés et projetés vers des schémas propres à chaque type. L’analyse des mutations DOM est incrémentale et bornée.
L’observateur Geo n’est enregistré que lorsque Geo Insights est activé. Sa désactivation retire l’observateur et annule les recherches en cours.
La version 1.2.1 n’ajoute aucune autorisation Chrome.
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
Cette page décrit les pratiques du produit et ne constitue ni une certification ni un avis juridique.