Apollo Videos · Effective 6 September 2026
Apollo Videos does not collect your data. There is no account to create, no analytics, no advertising, and no tracking. The developer operates exactly one small service, and it exists to hold things the app must not carry rather than to collect anything about you. It does two jobs. It tells the app where the videos are, which is how access is limited to Apollo members: the app itself knows no addresses, so a non-member is not shown a locked door, there is simply nothing to open. And when you switch captions on, it issues a transcription key that expires in a minute. It is sent no audio, and it keeps no records of you.
The app is gated by the Apollo Discord server, and its sole purpose is playing media files.
Apollo Videos is developed by Gabor Berenyi. Its complete source code is public at github.com/ber4444/kmp-videos, so every statement on this page can be checked against the code that makes it true, rather than taken on trust.
The app is a media player, so it makes network requests to play video and to check that you are allowed in. Those requests go directly from your device to the services below — never through the developer. Each one necessarily sees your IP address and the timing of your requests, as is the case for any website you visit.
| Service | What is sent | When |
|---|---|---|
| The streaming server | Requests for the video and audio you chose to play, plus the playlists that describe them. | While browsing the feed or playing a video. |
| Discord discord.com |
The standard OAuth2 sign-in exchange you start by tapping Connect to Discord, which returns your display name. The membership question is asked by the developer’s service rather than by the app — see the row below — so it is that service which reads your account id and your list of servers, using the sign-in you granted. | When you sign in, and once at each launch to re-check membership. |
| GitHub gist.githubusercontent.com |
A request for a text file listing additional videos in the feed, at an address the developer’s service supplies once you are signed in. No information about you is included. | Once per launch, and when you pull to refresh. |
| The feed and caption service operated by the developer |
Your Discord sign-in, so the service can ask Discord who you are and whether you are on the Apollo server. On that basis it returns the addresses the feed is built from, and — when captions are on — a transcription key good for one connection within a minute. It is told nothing about which videos you open. Its yes-or-no answer is cached in memory for five minutes under a hash of your token; your requests are also counted per network address, in memory, so that no one caller can exhaust the service. | At launch and on each refresh of the feed, and additionally while captions are on. |
| Soniox stt-rt.soniox.com |
The audio track of the video you are watching, so it can be transcribed into captions. This is media from the streaming server, not you — the app has no microphone permission and cannot record you. | Only while you have live captions switched on. |
Access to the feed is limited to members of the Apollo Discord server, so the app has to ask
Discord who you are. It uses the standard authorization-code flow with PKCE, and requests the two
narrowest scopes that answer the question: identify and guilds.
The app stores a few things locally, in its own private storage. None of it is transmitted anywhere.
SharedPreferences
on Android, the Keychain on iOS, localStorage on the web.Signing out erases the stored session. Uninstalling the app, or clearing its data in system settings, erases everything above. On the web build, clearing site data does the same.
One iOS detail, stated because it is not obvious: iOS deliberately keeps Keychain entries when an app is deleted, so the saved sign-in survives an uninstall until something clears it. The app clears it itself the first time it runs after being installed, so a reinstall never resumes someone else’s session — but between deleting the app and installing it again, the entry is still on the device.
The Android app requests only what the media player needs to work:
In the Google Play Data Safety form, this app declares No data collected and No data shared with third parties.
That declaration reflects the behaviour described above. The app builds no profile of you, keeps no record of you anywhere, and stores what little it holds on your own device. What it does send the developer’s service is the Discord sign-in you already granted, and only so that the service can put one question to Discord on your behalf. The answer is used to reply to that request and held in memory for a few minutes; it is never written down, never joined to anything else, and never used to work out what you watched.
Apollo Videos is not directed at children, and is not designed or marketed for them. It knowingly collects nothing from anyone, of any age.
The services the app contacts have their own privacy policies, which govern what they do with requests they receive:
If the app's behaviour changes in a way that affects this policy, this page is updated and the effective date at the top changes with it. Because the app is open source, the change that prompted it is visible in the repository's history.
Questions about this policy, or about how the app behaves, can be raised at github.com/ber4444/kmp-videos/issues.