Horus Fetch Privacy Policy

What Horus Fetch handles

When you explicitly start a download, Horus Fetch may handle only the information needed to complete that transfer on your device. Depending on the site and transfer, this may include:

• the file URL or page URL;
• the page title or filename hint;
• the referring page;
• direct media URLs already requested by the browser;
• request details needed to repeat the same download, such as relevant cookies, authorization headers, query parameters, or POST data;
• local app settings, pairing state, download history, and diagnostic logs stored on your machine.

How it is used

Horus Fetch uses this data to send a download from the browser to the local desktop app, start or resume the requested transfer, show status, and generate optional local diagnostics.

Horus Fetch does not sell your data and does not use download request data for advertising, profiling, or unrelated analytics.

Where the data goes

For normal operation, the browser extension sends transfer data only to the Horus Fetch desktop app on the same device. Horus Fetch does not send download request data, cookies, or authorization headers to Horus servers as part of normal operation.

When Horus Fetch downloads a file for you, it sends the request back only to the original source website that you chose to download from.

Diagnostics

Horus Fetch does not require mandatory telemetry for core download features. If you export a support bundle, sensitive values should be redacted before the bundle leaves your machine.