Don't trust us, verify it yourself

1. Watch network activity directly

Open your browser's developer tools (F12 or right-click → "Inspect"), the "Network" tab. Reload a page. Any network request from Noise Guard itself would show up there, recognizable by Noise Guard's extension ID as the source. The one exception: if you've entered a list URL under "Community" yourself and actively clicked "Check now", then exactly that one request appears, otherwise none.

2. Look at the actual permissions requested

Under chrome://extensions (or Firefox's equivalent), click "Details" on Noise Guard. The extension requests exactly four permissions, no more:

• storage: to save your settings on your own device
• contextMenus: for the right-click options (e.g. "Hide element")
• activeTab: to interact with the currently active page
• declarativeNetRequest: for network-based blocking of known ad domains

None of these four enable sending data to a server. The additional permission for all websites (<all_urls>) is needed so detection can run on any page at all, but says nothing about whether data leaves the device.

3. Look at the stored content yourself

In developer tools under "Application" (Chrome) or "Storage" (Firefox) → "Extension storage", you can view the complete stored dataset, in plain text. There's no encrypted or obfuscated storage portion that would hide anything.

4. What this can't verify

These three steps reliably show the behavior of the currently installed version. They're not a substitute for reviewing the source code itself, if it's publicly available, and they say nothing about future versions. Checking regularly yourself is more honest than trusting once and for all.