What Window Resizer can see, what it does with it, and — the short version — why nothing leaves your browser.
Collects — nothing. No analytics, no crash reporting, no telemetry, no account.
Sends to a server — nothing. There is no Window Resizer server. The extension has no backend and makes no network requests.
Stores — one thing, on your device only: the last custom width and height you typed, so the fields are pre-filled next time.
Reads — only your current window's size and your screen's work area, and only to resize the window when you click a preset.
Window Resizer resizes your current browser window to a preset or custom pixel size you pick from its popup. That's the entire product. Everything below follows from that one job.
Reading the window and display dimensions, capping the size to your screen, and moving the window all happen inside your browser. No page content, no URL, no browsing history, and no personal information is ever read or transmitted — not to us, not to a third party, not to an analytics service. The extension has no server to talk to.
Chrome requires an extension to declare, up front, every capability it might use. Here is what each declared permission is for, in this extension specifically.
| Permission | Used for |
|---|---|
| system.display | Reads your display's work area — the screen minus the taskbar or dock — so a preset larger than your monitor is capped to fit, and so the window is centered and placed on the correct screen in a multi-monitor setup. |
| storage | Saves the last custom width and height you entered, locally via chrome.storage.local, so those fields are pre-filled the next time you open the popup. This value stays on your device and is never sent anywhere. |
The extension requests no host permissions and no access to your tabs, your browsing history, or the content of any page.
chrome.storage.local holding your last custom width and height. You can clear it by removing the extension. Nothing else is written to disk.If what the extension collects, sends, or requests ever changes, this page will be updated and the "Effective" date above will move. Continuing to use the extension after an update means you've seen the current version of this policy.