← Back to M3U Playlist Inspector

Privacy

Privacy: How M3U Playlist Inspector Handles Your Files

M3U Playlist Inspector is a set of browser tools and a Python command-line script for checking, editing, merging, analysing and converting M3U and M3U8 playlist files. This page explains what happens to the files you open and what the site stores.

Your playlist stays in your browser

When you paste a playlist or choose a file, the page reads it with JavaScript in your own browser. The tools do not upload the contents to a server, and the page scripts contain no network requests of their own (no fetch, XMLHttpRequest, WebSocket or beacon calls). The tools also do not open the stream addresses inside your playlist, so they never contact the servers those addresses point to.

The source code is public, so you can read it or run the Python script on your own computer if you prefer not to use a web page at all.

What the site stores

What the hosting provider can see

The site is served by GitHub Pages. Like any web host, GitHub may log standard request information such as your IP address and the pages you request, under its own privacy statement. That applies to loading the page, not to the contents of playlists you open in it.

Keep your playlist private

Many playlists supplied by streaming services contain a username, password or access token inside each address. Treat such a file like a password. Do not paste it into public issues, forums or chats, and check a file before you share it.

Links to other sites

Some pages link to other websites, such as GitHub. Those sites have their own privacy practices, which this project does not control.

Questions

If something here looks wrong or out of date, open an issue on the GitHub project. To report a security problem, follow the security policy.

See also: all M3U tools and the M3U validation guide.