Privacy & Security

Privacy and security details for the FlowPick browser extension and its local processing workflow.

This page distinguishes extension detection, local processing and optional online services. The Privacy Policy describes the website, analytics, accounts and cloud transfers in more detail.

What stays on your device

The extension detects supported media requests in the browser. The extension has no analytics SDK. Files selected in local conversion, inspection, trimming and transcription tools are processed on your device rather than uploaded to FlowPick for processing.

Local does not mean no network activity: downloads contact the original media server. AI tools need to download their runtime and model, and the website can use analytics. Your source server can see requests made to it.

Extension permissions and request context

Media detection and authorized downloads need the browser permissions shown at installation. The exact permission list can differ by browser and version; review the store listing and your installed extension's permission screen.

Some sources require the original page's Referer or session context. Supported extension workflows may retain request context locally to fetch the media you chose. Do not assume that detecting a URL makes it public or safe to share. FlowPick does not bypass DRM, paywalls or access controls.

Temporary local storage

Processing may use memory, workers, browser-private OPFS storage and a chosen output directory. OPFS data is temporary working storage, not a saved file in your Downloads folder. Save the completed result before closing the page. Browser site-data controls can remove cached models and temporary data; clearing them during a job can interrupt it.

When you choose cloud transfer

Cloud transfer is optional and labelled separately. The submitted source goes to FlowPick infrastructure, which fetches and processes it using the account and quota shown in the product. Personal login cookies and custom authorization headers are not forwarded to that service. A URL can itself contain a private signed token, so only submit a source suitable for the cloud workflow.

Opening the cloud option does not stop your local download. Cloud processing has different access conditions because requests originate from the server's network and region.

Reporting problems without exposing a session

Include the tool name, browser version, error and a small sample you may share. Remove cookies, authorization headers, signed query parameters, private filenames and account details from screenshots and logs. Public GitHub issues are visible to everyone. For a vulnerability, use a private GitHub security advisory.

Review the extension source and release history in the GitHub repository.