Understand temporary media and bounded diagnostics
YTSave uses limited operational identifiers to control abuse and jobs, keeps browser preferences locally where possible, and expires prepared media according to the configured retention window.
Last updated: 26 August 2026. This page explains what the downloader processes, why it is needed and which controls remain on your device.
1. What this policy covers
This policy covers the public YTSave website, downloader, source catalog, contact form and private continuation links. It does not control the privacy practices of the media platforms you choose to access.
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 YTSave. The local result disappears when you close or reload the tab unless you save it.
3. Why it is used
Data is used to provide requested downloads, route work safely, enforce fair-use limits, investigate reliability, answer support requests, measure aggregate product health and protect the service from automated abuse.
4. Temporary media and retention
Signed download links expire. Processed temporary files are deleted by the media-node cleanup policy. Operational records are retained only as long as needed for reliability and abuse prevention. Contact messages remain until handled under the operator’s support-retention process. Opaque continuation links are durable so another device can restore the result; contact support if you need one removed.
5. Service providers and upstream platforms
To fulfill a request, YTSave may communicate with the submitted media platform, hosting and database infrastructure, configured egress providers and optional advertising or donation services. Provider credentials and internal routes are never placed in public result links.
6. Cookies and local storage
A first-party visitor cookie supports quotas and abuse controls. Local storage can remember preferences and recent public links. Private Mode disables new local history entries. Browser controls can remove both at any time.
7. Your choices
Do not submit a link or contact message you do not want processed. Use Private Mode for one-off analyses, clear browser history from the result page, and use the contact form for access, correction or deletion questions.
8. Children, security and changes
YTSave is not directed to children under 13. Reasonable technical and organizational safeguards are used, but no internet service can promise absolute security. Material policy changes will be posted on this page with a new update date.