Privacy Policy
Last updated: August 22, 2026
Mac Classic Player has no analytics, no crash reporting, no accounts, and no server of mine behind it. There isn't much to tell — but “we don't collect anything” would be sloppy, because the app does talk to two places. Here is all of it.
Your files stay on your Mac
Whatever you open is read from disk and played locally. Large files are served through a small HTTP server the app runs on your own machine, bound to 127.0.0.1 so nothing outside your Mac can reach it. No file, filename, or path is ever uploaded.
Cover artwork is looked up at Apple
When an audio file carries artist or album tags, the app sends those two pieces of text to Apple's public iTunes Search API to find cover art, along with a country code taken from your system language. Nothing else goes with it — not the filename, not the path, not any identifier for you or your Mac. This happens automatically and there is currently no switch to turn it off. The request only fires for files that actually have artist or album tags, and video files without those tags never trigger it. Apple's handling of the request is covered by their own privacy policy.
Update checks go to GitHub
The app checks for new versions by fetching a small file from its GitHub Releases page. GitHub sees the request the way it sees any download, including your IP address, and that is covered by GitHub's privacy policy. Nothing about your library is included.
What is stored on your Mac
The list of recently opened files and the window position are written to a folder inside your own Library directory. They never leave the machine, and deleting the app's support folder clears them.
You can check all of this
The app is open source under the MIT license, so none of the above has to be taken on trust. Read the source or open an issue there if something looks wrong.
Changes
If the app ever starts doing something new with data, this page gets updated before that version ships.