1. Local Processing First

Pixel Flow does not automatically scrape the open web or continuously collect website images in the background on your behalf. Scanning, saving, downloading, exporting, and reverse image search actions are initiated by you on the current page or on assets you select. You should only use Pixel Flow within scopes where you are authorized to access, process, and reuse the relevant images.

Pixel Flow prioritizes your privacy. Your collected image metadata and tags are stored locally in your browser's IndexedDB. We do not have access to this database.

Your local library, tags, download history, and user settings are separated by the currently signed-in Pixel Flow account. Signing out does not delete local library data, and switching accounts does not expose one account's local library to another account.

Data created while signed out is stored in a local guest space. When you sign in, guest data remains separate from signed-in account data. Data cleanup applies to the current account or guest space by default; clearing all local Pixel Flow data requires an explicit choice.

To power hover actions and context-menu workflows, the extension may temporarily cache information about the last image you hovered on, including page URL, image URL, alt text, dimensions, MIME type, source candidates, and, for some inline or embedded assets, a Base64 representation. This cache is kept in browser extension storage on your device and is used to perform the action you request.

2. On-Device AI Recognition

The integrated AI engine (AIDetector) runs on your local machine. Image parsing and feature extraction used for AI recognition are processed in-memory and are not uploaded to remote servers for AI processing. If you actively use Google reverse image search or other external features, temporary uploads or third-party processing may apply as described below.

AI, AIGC, copyright-risk, GPS, software, color, EXIF, and lifecycle signals are technical inferences from available files or metadata. They may be incomplete or incorrect and should not be treated as legal, authorship, ownership, or authenticity determinations.

3. PRO Subscription

To create accounts, verify Creator PRO access, process invitation or redemption rewards, and maintain purchase or grant history, we may process account identifiers such as user ID, client ID, email address, Google account profile data returned through OAuth, authentication tokens, payment customer or transaction identifiers, plan details, discount information, and PRO entitlement logs. Payments are handled securely by the active third-party payment provider. We do not store your credit card information.

4. Backup and Import

Backup files are generated locally and may include your collected image files, standard previews, download history, source URLs, image metadata, user preferences, custom tags, and account ownership information. To protect library privacy, Pixel Flow does not allow a backup exported by one account to be imported into another account. You are responsible for storing, sharing, and deleting backup files securely.

5. Reverse Image Search and Temporary Uploads

When you use Google reverse image search, Pixel Flow may open Google Lens with the image URL directly. If a direct URL cannot be used, the extension may temporarily process and upload an image copy through our API or object storage service to generate a Google Lens URL. This feature is initiated by you and may disclose image content or source information to Google and infrastructure providers involved in the temporary upload.

6. Sync Service

Our sync service and backend APIs handle account status, PRO entitlements, transaction confirmation, redemption codes, invitation rewards, configuration, and index metadata. They do not provide a cloud backup for your raw image library unless a specific feature clearly states otherwise.

7. Extension Permissions and Third Parties

Pixel Flow uses browser extension permissions such as storage, downloads, identity, tabs, context menus, side panel, offscreen documents, scripting, and declarative network rules to provide image collection, analysis, login, download, and export features. Some workflows depend on third-party services, including Google OAuth, Google Lens, payment providers, and hosting or API infrastructure. Those services process data under their own policies.

If Pixel Flow receives user information from Google APIs, our use of that information will comply with the Chrome Web Store User Data Policy, including the Limited Use requirements. Google account information is used only for sign-in, account identification, entitlement sync, and security maintenance. We do not sell it or use it for advertising unrelated to Pixel Flow's user-facing features.

Contact

Privacy questions can be sent to support@joinpixelflow.com.

Pixel Flow Privacy Policy.