Privacy Policy

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

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;
• in the internal build only, a user-selected same-document element or visible scrollable container while the premium-element-capture feature flag is enabled;
• 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, JPEG, or PDF;
• copying the edited PNG to the clipboard after the user chooses copy;
• preparing a local issue draft and screenshot preview before a provider submission;
• submitting a reviewed Linear issue draft and edited screenshot image only after the user authorizes Linear and chooses submit;
• storing short-lived capture handoff data so the preview editor can load the current screenshot and bulk capture results can support local thumbnails, batch saving, and preview queues during the current Chrome session.

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.

For finished bulk capture jobs, the extension keeps the local bulk job record and referenced captured images in chrome.storage.session until the earliest of: the user choosing Clear results, the user starting another bulk capture job, or Chrome clearing session storage at the end of the browser session. Clearing bulk results deletes only local extension session data and does not delete files already saved to disk. There is no time-based bulk-results auto-delete in this version.

The extension uses chrome.storage.local for local settings such as default capture mode, default export format, local export folder, appearance mode, and the selected issue creation service. If you choose a native local export folder, Chrome stores the browser-managed folder handle in local IndexedDB so future explicit PNG, JPEG, and PDF saves can write to that folder when permission is still available. If permission is unavailable, the extension falls back to the configured Downloads subfolder. While the custom filename pattern feature flag is disabled, custom filename pattern settings are not an active public-listing feature.

The internal-only selected-element capture experiment uses a temporary random local marker on the selected element during capture, then removes it after the capture is restored. The marker, element text, selectors, page content, and full URLs are not sent to analytics or remote services.

The preview editor can prepare an issue draft with the edited screenshot rendered as an in-memory local browser blob. Opening or canceling that draft does not transmit screenshot pixels, title, description, reference URL, destination, provider fields, or other user-entered issue text. If the user authorizes Linear, the extension stores only the short-lived access token returned by Linear. If the user then submits a Linear draft, the extension sends the reviewed title, description, optional reference URL, privacy-safe screenshot context, and edited screenshot image to Linear through the upload proxy. If the user authorizes Jira, the extension stores only the short-lived access token returned through the bundled token-exchange Worker. If the user then submits a Jira draft, the extension sends the reviewed title, description, optional reference URL, selected Jira site/project/issue type, privacy-safe screenshot context, and edited screenshot image to Atlassian. GitHub issue submission is not connected and fails closed while preserving the draft on screen.

Data Sharing

The extension does not sell screenshot pixels, page content, selected text, full page URLs, filenames, clipboard contents, saved files, cookies, or account data to third parties. Screenshot pixels are transmitted to a third party only when the user explicitly submits a reviewed Linear issue draft with the edited screenshot image through the Linear upload proxy, explicitly submits a reviewed Jira issue draft with the edited screenshot image through Jira's attachment API, or when an explicitly chosen cloud-upload provider action is enabled and used.

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 the current capture and export 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 extension may store the user's selected extension UI language locally when the user changes it in Settings. The selected language and Chrome locale are not sent in analytics events or feature-flag requests.

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. The internal-only premium-element-capture and premium-element-page-chrome-hiding flags follow the same feature-flag pattern as other premium features and are targeted in PostHog with build_variant = internal.

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 selects a cloud service in Settings and explicitly chooses the preview editor Upload action. In that flow, the extension may authorize with Google Drive or Dropbox and send the edited PNG plus generated filename to the selected provider and folder 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.

Linear issue creation runs only after the user reviews a local issue draft and authorizes Linear, then chooses submit. Authorization uses the product-owned Screenshot Capture Studio OAuth application, so users authorize access to their own Linear workspace without creating a Linear developer application. The extension may load Linear teams for selection, load project options after the user selects a team, resolve the selected team, optional selected project, and send the edited screenshot image to the configured Cloudflare Worker upload proxy at https://screenshot-linear-upload-proxy.gevorg-glechyan-company.workers.dev. The proxy uses the user's short-lived Linear access token to request Linear file upload metadata, performs the signed upload to Linear storage, and returns the Linear asset URL without storing the screenshot. The extension then creates the issue with that Linear asset URL in the description sent to https://api.linear.app. Builds without an upload proxy fall back to a bounded markdown data image for local development. The extension does not submit drafts in the background, persist Linear account details, persist refresh tokens, or send Linear or Jira issue links to analytics.

Jira issue creation runs only after the user reviews a local issue draft and authorizes Jira, then chooses submit. Authorization uses the product-owned Screenshot Capture Studio Atlassian OAuth application, so users authorize access to their own Jira Cloud site without creating a Jira developer application. The Atlassian authorization response is routed through the bundled Cloudflare Worker callback at https://screenshot-jira-oauth-token-proxy.gevorg-glechyan-company.workers.dev, which validates the Chrome identity redirect URL before forwarding the code back to the extension. The same Worker exchanges the code for a short-lived Jira access token without bundling the Atlassian client secret in the extension. After authorization, the extension may load Jira sites, projects, and issue types, then send the reviewed issue draft and edited screenshot to https://api.atlassian.com only after the user chooses submit.

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, internal selected-element capture, and full-page scrolling;
• storage: stores short-lived capture handoff data, local extension settings, the local export folder preference, browser-managed native folder handle, and the selected issue creation service;
• clipboardWrite: copies the edited screenshot to the clipboard only after the user chooses copy;
• downloads: saves explicit local PNG, JPEG, and PDF exports into the configured Chrome Downloads subfolder when native folder access is unavailable;
• identity: supports explicit cloud provider authorization flows when cloud upload is enabled and explicit Linear authorization from a reviewed issue draft.
• tabs: lists and activates tabs in the current Chrome window only after the user starts the premium bulk tab capture workflow from the guided popup dialog. Bulk tab capture runs locally, one tab at a time, with jobs capped at 30 tabs split into six-tab batches. The same premium bulk workflow can reuse one user-drawn selected-area rectangle and scroll offset across selected open tabs. These workflows store local job status, selected-area geometry, scroll offset, and preview handoff ids without sending tab URLs, page content, or screenshot data to a remote service.

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, email gevorg@glechyan.com.