Chrome Web Store Privacy Worksheet

Use this worksheet when completing the Chrome Web Store Developer Dashboard privacy fields for Window Resize Manager. Keep it aligned with public/manifest.json, docs/privacy-policy.md, docs/chrome-web-store-review.md, docs/usage-analytics-events.md, and the uploaded external release ZIP.

Public Privacy Policy URL

Configured GitHub Pages URL:

https://gevorg-glechyan.github.io/window-size-extension/privacy-policy/

Open this URL before submission and paste it into the Developer Dashboard privacy policy field only after this docs update is published and the URL is reachable.

Single Purpose

Window Resize Manager lets users read current Chrome window and viewport dimensions, show live numeric measurements on the active page, then resize the current normal Chrome browser window from a toolbar popup using built-in presets, locally saved custom presets, or manually entered dimensions.

Extension Permissions

The Chromium manifest requests these Chrome extension permissions:

• windows: read and resize the current normal Chrome browser window.
• storage: save custom presets, recent custom dimensions, and resize target settings locally in Chrome extension storage.
• scripting: run a one-shot numeric viewport measurement probe for the popup readout and viewport resize mode when Chrome allows page script access.

The manifest also declares a packaged content script and host access for http://*/* and https://*/*. It does not declare optional host permissions, DevTools APIs, or the broad tabs permission.

Host Access Justification

Host access to regular HTTP and HTTPS websites is required to show the live frame and viewport measurement overlay while the user resizes a Chrome window. The packaged content script listens only for resize events, creates extension-owned overlay elements, and reads only the numeric outerWidth, outerHeight, innerWidth, and innerHeight values. It requests the sender tab’s numeric page zoom factor locally from the extension service worker so the two measurements use a comparable coordinate system. The script does not inspect page content or elements, and it does not read, store, or transmit URLs, page data, the tab ID, selected text, cookies, form data, or website storage.

The overlay displays the packaged 32-pixel extension icon and an Open action for the toolbar popup. Only that icon is declared as a web-accessible resource, using Chrome’s per-session dynamic extension URL; no scripts or user data are exposed as web-accessible resources.

Permission Justifications

Use text consistent with:

windows: Window Resize Manager uses this permission to read the current Chrome window size and resize the current normal browser window after the user chooses a built-in preset, saved custom preset, or custom size.

storage: Window Resize Manager uses this permission to store user-created presets, recent custom dimensions, and the selected resize target mode locally on the user’s device.

scripting: Window Resize Manager uses this permission to run a one-shot numeric viewport measurement probe for the popup readout and viewport resize mode when Chrome permits script access.

Host access: Window Resize Manager loads its packaged content script on regular HTTP and HTTPS websites. The script listens only for window resize events, reads numeric frame and viewport dimensions, requests the current numeric page zoom factor locally, and creates an isolated, automatically fading overlay from extension-owned elements. It does not read page content, selected text, full URLs, cookies, form data, or website storage.

Remote Code Declaration

Select: No, the extension does not use remote code.

Explanation:

The extension does not load or execute remotely hosted extension code. The toolbar popup, background service worker, React bundle, dependencies, fonts, and icons are packaged inside the extension ZIP. The only automatic remote connection is explicit cookieless usage analytics sent to PostHog EU Cloud. The popup can open the Window Resize Manager, Screenshot Capture Studio, or PostHog Debugger Chrome Web Store listing, or the user’s email app, only after the user selects the corresponding link.

Data Types to Disclose

Recommended disclosures:

• User activity: yes. The external build sends explicit cookieless extension usage analytics such as popup opens, resize requests and outcomes, custom preset actions, resize target setting changes, rating or feedback action clicks, and cross-promotion impressions or clicks. Cross-promotion properties contain only source extension, target extension, and popup-footer placement; they do not include destination URLs.
• Website content: no. The extension does not collect page content, selected text, form data, or website storage.
• Web browsing activity: no. Analytics events do not include full URLs, tab titles, browsing history, or page origins.
• Personally identifiable information: no. Analytics events do not include names, emails, account data, cookies, stable personal identifiers, preset names, or exact dimensions.
• Authentication information, financial information, health information, personal communications, and precise location: no.

Do not select data categories that are not intentionally accessed by the extension unless the product behavior changes.

Data Use Certification

Use text consistent with this:

Window Resize Manager uses collected extension analytics only to understand and improve extension behavior, reliability, and feature adoption. It does not sell, share, transfer, or use collected data for advertising, profiling, credit worthiness, or unrelated purposes. User-created presets, recent custom dimensions, selected resize mode, viewport measurements, and window dimensions remain local to the user’s browser and are not transmitted.

Privacy Policy Consistency Check

Before submission, confirm that the published privacy policy states:

• what local data is stored in Chrome extension storage;
• that user-created presets and settings are not synced to an account or cloud service;
• that both build variants send explicit cookieless PostHog usage analytics;
• that analytics exclude page content, selected text, full URLs, tab titles, preset names, exact dimensions, raw error messages, cookies, website storage, and stable personal identifiers;
• that the Chrome Web Store and feedback-email destinations open only after an explicit user action, are not prefetched, and do not expose ratings, email content, or browsing data to the extension;
• that scripting is used only for one-shot numeric viewport measurement;
• that regular-website host access and the packaged content script are used only for resize detection and the extension-owned live overlay;
• that only the packaged 32-pixel extension icon is exposed as a dynamically addressed web-accessible resource for that overlay;
• that no broad tab access, ads, autocapture, session replay, surveys, accounts, billing, or cloud sync are part of the current product.