The compact data footprint behind QuickDL
QuickDL needs the public URL, detected source, chosen format, job status, and delivery facts to move one request through the utility. Coarse timing and privacy-protected visitor identifiers help enforce limits and find failures. Temporary files are cleaned automatically. Recent-link history and format preferences can stay locally and can be removed with browser controls.
In force from 26 August 2026. QuickDL outlines the small set of data required to run a request and the controls available to you.
1. What this policy covers
QuickDL's utility, supported-service pages, private result records and contact submissions are in scope. The destination platform behind a URL is outside QuickDL's control.
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 QuickDL. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
QuickDL records what one utility request needs for routing, delivery and status reporting. Coarse performance evidence supports troubleshooting, quotas and automated-traffic protection.
4. Temporary media and retention
QuickDL uses expiring signed URLs and automatic cleanup rather than permanent file hosting. It keeps compact reliability records for as long as necessary, retains help messages through review and removes handoffs on request.
5. Service providers and upstream platforms
QuickDL communicates with the URL's platform and the infrastructure that resolves and delivers its output. No API secret or internal provider route is placed in a visitor-facing result.
6. Cookies and local storage
QuickDL needs a first-party identifier for fair limits. Its compact local history and format settings remain in your browser, where Private Mode can pause collection and site controls can clear them.
7. Your choices
QuickDL cannot process a URL you do not submit. Choose Private Mode for one-off checks, clear its browser data when needed and contact support about protected operational records. Open the contact form.
8. Children, security and changes
QuickDL targets visitors 13 or older. We maintain proportionate protections, make no absolute security promise, and mark important privacy edits with their publication date.