Privacy Policy
Last updated: August 24, 2026
At a glance
- If you allow it, we collect product analytics for one purpose: to make Screenshot Editor better for you.
-
Extension analytics are optional and are never sent without your consent.
- ❌ We NEVER send your screenshots, annotation text, clipboard contents, or information about the pages you capture.
- ✅ We only send pseudonymous product-usage and technical information needed to understand how Screenshot Editor is used, improve your experience, and evaluate product experiments.
- Our public website (this website) uses web analytics separately from Screenshot Editor product analytics.
1. Scope
This Privacy Policy explains how Screenshot Editor ("we", "us", or "our"), handles information when you use the Screenshot Editor Chrome extension or visit the official Screenshot Editor website.
The extension and website have different analytics flows. They are described separately below.
2. Screenshot and annotation data
The core workflow—capturing or loading an image, annotating it, cropping it, and exporting it to a file or the clipboard—runs locally in your browser.
Product analytics do not include screenshot or loaded-image pixels, annotation text, clipboard contents, exported image files or filenames, DOM/page contents from the page you captured, exact pointer coordinates, or exact crop geometry.
3. Optional extension product analytics
If you choose to allow product analytics, the extension sends pseudonymous product-usage, reliability, and experimentation information to PostHog. Product analytics are not required to use Screenshot Editor's editing, copy, or download features.
We use this information to understand which features are useful, how the product behaves across browsers, operating systems, devices, screen and viewport sizes, where users are located at an approximate country/city level, how pseudonymous users interact with the product over time, and which product variants work better.
Data sent or retained for extension analytics
| Category | Examples | Purpose |
|---|---|---|
| Product events | Editor opened, capture success/failure, selected tools, shape operations, crop actions, output success/failure, feedback rating. | Measure feature use and reliability. |
| Image and editing context | Image source/type, orientation, coarse image-size bucket, shape type/count, input method, transformation type, crop-reduction bucket, style choices, output destination. | Understand how editor capabilities are used. |
| Text metrics | Character count, line count, and coarse length buckets. Actual annotation text is not sent. | Understand text-tool usage without collecting text content. |
| Application context | App version, extension/web platform, environment. | Compare behavior across releases and targets. |
| Pseudonymous identity and profile | A randomly generated PostHog distinct/device identifier and a PostHog Person profile keyed by that identifier. | Recognize repeat usage and inspect the sequence/history of product events for one pseudonymous installation without requiring an account, name, or email address. |
| Technical and display context | Browser/version, operating system/version, device type, screen dimensions, viewport dimensions, timezone and timezone offset. | Understand compatibility and real UI/display constraints. |
| Approximate location | Country and city derived from network location. | Understand the geographic distribution of users. |
| Product experiments | Remote feature flags, experiment assignments or variants, and pseudonymous information about exposure to a product variant. | Roll out features gradually, compare product variants, and run A/B tests to improve Screenshot Editor. |
| Delivery metadata | Event timestamp, event/deduplication identifier, SDK name/version, processing metadata needed to deliver and store analytics. | Process analytics events correctly. |
Pseudonymous Person profiles
When extension analytics are enabled, PostHog may create a Person profile for the generated pseudonymous device/distinct identifier. This lets us view product events from the same pseudonymous installation as a history or timeline and analyze repeat usage.
Screenshot Editor does not populate that profile with your name, email address, account identifier, screenshot content, annotation text, clipboard contents, or other direct identity.
Feature flags and experiments
If you allow product analytics, Screenshot Editor may retrieve remote feature flags and experiment assignments. We may use them to roll out features gradually, compare product variants, and run A/B tests to understand which experience works better.
If product analytics are not enabled, Screenshot Editor does not participate in analytics-based experiments and uses its default local behavior.
Data deliberately excluded from extension analytics
- the current extension/page URL, URL query parameters, hostname, pathname, and capture-attempt identifiers;
- referrer/referring-domain and campaign/UTM attribution for the extension;
- raw user-agent string and browser-language setting;
- PostHog session/window identifiers;
- postal code, latitude, longitude, GeoIP accuracy radius, and other unnecessarily precise location fields;
- arbitrary SDK/debug metadata or custom Person properties not explicitly part of Screenshot Editor's analytics contract;
- automatic non-product PostHog events.
IP addresses and GeoIP
The extension does not include an IP address as an analytics event property. PostHog receives the network request and can process its source IP at the transport/ingestion layer to derive approximate location. Screenshot Editor's intended retained location data is country and city only; more precise GeoIP-derived fields are outside the intended dataset.
4. Your analytics choice
Extension product analytics are consent-based. Before they are enabled, Screenshot Editor asks whether you want to share pseudonymous product analytics about feature usage, reliability, browser/device/display characteristics, approximate location, behavior over time, and product experiments such as feature flags and A/B tests.
If you decline or have not yet made a choice, external product analytics remain disabled. You can later change the product-analytics setting in Screenshot Editor's Chrome extension options. Turning analytics off stops future PostHog product events and participation in analytics-based experiments; it does not automatically remove events already received before you turned analytics off.
5. Website and future web-app analytics
The public Screenshot Editor website uses web analytics separately from extension analytics. Website or future web-app analytics may include visited page URLs, referrer/referring domain, campaign or UTM attribution, pseudonymous browser identifiers, browser/device information, approximate location, and page/session interaction statistics where configured.
The current main site uses Google Analytics. These web analytics flows do not give Google screenshot pixels, annotation text, clipboard contents, or exported files.
6. Local storage and cookies
The extension can use Chrome/local browser storage for application preferences and, when product analytics are enabled, the pseudonymous PostHog identifier. The PostHog integration is configured to use local storage rather than cookies.
The main site's analytics integration may use first-party cookies for website measurement.
7. Service providers and third-party links
We use PostHog for optional extension product analytics and Google Analytics / Google for website analytics. Screenshot Editor may also link to third-party services such as feedback forms or the Chrome Web Store; their own privacy terms apply when you use them.
We do not use extension product analytics for advertising, and we do not send screenshot or annotation content to analytics providers.
8. Retention and security
Analytics data is retained only for as long as reasonably needed to understand product or website usage, investigate reliability, evaluate product experiments, and improve Screenshot Editor, subject to the retention settings configured with the relevant service provider.
Because analytics identifiers and Person profiles are pseudonymous rather than anonymous, they are treated as analytics data and protected accordingly.
9. Changes to this policy
We may update this Privacy Policy when Screenshot Editor, its analytics, or its service providers change. The date at the top of this page identifies the current version.
10. Contact
For privacy questions about Screenshot Editor, contact us at screenshot.editor.kf@gmail.com.
Project: Screenshot Editor