WarpFetch Legal

Privacy Policy

This Privacy Policy explains how WarpFetch handles information when you use the macOS app, supported browser integrations (Safari extension and optional WarpFetch Chrome extension), the optional local browser bridge, Spotlight indexing, and Apple-managed subscription or purchase features.

Effective date: April 9, 2026 Applies to: WarpFetch for macOS and supported WarpFetch browser integrations Approach: Local-first, user-controlled features
Most data stays on your Mac WarpFetch stores download history, preferences, tags, receipts, and recovery state locally on your Mac.
Sensitive browser data is opt-in Cookies, authorization headers, and referrers are excluded from browser capture by default.
Payments are handled by Apple Subscriptions, trials, lifetime unlocks, billing, and payment details are processed through Apple's App Store systems.

1. Scope

WarpFetch is a macOS download manager. It can receive downloads that you add manually, import in batches, send from supported browser integrations such as the Safari extension and the optional WarpFetch Chrome extension, route through the optional local browser bridge, and index completed files for on-device Spotlight search. This Privacy Policy covers the information involved in those features.

When you use a supported WarpFetch browser integration, the browser integration can send supported download requests to the local WarpFetch app running on the same device through http://127.0.0.1. The browser handoff flow is intended for local-device communication and not for routing those requests through WarpFetch-operated remote servers.

This policy does not govern the privacy practices of websites, file hosts, CDNs, cloud providers, or Apple's services. When you download from a third-party source, that source may receive requests from your device according to its own privacy practices.

2. Data We Handle

2.1 Data you enter or choose

  • Download URLs, file names, tags, notes, checksum values, workspace selections, and scheduling details that you enter in WarpFetch.
  • Save locations and folders that you choose, including tag-specific folders, workspace folders, or network storage locations you authorize.
  • Optional request metadata you provide, such as User-Agent, Referer, Cookie, usernames, or passwords.

2.2 Data processed to run downloads

  • Download progress, status, connection counts, speed samples, timestamps, retry state, resume state, and destination information.
  • Response metadata such as content type, redirect destinations, file size information, range support, and server-provided file-name suggestions.
  • Checksums, receipt details, and history records for completed or failed downloads.

2.3 Saved credentials

If you choose to save site credentials for a host, WarpFetch stores them in the macOS Keychain so they can be reused for later downloads from that host.

Saved site credentials use macOS Keychain

2.4 Clipboard monitoring

Clipboard monitoring is optional. If you enable it, WarpFetch checks the clipboard for supported direct download links so it can prefill the add-download flow. Clipboard monitoring is intended to detect direct file links, not to read unrelated clipboard contents for analytics or advertising.

Optional feature

2.5 Browser bridge and browser-assisted capture

If you enable the local browser bridge and use a supported WarpFetch browser integration such as the Safari extension or Chrome extension, WarpFetch can receive a locally forwarded payload that may include the URL, file name, MIME type, page title, save path, referrer, cookies, and request headers supplied by the browser integration.

Sensitive browser request data, including cookies and authorization headers, is disabled by default. It is only included if you explicitly enable that behavior in Settings.

The browser integration may also read the active tab URL or a supported browser download URL so it can prefill or hand off the download you asked WarpFetch to manage. WarpFetch uses that browser-derived data only for the requested download handoff and related download management features.

The Safari extension stores a small amount of operational diagnostic data locally in the browser's own storage (such as whether the content script was recently active or whether a download cancel succeeded). This diagnostic data records only the hostname of the relevant site — never the full URL, path, or query string — so your browsing history is not retained in extension storage.

The optional cookies permission in the Safari extension is used solely to forward session cookies to the WarpFetch app on the same Mac via localhost (127.0.0.1) so that authenticated downloads work correctly. Cookies are never transmitted to any WarpFetch-operated server or any third party.

2.6 Spotlight indexing

WarpFetch can index completed downloads into the macOS Spotlight index on the same Mac so you can find them through system search. Indexed metadata can include the file name, file type, source host name, tags, workspace name, file size, and completion date.

WarpFetch does not place the full original download URL, signed query strings, or secret tokens into Spotlight metadata.

2.7 Apple-managed purchase and entitlement data

WarpFetch uses Apple's StoreKit and App Store systems to determine whether a trial, subscription, or lifetime unlock is active. Payment processing, billing information, subscription renewal, and purchase restoration are handled by Apple, not by WarpFetch directly.

