How M3U8toMP4.org processes M3U8 URLs and local files
M3U8 URLs are used by client-side code to request manifests and media directly from the source host. Local files are read into browser memory for FFmpeg.wasm processing. The site does not provide a media upload API or cloud conversion queue.
The source host, CDN, browser, network provider, or hosting platform may still observe normal requests. This policy covers M3U8toMP4.org, not third-party media sources.
What M3U8toMP4.org stores during a media conversion
The application does not intentionally store playlist URLs, video segments, converted media, FFmpeg logs, or local file contents on its servers. Temporary object URLs and in-memory data disappear when the page is refreshed or closed.
The application does not require an account. Browser history may retain visited page URLs, but source URLs entered in tool fields are not placed in this site's route or query string.
How browser logs and essential hosting data may be handled
Infrastructure providers may create standard security and request logs for page assets, such as IP address, user agent, timestamp, and requested path. Those page requests do not include the media bytes processed locally by the tools.
If privacy-preserving aggregate analytics are introduced, this policy will be updated before they are enabled. The current product does not require advertising trackers to function.
How to contact M3U8toMP4.org about privacy
Send privacy questions to hello@m3u8tomp4.org. Do not include private playlist tokens, cookies, authorization headers, or media files in a support message.
Users can clear the current in-memory job by refreshing the page and can clear normal browser cache or history through their browser settings.