Privacy & Permissions
WorkRouter is designed to be useful without collecting what it doesn't need. This page explains what the extension collects, why, and what it never does.
Permissions requested
| Permission | Why |
|---|---|
| Active tab | Read the current page URL and title only when you explicitly invoke WorkRouter. |
| Storage | Keep your bounded session token and saved preferences on your device. |
| Side panel | Show the check result next to the page you're viewing. |
| Context menus | Let you send a page, link or selection to WorkRouter from the right-click menu. |
No host permissions by default. No background observation. No cookies, passwords, history, or unrelated authenticated account content. The extension does not read arbitrary sites unless you invoke it.
What we collect
- Current page URL, title, and text you explicitly select — only at the moment you invoke WorkRouter.
- A bounded session token (stored hashed server-side) for idempotent saved records.
- Funnel analytics events (e.g. extension check invoked, job saved) — never raw page content.
What we never do
- Never sell your browser data or use it for unrelated ad targeting.
- Never contact a customer, submit a bid or proposal, or spend money or credits from the extension.
- Never expand source permission beyond what WorkRouter's WR-161 source governance allows.
- Never claim a WorkRouter adapter is a third-party site's native integration.
- No server secrets are shipped inside the extension bundle.
Source governance
When you send or check work, WorkRouter evaluates the source server-side. A source hint is never permission: blocked source lanes stay blocked, and your submission cannot expand what WorkRouter is allowed to watch or do.
Removal
Uninstalling the extension removes its local storage. To delete your saved records, contact support and we'll remove them.