Voynix

Voynix Privacy Policy

Last updated: October 7, 2026

Voynix is a local-first music player for Mac and Android, developed by an individual (tekapo). This policy explains what data the Voynix apps handle. In short: the developer does not collect your data. There are no accounts, no analytics, no advertising and no developer-run servers.

Data stored on your devices

Voynix keeps your library (track information read from your music files, playlists, play history, favorites, settings, artist images and album covers) on your own devices: on the Mac in ~/Library/Application Support/com.tekapo.voynix, and on Android in the app's private storage. Your music files are read in place and are never uploaded anywhere. Deleting the app (and, on the Mac, that folder) removes this data.

Wi-Fi sync

When you pair a Mac and an Android device, the marked playlists, tracks, play history and favorites are copied directly between your two devices over your local network. The sync server runs on your Mac and requires pairing, and traffic is protected by a certificate that is pinned at pairing time. This data is not sent to the developer or to any third party.

Requests to third-party services

Some features look up information online. In these cases the text below is sent to the service, which also sees your IP address as with any internet request. No account or identifier from Voynix is attached.

ServiceUsed forWhat is sent
LRCLIBLyrics (Mac and Android), when you open the lyrics viewArtist, track title, album and duration of the track
DeezerArtist images and album covers (Mac)Artist name, or the search text you enter for album covers
iTunes Search API (Apple)Album covers (Mac)Artist name and album title, or the search text you enter

Those services' own privacy policies apply to the requests they receive. Voynix does not send your music files, your library as a whole or your play history to them.

Android permissions and the camera

Other information

Changes and contact

If this policy changes, the new version is published on this page with an updated date, and the history is kept in the repository. For questions, please open an issue on GitHub. To report a vulnerability, see SECURITY.md.