See what DownF observes during a compatibility check
DownF processes the public URL, chosen output, job state, coarse timing, byte totals, and privacy-protected operational identifiers needed to compare formats and control abuse. Prepared media is temporary, while display preferences can remain in your browser. The policy below separates server records, device-only data, contact messages, and third-party platform activity.
Effective 26 August 2026. This notice explains the information used by DownF, why each record is necessary and which settings remain under your control.
1. What this policy covers
This policy applies to the DownF website, compatibility checker, source directory, continuation links and contact form. The privacy rules of a media platform remain that platform's responsibility.
2. Information processed
- Submitted links: the public URL is sent to the resolver so it can detect the source and return formats.
- Operational data: request identifiers, coarse timing, status, byte totals and privacy-protected visitor or IP hashes help prevent abuse and diagnose failures.
- Contact messages: name, email, subject, optional public URL and message are stored in the private control center.
- Continuation links: an opaque token maps to the cleaned public media URL in the control database. The URL is not embedded in the token or QR code.
- Device-only preferences: recent-link history, format preference and private-mode choices stay in browser storage unless you clear them.
- Local media tools: a file selected on the local-tools page is read into temporary WebAssembly memory in your browser and is not uploaded to downf.io. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
DownF uses limited request data to return compatibility findings, route work safely, enforce fair quotas, investigate failures and respond to support. Aggregated health signals also help defend the service from automation abuse.
4. Temporary media and retention
DownF delivery URLs have a short lifetime, and cleanup removes prepared assets from media storage. Reliability records are kept only while useful, while help messages remain until handled. Ask support to remove an opaque continuation record.
5. Service providers and upstream platforms
A DownF request may contact the submitted platform, hosting systems, databases, configured egress routes and optional advertising or donation partners. Credentials and internal routing details never appear in a public result URL.
6. Cookies and local storage
DownF uses a first-party visitor cookie for quotas and abuse defense. Your browser may remember preferences and recent links, unless Private Mode is enabled. Browser controls can clear both.
7. Your choices
Avoid sending DownF any URL or message you do not want processed. Private Mode limits local history, browser controls clear stored preferences and the contact form handles access, correction or deletion requests. Open the contact form.
8. Children, security and changes
DownF is intended for users aged 13 or older. We apply reasonable safeguards, cannot guarantee perfect internet security, and will date this notice again when material terms change.