Privacy Policy

1. Policy Content

FlowGet Privacy Policy

Effective Date: June 20, 2026

Last Updated: June 20, 2026

Company / Legal Entity: FlowGet Download Manager

Website: https://flowget.xyz

Contact: [email protected]

1. Introduction

FlowGet is committed to protecting your privacy. This Privacy Policy explains how we collect, use, store, and protect information when you use the FlowGet website, customer portal, desktop application, and FlowGet Browser Integration extension.

FlowGet Browser Integration works with the FlowGet desktop app to help users detect downloadable files, media streams, playlists, and browser download tasks, and send selected downloads to the local FlowGet desktop app.

This policy explains what information may be accessed, why it is used, how it may be transferred, and what choices users have.

2. Scope of This Policy

This Privacy Policy applies to:

• The FlowGet website.
• The FlowGet customer portal.
• The FlowGet desktop application.
• The FlowGet Browser Integration extension for supported browsers.

Some sections below specifically describe the browser extension because browser extensions may access page, tab, download, and media-related information to provide download-management features.

3. Local-First Architecture

FlowGet is designed as a local-first download manager. Your download queues, download history, RSS feed configurations, proxy settings, downloaded files, save paths, and related download records are primarily stored on your local device.

We do not use our servers to sell, profile, or advertise based on your download history, target URLs, file paths, or private download activity. FlowGet remote services are used only for product-related functionality such as account access, licensing, activation, subscription status, updates, security, and support.

4. Information We Collect

When you interact with FlowGet services, we may collect limited information needed to provide, secure, and maintain the product. This may include:

• Account Information: Your name, email address, encrypted credentials, and account-related information when you create or use a FlowGet account.
• Billing and Subscription Information: Order details, subscription status, invoice metadata, plan information, renewal status, and payment confirmation details. Payment credentials, such as full credit card numbers, are handled by secure payment processors and are not stored by FlowGet.
• Licensing and Device Activation Data: License status, activation records, device limits, and cryptographic hardware identifiers generated by the client to help bind licenses to authorized devices. These identifiers are designed for license validation and do not contain readable personal device files, downloaded files, or private download content.
• Product and Security Diagnostics: Basic technical information needed to troubleshoot activation, updates, connection issues, crashes, or security-related problems. Diagnostic data is used to maintain and improve FlowGet functionality and is not used for advertising, ad targeting, or resale.

5. FlowGet Browser Integration Extension

FlowGet Browser Integration helps users send downloads from the browser to the local FlowGet desktop app.

Depending on the feature used, the extension may:

• Detect browser download tasks.
• Detect downloadable links on a page.
• Detect media URLs, video/audio streams, HLS/DASH manifests, and playlist links.
• Show download options to the user.
• Send selected or automatically intercepted downloads to the local FlowGet desktop app.
• Store extension settings, such as automatic capture preferences and file type rules.

The extension uses this information only to provide user-facing download-management features and related security functionality.

6. Information the Extension May Access

Depending on the website, browser feature, and FlowGet feature used, the extension may access the following types of information:

• Current page URL and tab URL.
• Download URLs.
• Media, video, audio, playlist, HLS/DASH, and temporary signed media URLs.
• File names and suggested file names.
• Page titles, video titles, playlist titles, and link text when needed to identify or display a user-selected download.
• Selected download metadata, such as URL, filename, size, MIME type, and download state.
• Selected request information needed to reproduce a user-requested download in the desktop app, such as referer, user-agent, range, authorization-related headers, or other required request headers.
• Cookies only when required by a website for a user-requested authenticated download or media stream.
• Extension settings stored locally in the browser, such as automatic capture preferences and file extension filters.

FlowGet does not use this information to build advertising profiles or track users across websites for advertising.

7. Information Sent to the Local FlowGet Desktop App

When the user sends a download to FlowGet, or when a configured automatic capture rule applies, the extension may send download-related information to the local FlowGet desktop app installed on the user’s device.

This may include:

• Download URLs and media URLs.
• Temporary signed media URLs.
• Page URLs and referer URLs.
• File names and suggested file names.
• Page, media, video, or playlist titles.
• Selected quality or format information.
• Playlist metadata and selected playlist items.
• User-selected batch link lists.
• Cookies or selected request headers only when needed for the user-requested download to work outside the browser.

This transfer is used so the local desktop app can show a confirmation window, process the requested download, resume or manage the download, or provide related download-management functionality.

8. Native Messaging and Localhost Communication

The FlowGet Browser Integration extension communicates with the installed FlowGet desktop app through browser native messaging and a token-protected localhost bridge.

The localhost bridge runs on the user’s own device, such as at 127.0.0.1, and is used for communication between the browser extension and the local desktop app.

FlowGet uses a private bridge token to help prevent unauthorized access to the local bridge. Normal webpages do not receive the private bridge token. The token is not intended to be placed in webpage content, shared with websites, or used for advertising or analytics.

9. Cookies and Request Headers

Some downloads only work when the request includes cookies or specific request headers from the website where the user has access to the content.

For example, a user-requested download may require:

• Session cookies.
• Referer header.
• User-agent header.
• Range header.
• Authorization-related headers.
• Other website-required request headers.

