Privacy statement

Swifty Download Manager (SDM) does not send personal information, browsing activity, download URLs, filenames, usage data, analytics, or telemetry to the developer and does not sell that information. Network requests to your chosen download source are described below. The app requires no account and contains no advertising, tracking, or developer-operated crash-reporting service.

Download URLs, filenames, destinations, progress, history, diagnostics, engine preferences, and security-scoped bookmarks are stored locally in the app’s sandbox. You control this information through the app and the operating system.

The browser extensions store two file-type preference lists in the current browser profile’s local extension storage. These settings control automatic download handling and are not synchronized across browsers or sent to the developer. This preference storage does not contain download URLs, browsing history, cookies, or authentication data. You can change the lists or restore their defaults in the extension’s Download settings page.

On HTTP and HTTPS pages, the Chrome and Safari extensions locally inspect user-initiated link targets, the current page URL, an optional suggested filename, and eligible direct-download navigations or click-triggered window openings. When you choose or initiate a supported download, the extension reads website cookies matching that download URL, including authentication cookies, and obtains the browser User-Agent. It sends these with the download URL, optional filename, and source website origin to the local SDM app so the app can retrieve the selected file using your browser session. The full source page path and query are not passed to the app. Cookie values and download URLs may contain identifiers issued by the source website. The extensions do not read form input, POST request bodies, or arbitrary Authorization/custom headers. A recent-click timestamp may be held in memory for up to 30 seconds to avoid intercepting unrelated window openings; it is not retained as activity history. The extensions do not persist browsing history or send this information to a developer-operated server.

Chrome sends the handoff through an encrypted connection on your device. Safari temporarily stages an encrypted file in storage shared with the app; the app deletes it when consumed, rejects expired handoffs, and cleans up expired files on subsequent use. The custom URL scheme activates the app with a short-lived ticket and key, without embedding the cookie payload.

SDM uses browser cookies and request headers in memory for the selected download and does not save them in download history. Cookies follow domain, path, Secure, and expiration rules, including on redirects. Keep SDM running for browser-session downloads; after restarting the app, send them again from the signed-in browser. URLSession uses a foreground session for these downloads and starts a fresh transfer when resuming a paused browser-session task. Public downloads retain their normal background/resume behavior.

When you start a download, SDM connects directly to the source you selected so it can retrieve the file. For browser-session downloads, the request includes matching cookies, the browser User-Agent, and the source origin where available. An HTTPS browser-session download cannot redirect to HTTP. The source website and your network provider may process network activity under their own terms.

Before automatically handling a candidate file link or navigation, the browser extension may send a HEAD request to the selected source to check its response headers. The browser may include matching website credentials under its cookie rules. The check does not fetch the file body, times out after three seconds, and leaves failed checks in the browser. File-type preferences apply to direct file links; the extension does not capture embedded video playback or streaming segments.

The Chrome extension’s use of information received from Chrome APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.

This website does not use analytics, advertising, tracking pixels, cookies, or externally hosted fonts. Your language and appearance preferences may be stored locally in your browser and are never transmitted by SDM. If the site is hosted by a third-party platform, that platform may process standard request logs under its own terms.

If SDM’s privacy practices change, this statement will be updated before a release containing that change is made available.