What we do and don’t know about you.

What Patch Panel stores

Your YAML configuration and a handful of display settings — bar position, height, width, display mode, auto‑hide toggle, and a schema version marker. That’s it.

All of it lives in chrome.storage.local on the same device you installed the extension on. Patch Panel does not use chrome.storage.sync, so the data is never synced through your Google account. Nothing is ever uploaded to a server by the extension.

What Patch Panel accesses

Patch Panel runs a small content script on every http:// and https:// page so it can draw a bar on top of the page. The content script only renders its own UI. It does not read, log, or transmit the contents of the pages you visit, nor does it look at your browsing history, tabs, cookies, form data, or anything else on the page.

The extension requests exactly one permission: storage. There are no host permissions, no tabs permission, no cookies permission.

Third-party requests

Patch Panel itself makes no network requests — it never phones home and never contacts any server under our control.

However, your YAML config can include icon URLs for each service. Those icons render as ordinary <img> tags in the bar, which means your browser will fetch them from whatever URL you wrote.

If you point icons at your own self-hosted images, those requests never leave your network. If you use a third-party favicon service like https://www.google.com/s2/favicons?domain=…, then your browser contacts that service directly and it learns the domains you looked up, subject to its own privacy policy. This is your choice; you can avoid it by self‑hosting icons or by omitting icon from your config entirely.

Analytics, tracking, and telemetry

None. There is no analytics SDK, no crash reporter, no error tracker, no A/B test framework, no ad network, no fingerprinting — of any kind.

Your data, your device

Because everything lives in your browser’s extension storage, uninstalling Patch Panel from Chrome removes all of it. There is no cloud account, no server-side record, and nothing for us to delete on your behalf — because we never had any of it in the first place.

You can also inspect and edit the full stored state at any time from the extension’s Options page.

Changes

If this policy ever changes, the new version will ship in the next release of the extension and the “updated” date at the top of this page will move. The change history lives in the Git history — diffs only, no rewrites.

Contact

Questions, concerns, or something that doesn’t match what you’re seeing? Open an issue at github.com/balu‑/patch‑panel.