Privacy Policy

Effective date: [EFFECTIVE DATE] · Applies to Media Player Windows version 0.1.0 and later

Note for the publisher — delete this box before launch.

Everything this page says about the application was checked against the version 0.1.0 source: it contains no code that opens a network connection. Before publishing:

Fill in every [BRACKETED] value.
Section 7 covers this website. It is written for a deployment with no analytics. If you later add analytics, a newsletter, a contact form or Vercel Web Analytics, this page must be updated first — those change the answer.
Have it reviewed for GDPR, UK GDPR, CCPA/CPRA and any other regime you fall under. “We collect nothing” is a strong position but it still has to be stated in the form each regime expects.
Re-check it against the build on every release. This document is only as true as the code.

The short version

The application collects nothing and sends nothing. It has no account system, no telemetry, no analytics, no crash reporting and no update check. It contains no code that opens a network connection on its own.

Everything it remembers — your settings, your library index, what you watched and where you stopped — is written to files in your own user profile and never leaves your computer. We have no server holding your data, because there is no data being sent to one.

1. Who we are

The Media Player Windows application and the website at mediaplayerwindows.com are published by [LEGAL ENTITY NAME], [REGISTERED ADDRESS]. For data-protection purposes we are the controller for any personal data this policy describes — which, for the application, is none.

2. What the application collects

Nothing. Specifically, the application does not:

ask you to create an account or sign in;
send usage statistics, feature-usage counters, session lengths or any other telemetry;
send crash reports or stack traces;
contact a server to check for updates or to validate a licence;
assign you an identifier, advertising ID or device fingerprint;
read your address book, location, camera or microphone;
include any advertising, tracking or analytics SDK;
transmit the names, contents or metadata of any file you open.

This is verifiable rather than merely promised: the application ships as readable Python source, and no module in it imports an HTTP or socket client. The only networking code in the product is a URL parser, used to recognise when the text you typed is a stream address rather than a file path.

3. What it stores on your computer

The application keeps state so it can be useful across sessions. All of it is local. None of it is transmitted.

File	What is in it
`settings.json`	Your preferences: theme, accent, volume, playback speed, chosen engine, subtitle styling, window position.
`library.db`	A SQLite index of the folders you asked it to scan: file paths, titles, durations, and artist/album/genre/year tags read from the files. Also your watch history — file path, last position, how many times played, when — and any bookmarks you set.
`session.json`	The playlist that was open when you last closed the window, so it can be restored.
`logs\player.log`	A diagnostic log: which engine started, errors, and the paths of files that were opened. Written so that a problem can be diagnosed on your own machine. It is never sent anywhere.
`cache\thumbnails\`	Thumbnail images generated from your own media for the library view.

These live in one of two places, depending on how you run it:

Installed: %LOCALAPPDATA%\MediaPlayerWindows
Portable (a portable.txt file next to the application): a data folder beside the application itself, so a USB stick leaves nothing on the host machine.

Screenshots you take are saved to Pictures\Media Player Windows, or beside the application in portable mode.

4. When network traffic happens

Only when you cause it. If you open a network stream — by pasting an address, or opening a playlist that contains one — the player connects to that address in order to play it. That connection goes to the server you named. It does not pass through us, and we are not told about it.

Whoever operates that server can see what any server sees: your IP address, the time, and what you requested. That is between you and them, under their privacy policy, not ours.

Nothing else in the application initiates a connection. If you run it on a machine with no network at all, every feature except stream playback behaves identically.

5. Deleting your data

Because it is all local, you are in complete control and do not need to ask us for anything.

Watch history: Settings → Advanced → Clear watch history.
Everything at once: delete the data folder listed in section 3. Settings → Advanced → Open the data folder takes you straight there.
On uninstall: the uninstaller asks whether to remove your settings, library and history. It defaults to keeping them, so you have to choose deletion deliberately — and it will not delete them silently during an unattended uninstall.

6. Children

The application is a general-purpose media player and is not directed at children. Because it collects no data at all, it collects no data from children.

7. This website

This site is a set of static pages. It sets no cookies, has no login, no contact form and no analytics or tracking scripts, so there is no consent banner to click.

Hosting

It is hosted by Vercel Inc., which processes standard server request logs (IP address, timestamp, requested URL, user agent) in order to serve pages and protect the service. Vercel acts as our processor; see Vercel's own privacy documentation for its retention practices.

Fonts

The pages load the Outfit and Work Sans typefaces from Google Fonts. Your browser therefore makes a request to fonts.googleapis.com and fonts.gstatic.com, which discloses your IP address to Google.

[PUBLISHER: if you would rather not disclose visitors' IP addresses to Google — the safer reading of GDPR — self-host the two font files and delete this subsection. The change is one @import line in styles.css.]

Downloads

The download button points at GitHub. Following it takes you to GitHub, Inc., under its own privacy policy.

8. Third-party components

The application bundles a Python runtime, the wxPython interface toolkit, Pillow, mutagen and Send2Trash. These are libraries running on your computer; none of them is a service and none of them reports to anyone.

If you add the optional mpv or VLC playback libraries yourself, they run locally too. They are not ours and are not included in the installer, and their own terms apply to them.

9. Your rights

Data-protection law gives you rights over personal data an organisation holds about you — access, correction, erasure, portability, objection, and the right to complain to a supervisory authority.

For the application, we hold nothing to which those rights could apply. There is no account, no profile and no server-side record. Your data is in your own file system, under your own control.

For the website, the only personal data involved is what our host processes in its request logs. If you want to exercise a right in respect of that, or you are unsure, write to us at the address in section 11 and we will help.

[PUBLISHER: name the competent supervisory authority for your establishment here, and add the CCPA/CPRA-specific disclosures if you offer the software to California residents — even a “we sell no personal information” statement has to be made explicitly.]

10. Changes to this policy

If the application ever starts doing something this page says it does not — an update check, an opt-in diagnostic report, anything at all — this page will be changed before that version is released, and the effective date above will change with it. The current version is always the one on this page.

11. Contact

Privacy questions: [CONTACT EMAIL ADDRESS].