SiteEgress docs

Understand what the browser can show—and what it cannot.

Start with the evidence model, then use destinations, signals, Geo Insights, history, and exports according to the question you are investigating.

Quick start

From installation to an explainable first review

01

Install and refresh

Install SiteEgress from the official Chrome Web Store listing, then refresh pages that were already open.

02

Open the Side Panel

Click the SiteEgress toolbar icon on a normal HTTP or HTTPS website.

03

Review the score

Use the score as a prioritization aid, then read the findings and evidence rather than relying on the number alone.

04

Inspect destinations

Search third-party hostnames, known services, channels, and the data-flow view.

05

Enable optional features deliberately

Read the disclosure before enabling local history or Geo Insights.

06

Export only when needed

Review the report before sharing because hostnames and observed destinations can be sensitive in context.

Core concepts

Use consistent definitions when reading the interface and evidence

Observed

A browser-visible resource or API event was seen during the current session.

Declared

The page referenced a destination, such as preconnect or DNS prefetch, but an actual transfer was not confirmed.

Matched

A destination matched a known service in the packaged local catalog.

Heuristic

An API signal may be privacy-sensitive but can also have legitimate graphics, media, compatibility, or anti-fraud uses.

Geo Insights

Country-level estimates derived from observed public destination-server IPs after explicit opt-in.

Exposure score

A bounded summary of visible destinations, known services, collection signals, fingerprinting signals, and transport hygiene—not a legal or moral verdict.

Need help?

Include the product name, version, Chrome version, and minimal reproduction steps when contacting support.

Support