EasyF privacy, explained without hidden steps
EasyF sends a pasted public link to the resolver so it can identify the service and list available media. Short-lived job records, aggregate timing, protected visitor identifiers, and byte totals keep the workflow reliable and fair. Contact information is used for support, local preferences stay in the browser where possible, and prepared downloads are removed on a schedule.
Current as of 26 August 2026. EasyF describes its limited data use here in plain language, including the choices available to each visitor.
1. What this policy covers
EasyF includes its guided downloader, catalog and help desk within this policy. External media services operate independently and are not controlled by these terms.
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 EasyF. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
EasyF handles only the information required to guide a request, protect capacity and answer a visitor's message. Anonymous product-health measurements reveal failures without publishing submitted links.
4. Temporary media and retention
EasyF automatically clears its generated files after the configured window. Logs are limited to operational need, help-desk messages stay until completion and private continuation links can be removed by contacting the team.
5. Service providers and upstream platforms
EasyF depends on the submitted media service and ordinary hosting, storage and routing vendors. Advertising or donation providers are used only when configured, without disclosing internal keys in results.
6. Cookies and local storage
EasyF keeps quota protection in a first-party cookie and optional convenience settings in local storage. Private Mode avoids adding history, and clearing site data removes these records.
7. Your choices
EasyF leaves the decision to submit with you. Private Mode avoids new recent-link entries, browser settings clear local data and the help desk accepts privacy requests. Open the contact form.
8. Children, security and changes
EasyF is not designed for children younger than 13. No online system is risk-free despite practical safeguards, so meaningful changes to these rules will be dated on this screen.