SiteEgress
Add to Chrome
SiteEgress 1.3 for Chrome

See where your data goes.

Inspect browser-visible third-party destinations, tracking services, fingerprinting signals, forms, permissions, and privacy changes—processed locally.

Add SiteEgress to Chrome Explore SiteEgress
Local-firstNo telemetryMinimal permissions
SiteEgress
SiteEgress privacy exposure overview in Chrome
3API permissions
36interface languages
1optional Geo lookup
5export paths
Core capabilities

Inspect the data flow—and compare what changes after a privacy choice.

SiteEgress separates observed, declared, matched, and heuristic evidence, then lets you compare two time-bounded local checkpoints without claiming legal compliance.

Visible data destinations

Map first-party and third-party hostnames seen through browser-visible resource and API activity.

Known service recognition

Identify common analytics, advertising, session replay, messaging, and observability services from a packaged local catalog.

Privacy Checkpoints

Capture minimized before/after evidence windows and compare destinations, services, countries, signals, and score changes.

Fingerprinting signals

Surface Canvas, WebGL, Audio, WebRTC, device enumeration, and related high-entropy API use as conservative heuristics.

Forms and permissions

Review form destinations, cross-site submission attempts, password-field presence, and sensitive browser permission requests.

Local reports and receipts

Export JSON, CSV, standalone HTML, print/PDF, or a focused Privacy Receipt without uploading the audit.

New in SiteEgress 1.3

Compare before and after a privacy choice

Capture two minimized, time-bounded evidence windows around a Cookie or privacy choice. You make the choice manually; SiteEgress shows what browser-visible activity changed.

1

Capture before

Save a local baseline before selecting Accept, Reject, or Customize.

2

Make the choice

Use the website's own privacy controls. SiteEgress never clicks the banner for you.

3

Capture after

Browse briefly, save the second checkpoint, and compare visible differences.

Export a local Privacy Receipt

Create a standalone HTML record of the selected checkpoints, differences, confidence, and limitations. It excludes private values and raw IP addresses.

A comparison is browser-visible technical evidence. It is not proof that a website legally honored or violated consent.

SiteEgress Privacy Checkpoints before and after comparison
SiteEgress Security Suite

Two extensions. One optional local security context.

SiteEgress and Agent Guard remain independent Chrome extensions. When both are installed and both local bridge toggles are enabled, they can exchange a minimized, origin-scoped security summary on the device.

1

Install independently

Use either extension alone, or install both from their separate Chrome Web Store listings.

2

Enable both sides

The bridge is off by default. Each extension must opt in before product summaries are exchanged.

3

Review shared context

Agent Guard can see SiteEgress destination risk context; SiteEgress can show minimized Agent Guard action and policy context.

Minimized fields only

  • HTTP(S) origin or destination hostname
  • Known service or action category
  • Aggregate scores, counts, policy outcomes, and confidence
  • Versioned evidence metadata with bounded collections

Never exchanged

  • Page text or prompts
  • Typed form values, passwords, secrets, Cookie or Storage values
  • Request or response bodies and URL parameter values
  • Raw destination IP addresses

Bridge context is evidence, not authority. SiteEgress cannot approve an Agent Guard action, and Agent Guard cannot rewrite a SiteEgress audit.

Install SiteEgressInstall Agent Guard
SiteEgress third-party data flow view
Workflow

How SiteEgress works

1

Observe

Packaged Chrome content scripts observe minimized browser metadata from the start of normal HTTP and HTTPS page loads.

2

Classify

SiteEgress separates observed, declared, matched, and heuristic evidence and calculates an explainable exposure score.

3

Review

The Side Panel presents a quick summary, full destination map, signals, evidence, optional local history, and exports.

Privacy architecture

Local-first by design

SiteEgress has no account, developer audit backend, telemetry, advertising SDK, cloud sync, or external AI service. Privacy Checkpoints are bounded local summaries. Optional Geo Insights is off by default; raw destination IPs are never retained.

Local-first No telemetry Minimal permissions
manifest.json

Minimal extension API permissions

storage

Stores current session reports, interface preferences, and optional compact local history.

sidePanel

Displays the audit beside the website while the user continues browsing.

webRequest

Observes non-blocking response metadata required only for optional Geo Insights.

SiteEgress declares HTTP and HTTPS website access for document-start content scripts and non-blocking response metadata. It does not request webRequestBlocking and cannot inspect Chrome internal pages or the Chrome Web Store.

What SiteEgress cannot prove

  • Server-to-server transfers that are not visible inside the browser
  • How a recipient uses data after receiving it
  • Whether a website has malicious intent
  • Legal compliance with GDPR, CCPA, or other laws
  • That a low score means a website collects no data

See the data flow. Compare the privacy choice.

Install SiteEgress 1.3 from the official Chrome Web Store listing and review its published permissions and privacy disclosures.

Add SiteEgress to Chrome