Subnext Player. Last updated 21 September 2026.
Subnext Player has no backend. There is no Subnext Player server, no account to create, and nowhere for us to send your data even if we wanted to. This policy is short because there is very little to describe.
Subnext Player plays media from sources you connect yourself: a Plex server, files on your device, a folder you choose, or a network share on your own network. It hosts no content and ships no catalogue.
Everything the app remembers is stored on your device only:
None of this is transmitted to us, because there is no us to transmit it to. Uninstalling the app removes it.
Only connections to the services you have configured, made directly from your device to them:
Those services have their own privacy policies and their own terms, and your relationship with them is yours rather than ours. We are not an intermediary, we do not proxy these connections, and we cannot see them.
The current version of Subnext Player sends no crash reports. Optional crash reporting may be added in a future version. If it is, it will be off unless you turn it on, it will be described here before that version ships, and it will never include your credentials, your server addresses or anything about what you watch.
Subnext Player is not directed at children and is not designed for use by them. It plays whatever you point it at and performs no content filtering of its own.
The app requests access to video on your device only so it can play it, and only the scoped media permission needed for that. It does not request broad filesystem access. Folder access is granted by you, per folder, through the system picker.
If this policy changes, the date above changes with it. This page is generated from the app's public source repository, so the full history of every revision is visible there.
Questions or concerns can be raised at the project's issue tracker.