Tab Leak Guard processes monitoring data locally in Firefox. It makes no application network requests and includes no analytics, advertising, telemetry, automatic crash reporting, remote configuration, or remote code.

On pages you authorize, the collector observes bounded numeric and boolean summaries of live DOM size, added/removed elements, resource activity, responsiveness, visibility, collector health, and whether editing was observed. It does not read page text, HTML contents, form values, cookies, authentication tokens, request bodies, screenshots, or keystroke contents. Firefox-provided URLs, hostnames, tab identifiers, optional titles for extension views, and tab activity/sharing state are used locally for scope, display, and recovery checks.

Current samples and temporary sessions use Firefox session storage. Preferences, site policies, bounded recovery journals, and receipts use local extension storage. Samples are capped at 16 per document and 300 tab records. Receipts are capped at 50 with a user-selectable retention policy of off, 24 hours (default), or seven days. You can clear receipts or delete extension-managed local data; website permissions are managed separately in Firefox. Private browsing is disabled.

Notifications are generic by default; hostname disclosure is optional. Diagnostic exports remain local until you deliberately share them and exclude page titles, hostnames, page text, and form values. Review any exported file before sharing it.

Full policy: https://github.com/caamer20/tab-leak-guard/blob/main/docs/privacy.md
Support: https://github.com/caamer20/tab-leak-guard/issues
Private security reports: https://github.com/caamer20/tab-leak-guard/security/advisories/new