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. This local page is different: the selected file is read with the browser File API and written into temporary WebAssembly memory, with no media-upload endpoint.