Privacy Policy for Screenshot Capture Studio

Last updated: 2026-06-28

Screenshot Capture Studio is a Chrome extension for capturing visible areas, selected regions, or full pages from the active Chrome tab, then editing, copying, or saving those screenshots locally.

Summary

Screenshot Capture Studio is local-first. Screenshot capture, editing, clipboard, and local export processing happen in Chrome on the user’s device. The extension does not send screenshot pixels, page content, selected text, full page URLs, filenames, clipboard contents, saved files, or stable personal identifiers to the developer of this extension or to analytics.

The current public listing does not advertise cloud upload or custom filename pattern settings while the premium-cloud-upload and premium-filename-patterns feature flags remain disabled.

Data the Extension Can Access

When the user starts a capture, the extension can access only the active tab through Chrome’s temporary activeTab permission. Depending on the capture mode selected by the user, the extension can access:

the visible pixels of the active tab for visible-area capture;
a user-selected region of the active tab for selected-area capture;
page screenshots captured during local scrolling and stitching for full-page capture;
basic local export metadata, such as capture timestamp, app name, extension version, capture mode, image dimensions, and the captured page origin when Chrome exposes an http or https page URL.

Captured page origin is limited to scheme, host, and port, such as https://example.com. The extension does not embed or send full URLs, paths, query strings, fragments, page content, selected text, filenames, clipboard contents, cookies, account data, or stable identifiers.

How the Extension Uses Data

The extension uses captured screenshot data only to provide its user-facing screenshot features:

opening the screenshot in the local preview editor;
drawing annotations, shapes, text comments, crop edits, and blur redactions;
saving the edited screenshot as PNG or JPEG;
copying the edited PNG to the clipboard after the user chooses copy;
storing short-lived capture handoff data so the preview editor can load the current screenshot.

Local Processing and Storage

Screenshot processing is local to Chrome. The extension stores captured images in chrome.storage.session only long enough for the preview editor to load the current capture. The preview removes the session entry after loading it.

The extension uses chrome.storage.local for local settings such as default capture mode and default export format. While the custom filename pattern feature flag is disabled, custom filename pattern settings are not an active public-listing feature.

The extension does not sell, share, transfer, or transmit screenshot pixels, page content, selected text, full page URLs, filenames, clipboard contents, saved files, cookies, or account data to third parties.

The developer of this extension does not receive the user’s screenshots, saved files, clipboard contents, page content, selected text, or full page URLs through the extension.

First-Party Extension Usage Analytics

The extension may send limited, cookieless product usage events to the developer’s PostHog project at https://eu.i.posthog.com. These events are explicitly allowlisted and contain only low-cardinality extension metadata, such as capture mode, trigger, broad failure category, export format, result, extension version, build variant, and non-premium settings values.

Usage analytics does not use PostHog autocapture, session replay, surveys, heatmaps, implicit page tracking, cookies, browser localStorage, or stable personal identifiers. The analytics session identifier is generated in Chrome session storage and is not persisted across browser sessions.

Analytics and feature-flag requests never include screenshot pixels, page content, selected text, full page URLs, filenames, filename patterns, generated filenames, cloud provider share links, clipboard contents, saved files, account identifiers, or stable personal identifiers.

The same first-party PostHog project may evaluate extension feature flags using the project token, the same session-scoped identifier used for analytics, and the low-cardinality build variant (external or internal). Feature-flag evaluation does not include screenshot pixels, page content, selected text, full page URLs, filenames, filename patterns, clipboard contents, or saved files.

Feature-Gated Cloud Upload

The extension package includes the identity permission for explicit cloud provider authorization flows. Cloud upload is currently feature-flagged off for the public listing and should not appear as an active public feature while the premium-cloud-upload flag remains disabled.

If cloud upload is enabled in a future public release, it is designed to run only after the user explicitly chooses a cloud connection or upload action. In that flow, the extension may authorize with Google Drive, Microsoft OneDrive, or Dropbox and send the edited PNG plus generated filename to the selected provider to create the uploaded file and, where supported, a share link. The extension does not upload in the background, sync folders, read existing cloud file contents, persist refresh tokens, persist provider account details, or send cloud share links to analytics.

Remote Code

The extension does not load or execute remotely hosted extension code. Its extension pages, background service worker, content helpers, and dependencies run from the packaged extension files.

Permissions and Site Access

The extension requests these Chrome permissions:

activeTab: allows a user-initiated screenshot of the active tab without requesting broad host access;
scripting: injects user-initiated helpers into the active tab for selected-area capture and full-page scrolling;
storage: stores short-lived capture handoff data and local extension settings;
clipboardWrite: copies the edited screenshot to the clipboard only after the user chooses copy;
identity: supports explicit cloud provider authorization flows when cloud upload is enabled.

The extension does not request host permissions or optional host permissions.

Limited Use Statement

The extension’s use of data is limited to the user-facing screenshot capture, editing, copy, save, local settings, feature-flag evaluation, and limited extension usage analytics described in this policy and in the Chrome Web Store listing. The extension does not use screenshot data, browsing data, page content, or clipboard contents for advertising, profiling, resale, credit worthiness, or any unrelated purpose.

The use of information handled by this extension complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

Contact

For privacy questions, support, or bug reports, use GitHub Issues:

https://github.com/Gevorg-Glechyan/screenshot-extension/issues