Privacy Policy
Effective date: August 9, 2026
PixelFlow is a local-first browser extension that helps users find, preview, organize, and download images available on the current page. This policy explains how PixelFlow handles data when the extension is used.
1. Single purpose and user control
PixelFlow analyzes a page only after the user explicitly opens the extension or starts a scan. It does not continuously monitor browsing activity or analyze pages in the background without a user action.
2. Image and page data
To provide its core features, PixelFlow reads image-related information from the current page, including image URLs, dimensions, formats, and source types. This information is used only within the active extension session to show previews, apply local filters and selections, and download images chosen by the user.
PixelFlow:
- does not upload images or image information to PixelFlow servers;
- does not persistently store image URLs or image content;
- does not store page URLs, domains, or browsing history;
- does not maintain its own download history; and
- does not send page or image information to the analytics provider.
The browser and the website hosting an image may make their normal network requests when an image is displayed or downloaded. The browser may also retain download records according to the user's browser settings. PixelFlow does not copy those records into a separate history.
3. Session-only technical state
PixelFlow uses the browser's session-scoped extension storage to remember only the numeric tab/window identifiers and boolean state needed to keep the Side Panel connected to the user-authorized tab. This state does not contain page URLs, domains, image URLs, image content, file names, or browsing history. It is not synchronized to a user account and is not used as persistent product data.
4. Anonymous product analytics
PixelFlow uses Mixpanel for anonymous product analytics so the developer can understand whether the extension's core workflow is functioning and being used. Analytics is sent over HTTPS. A random session identifier is generated in memory and is not persisted between extension sessions. Mixpanel requests use ip=0 to disable IP-based geolocation enrichment.
PixelFlow sends only anonymous product-usage events related to opening the extension, scanning, filtering, selecting images, and starting or completing downloads. Only the following aggregate or enumerated properties are permitted:
- image count;
- selected/downloaded item count;
- successful and failed download counts; and
- selected size and format filter values.
Analytics does not receive:
- page URLs or domains;
- image URLs or image content;
- browsing history;
- download file names; or
- the image data objects used by the extension.
PixelFlow does not use analytics data for advertising, cross-site tracking, user profiling, sale, or data brokering. PixelFlow does not maintain a separate analytics database. Anonymous event retention is governed by the Mixpanel project configuration and Mixpanel's privacy policy. Disabling or uninstalling PixelFlow stops future analytics events from the extension.
5. Browser permissions
PixelFlow requests only the permissions required for its user-initiated workflow:
| Permission | Purpose |
|---|---|
activeTab | Grants temporary access to the tab on which the user invokes PixelFlow. |
scripting | Injects the local Content Script into the user-authorized page when needed to analyze images. |
downloads | Sends images selected by the user to the browser's download manager. |
sidePanel | Provides the PixelFlow interface in the browser Side Panel. |
storage | Stores only session-scoped tab/window identifiers and boolean coordination state required by the Side Panel workflow. |
https://api.mixpanel.com/* | Allows the anonymous product-usage data described above to be sent to Mixpanel. |
PixelFlow does not request <all_urls>, tabs, webRequest, or access to browsing history.
6. Data sharing and security
The only third-party product-data recipient is Mixpanel, and it receives only the anonymous product-usage data and permitted aggregate properties described in this policy. PixelFlow does not transfer page or image data to the developer or to Mixpanel. PixelFlow does not use remotely hosted executable code.
PixelFlow's use of information received through browser APIs is limited to providing and improving the extension's user-facing, single-purpose functionality. That information is not sold, used for personalized advertising, or made available for unrelated human review, except where required for security, legal compliance, or user-requested support.
7. Changes and contact
This policy will be updated if PixelFlow's data practices materially change. The effective date at the top of this document identifies the latest revision. Questions about this policy can be submitted through the support contact published with PixelFlow's Chrome Web Store or Microsoft Edge Add-ons listing.