Security: what goes where
Last updated: November 2026
This page says, for each part of CodoPlayer, what stays in your browser, what our server receives and what it keeps. It describes how the code works today and makes no claim of an audit, a certificate or a rating. The full list of what we store is in the privacy policy.
Where the video goes
In the web player the video is requested by your browser from your provider's server, and our server is not in that path. The same holds for the apps. We do not host, relay, convert or re-encode your streams. What our server does receive is described below.
What stays in your browser
- Player data: your session, settings, favourites, resume positions, a random visitor number and a cache of playlist data are kept in your browser's local storage on your device. Clearing this site's data in your browser removes them (and gives you a new visitor number).
- A playlist file you upload in the web player stays in your browser.
- The browser-only tools (Browser Playback Test, Bandwidth Calculator, M3U Creator, Playlist Compare, Subtitle Converter, XMLTV Viewer and M3U8 Player) read the file or text you give them inside your browser. They send nothing to our server except the page and its own script files. The M3U8 Player contacts the stream address you type directly from your browser.
What our server receives
- The web player sends us, with or without an account: a visitor number, device details as the browser reports them, your IP address and country, what you watch and search for, and problem reports. It also sends the playlists you open: the provider's server address with your username and password, or the playlist link, kept with your visitor number so we can open it ourselves when it does not work for you. Usernames and passwords are removed from problem reports before they are sent. Exact lists and retention are in the privacy policy. So the credentials of a playlist you open in the web player do reach our server.
- The server-side playlist tools (checker, validator, editor and the others that take a link, a login or an uploaded file) send what you give them to our server, which downloads and reads it. We keep a record of each use and a copy of the playlist or guide for up to a year; the files a tool makes are deleted after 4 hours. On most of these tools a playlist or guide file you choose is read by your browser instead and is not uploaded: the page says which applies, next to the file button, before you choose.
- Accounts: name, email and a hashed password. Forms that need it are protected by a Cloudflare check, and your browser talks to our site over HTTPS.
- The free player host (free.web.codoplayer.com) is served over plain HTTP on purpose, so that it can open HTTP streams. Anything you type on that host crosses the network unencrypted; the HTTP help page explains why.
- The CodoPlayer extension sends an install number, version and browser details, and optional statistics that never include a video's link. See the extension section.
Cookies and third parties
The player uses local storage, and a short-lived cookie may route you between the free and secure player hosts. Measurement and advertising tags run on our pages when they are switched on and handle what they collect under their own policies. The web player may ask ipapi.is, a separate service, about your IP address.
Deleting your data
Clear the site's data in your browser to remove what is stored there. To delete an account or the records held about you on our server, ask through the feedback form; the extension has an Erase my data button. Details are in the privacy policy.
Reporting a security problem
Use the feedback form and say it is a security report. Please do not send credentials or other people's data. The same contact is listed in security.txt.