I build the player's home page, a small media player client for Android and Windows. the apk is 1.17 mb, the exe is 29.5 mb. the landing page claims "zero telemetry" and "no account". claims like that are cheap, so i tried to disprove my own claim.
setup: i ran the app behind mitmproxy on a test phone with a fresh profile. watched a full movie, browsed around, switched audio tracks, loaded subtitles, killed the app mid-playback, reinstalled it. one week of normal use, every tls handshake logged.
the full list of outbound requests:
- the video stream urls themselves. that is the product, nothing else rides on them
- one dns lookup per stream host
- nothing else
no analytics, no crash reporter, no ads sdk, no fingerprinting calls, not even a version check. you update by re-downloading from the 1.17 mb apk download.
the interesting part was what i had to delete to get there. an early build shipped with a crash reporter behind an "opt in" default. i told myself that was fine. it was not, and honestly the consent dialog was doing more work than the reporter ever did. the fix was not a toggle, it was removing the dependency. today the android manifest asks for exactly three things: INTERNET, ACCESS_NETWORK_STATE, POST_NOTIFICATIONS. no READ_PHONE_STATE, no ad id, storage is scoped through the system picker.
the windows build is the same story. it opens the stream url and a local file dialog. that is the whole network surface. get it from the pc installer.
if you do not trust me: install the apk, block its network except the stream host, and watch it still work. or just decompile the apk and read the manifest yourself.
full disclosure: i am the developer of RKMovies.
Top comments (0)