When required for a user-requested download, FlowGet Browser Integration may send these cookies or headers to the local FlowGet desktop app so the app can perform the download.

Cookies and sensitive request headers are used only for the requested download functionality. FlowGet does not collect cookies or request headers for advertising, cross-site tracking, resale, or unrelated profiling.

10. Download URLs and Media URLs

FlowGet Browser Integration may detect and send download URLs, video/audio media URLs, HLS/DASH manifest URLs, segment URLs, playlist URLs, and temporary signed media URLs to the local FlowGet desktop app.

Some of these URLs may contain temporary tokens or signatures created by the source website. FlowGet uses these URLs only to complete or manage the download requested by the user. Temporary signed URLs may expire according to the source website’s own rules.

11. Local Storage

The browser extension may store settings locally in browser extension storage. These settings may include:

• Automatic download capture enabled or disabled.
• File type capture rules.
• Extension preferences.
• Browser integration settings.

The FlowGet desktop app may store local app settings and download records, such as download history, URLs, filenames, save paths, progress, status, and related metadata, depending on the desktop app feature used and the user’s settings.

Cookies and sensitive request headers, when used, are used for user-requested download processing. Users should treat downloaded records, diagnostic logs, and exported support files as potentially sensitive.

12. Data Sent to FlowGet Remote Services

The FlowGet Browser Integration extension is designed primarily to communicate with the local FlowGet desktop app for download handling.

The extension does not use analytics or telemetry in the current version.

The FlowGet desktop app may contact FlowGet remote services for product functionality such as account access, licensing, activation, subscription status, entitlement checks, security, updates, or support-related features.

FlowGet remote services are not used to sell browsing data, download URLs, cookies, or request headers.

13. Logs and Diagnostics

The extension and desktop app may create diagnostic information to help troubleshoot download, connection, or app problems.

Diagnostic information may include technical details such as:

• Download status.
• Error messages.
• File names.
• URLs related to a download.
• Whether cookies or headers were present.

Sensitive values such as cookies, authorization headers, license tokens, and bridge tokens should not be intentionally included in diagnostic logs. Users should review diagnostic logs before sending them to support.

14. Chrome Web Store Limited Use Disclosure

FlowGet’s use of browser extension data is limited to providing and improving user-facing download-management features, maintaining security, enabling communication with the local desktop app, and supporting requested product functionality.

FlowGet does not use browser extension data for unrelated purposes such as:

• Advertising.
• Ad targeting.
• Sale or resale of user data.
• Building unrelated user profiles.
• Cross-site tracking for marketing purposes.

FlowGet only uses extension-accessed data in ways that are disclosed in this Privacy Policy and are related to the functionality users request from FlowGet.

15. Data We Do Not Sell or Use for Advertising

FlowGet does not sell:

• Browsing data.
• Download URLs.
• Media URLs.
• Cookies.
• Request headers.
• Personal information collected through the browser extension.

FlowGet does not use browser extension data, cookies, request headers, or download history for advertising or ad targeting.

16. Data Sharing

FlowGet Browser Integration shares download-related information with the local FlowGet desktop app installed on the user’s device so the app can perform user-requested download tasks.

FlowGet remote services may receive account, license, activation, entitlement, update, device, or support-related data from the desktop app when those product features are used.

FlowGet does not sell personal data.

FlowGet may disclose information if required by law, regulation, legal process, or to protect the rights, safety, or security of FlowGet, users, or others.

17. Data Retention

Extension settings remain in browser extension storage until the user changes those settings, clears extension data, or removes the extension.

Download records and app settings stored by the FlowGet desktop app remain on the user’s device according to the desktop app’s settings and user actions.

Temporary download data is used as needed to process the requested download. Temporary signed media URLs may expire according to the source website’s rules.

18. User Controls and Deletion

Users can control FlowGet Browser Integration in several ways:

• Disable automatic download capture in extension settings.
• Change file type capture rules.
• Use browser controls to disable or remove the extension.
• Clear extension storage through the browser.
• Stop or uninstall the FlowGet desktop app.
• Manage or delete download history and local records in the desktop app, where supported.
• Contact FlowGet support for privacy questions.

19. Security

FlowGet uses security measures intended to protect browser-to-desktop communication, including native messaging and token-protected localhost communication.

Users should install FlowGet only from official FlowGet sources and supported browser extension stores. Users should avoid sharing diagnostic logs, exported settings, or downloaded records if they may contain sensitive URLs, filenames, cookies, headers, or account-related information.

No software or communication method can be guaranteed to be completely secure, but FlowGet is designed to limit use of browser extension data to the functionality described in this policy.

20. Children’s Privacy

FlowGet is not directed to children. FlowGet does not knowingly collect personal information from children through FlowGet Browser Integration.

21. International Users

FlowGet may be used by users in different countries or regions. Privacy rights and obligations may vary depending on the user’s location and applicable law.

Users may contact FlowGet using the contact information below for privacy-related questions.

22. Changes to This Policy

FlowGet may update this Privacy Policy as features, browser requirements, store requirements, or legal requirements change.

When this policy is updated, the “Last Updated” date should be changed. Continued use of FlowGet after an update means the user accepts the updated policy where permitted by applicable law.

23. Contact Us

For questions regarding privacy and policy, please reach out to us via our Contact Us Page.