Understand YTSave's temporary media and bounded diagnostics
YTSave processes a submitted public URL, returned format metadata, selected output, and limited operational signals needed to run the job, prevent abuse, and investigate reliability. Prepared media expires under the configured cleanup window. Preferences and recent public links stay in browser storage where possible, while support messages and opaque continuation records use the private control database.
Last updated 26 August 2026. YTSave documents the information needed for analysis and delivery, together with the controls that remain in your browser.
1. What this policy covers
YTSave covers the downloader, evidence catalog, contact route and opaque continuation records described on this domain. Upstream media providers remain governed by their own notices.
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
YTSave uses request metadata for source detection, exact-format selection, temporary delivery and private continuation. Reliability analysis, fair-use limits and abuse prevention require a limited operational record.
4. Temporary media and retention
YTSave signs each delivery for a limited period and deletes prepared files under its cleanup window. Protected operational records last only for reliability and abuse needs, support messages remain until handled and continuation records are removable on request.
5. Service providers and upstream platforms
YTSave may communicate with the submitted media platform, hosting and database infrastructure, configured egress providers and optional advertising or donation services. Provider secrets and private routes are excluded from result links.
6. Cookies and local storage
YTSave uses a first-party visitor cookie for quotas and automated-abuse controls. Local storage may remember settings and recent public links, while Private Mode stops new entries and browser controls can remove them.
7. Your choices
Do not submit a URL or message to YTSave unless you want it processed. Private Mode limits recent local history, browser controls remove device data and support handles access, correction or deletion requests. Open the contact form.
8. Children, security and changes
YTSave is not directed to children under 13. Organizational and technical controls limit risk without erasing it, and a new date will identify every material change to this notice.