3. How We Use Data

  • To start, schedule, accelerate, pause, resume, retry, verify, and complete downloads that you request.
  • To organize files using your chosen folders, tags, workspaces, naming rules, and post-download actions.
  • To maintain download history, receipts, and recovery information so interrupted downloads can continue safely.
  • To support optional features you enable, such as browser-assisted capture, clipboard suggestions, Spotlight indexing, Finder tags, notifications, Music import, and saved credentials.
  • To determine access to paid features through Apple's StoreKit APIs.

Based on the current app implementation, WarpFetch does not include third-party advertising SDKs, analytics SDKs, or cross-app/cross-site tracking libraries.

Browser-derived data is used only to hand off supported downloads to the local WarpFetch app, preserve authenticated download context when you explicitly opt in, and show browser bridge status. WarpFetch does not sell that data and does not use it for advertising, profiling, or unrelated analytics.

4. Permissions and Device Access

  • Notifications: WarpFetch requests notification permission only when needed for download alerts or when you test notifications.
  • Folder access: WarpFetch uses standard macOS folder pickers when you choose a save location, default folder, or tag folder. It stores security-scoped bookmarks so it can continue writing to those folders later.
  • Browser bridge: The local browser bridge remains off unless you enable it.
  • Browser integration permissions: Supported WarpFetch browser integrations may use browser permissions to detect supported downloads, read the current tab URL for manual handoff, store extension settings locally, read site cookies when required for authenticated downloads, and communicate with the local WarpFetch app over localhost.
WarpFetch is designed so sensitive features are turned on by you, not silently enabled in the background.

5. When Data Leaves Your Device

Most WarpFetch data stays on your Mac. Data leaves your device only in the following situations:

  • Browser handoff to the local app: If you use a supported WarpFetch browser integration, the selected download request data is sent to the local WarpFetch app on the same device through localhost so the app can start the download.
  • Download requests: When you download a file, your Mac contacts the file host or source server and may send the request metadata required to complete that request.
  • App Store purchases: Subscriptions, trials, restores, and entitlement validation are handled through Apple services.
  • Support communication: If you contact support, the information you choose to send will be used to respond to your request.
Important: If you enable sensitive browser capture, cookies, authorization headers, and related session context may be processed so authenticated downloads can work correctly.
WarpFetch does not use the browser handoff flow to transmit your selected download requests to WarpFetch-operated remote servers for advertising, profiling, or unrelated analytics.

6. Security and Storage

  • Saved site credentials are stored in the macOS Keychain.
  • Download records, tags, preferences, receipts, and recovery state are stored locally on your Mac.
  • Downloaded files are stored in the save locations you choose or authorize.
  • The local browser bridge listens only on localhost when enabled and is designed for local-device communication.
  • Spotlight indexing is local to the Mac where indexing is enabled and uses the system Spotlight index on that device.
  • Supported WarpFetch browser integrations use local communication with the app over localhost. The Safari extension is bundled with the macOS app. The Chrome extension is installed separately through the Chrome Web Store. Neither integration is designed to download or execute remote code as part of the browser-to-app handoff flow.

No method of storage or transmission is completely secure. You are responsible for choosing trusted download sources and protecting access to your Mac, Apple account, and saved credentials.

7. Your Choices and Controls

  • You can turn clipboard monitoring on or off in Settings.
  • You can enable or disable the local browser bridge in Settings.
  • You can keep sensitive browser headers disabled, or opt in only when needed.
  • You can install, disable, or remove a supported WarpFetch browser integration through your browser's extension controls.
  • You can remove saved credentials from the app's credential manager.
  • You can delete downloads, history items, tags, workspaces, and local files according to the controls WarpFetch provides.
  • You can manage or cancel subscriptions through your App Store account settings.

8. Children's Privacy

WarpFetch is not directed to children. If you believe information from a child has been provided through the app or related support channels inappropriately, contact us so we can review and address the issue.

9. Changes to This Policy

We may update this Privacy Policy when WarpFetch's features, data practices, or legal obligations change. When we make material updates, we will revise the effective date above and publish the updated policy at the privacy-policy URL used by the app.

10. Contact

For privacy questions or support related to WarpFetch, contact: