Privacy Policy — Last updated July 20, 2026
Binge is an Android app for browsing, discovering, and tracking movies and TV shows. This policy explains what information is collected when you use Binge, how it is used, and your choices regarding that information.
Your search queries, ratings, watchlist additions, favorites, and any custom lists you create are sent to The Movie Database (TMDB) so they can be saved to your TMDB account and synced across devices. Binge does not operate its own backend server — all account data lives with TMDB.
| Data | Purpose |
|---|---|
| TMDB session & account ID | Keeps you signed in between sessions |
| Recent searches (up to 8) | Powers the search history suggestions |
| Content & UI preferences | Your chosen start tab, adult-content filter, analytics opt-in |
| Cached media data | Speeds up browsing by avoiding repeated network calls; auto-expires |
| Connected server details (optional) | If you connect Binge to your own media-request server: your access key or login session, stored encrypted, and the server's address, stored as you entered it. Only present if you set one up |
All local data is stored in Android DataStore and a Room database on your device. Uninstalling the app removes all of it. Images you chose to save to your Pictures folder are yours and stay where you put them.
When the app crashes — and when it hits an error it recovers from, such as a failed network request — a report is sent to Google Firebase Crashlytics so the bug can be found and fixed. It contains the stack trace, your device model, Android version and app version, plus recent diagnostic log entries — which can include the name of the screen you were on and the address of a request that failed.
Reports are not linked to your TMDB account. Like usage analytics they carry a randomly generated identifier for your app installation, so repeated crashes on one device can be recognised as the same device — making them pseudonymous rather than anonymous. Unlike analytics, crash reporting is on by default; you can turn it off in Account → Preferences → Send crash reports.
Analytics is off until you turn it on. During setup Binge asks whether you want to share usage data (screens viewed, features used). Nothing is collected unless you actively agree — declining, or closing the app without choosing, leaves it off.
If you do agree, the same events are sent to two analytics providers. PostHog processes them on servers in the European Union. Google Firebase Analytics is operated by Google, which processes data on its own infrastructure outside the EEA under Google's privacy policy and terms.
These events record that something happened, not what it was. For example, a search is recorded as "a search was performed" — your search terms are never included. No event carries the titles you browse, your ratings, your lists, your TMDB username, or your TMDB account ID.
They are not fully anonymous, and we would rather say so than overstate it. Each provider attaches a randomly generated identifier for your app installation, and receives your device's IP address, so events from the same device can be grouped together. That identifier is not linked to your TMDB account and is discarded when you uninstall the app, but it does mean the data is pseudonymous rather than anonymous.
You can disable analytics at any time in Account → Preferences → Share analytics data. Turning it off stops all future collection by both providers. Previously collected data is governed by Google's privacy policy and PostHog's privacy policy.
Binge relies on the following third-party services. Each has its own privacy policy.
Binge requests only the permissions it needs:
Binge does not request access to your camera, microphone, location, contacts, or any other sensitive data.
Binge does not have its own account system. Signing in means authorising Binge to access your existing TMDB account via TMDB's OAuth flow. Your TMDB credentials are entered directly on the TMDB website — Binge never sees your password. The resulting session token is stored locally on your device and sent only to the TMDB API. You can revoke access at any time from your TMDB connected applications settings, or by signing out inside the app.
Connecting a media-request server is separate, and works differently: that server has its own accounts, so you may enter its username or email and password directly in Binge. Those are sent only to the server address you supplied — never to us, and never to any third party — and only the resulting access key or login session is kept on your device, encrypted.
Binge is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information through the app, please contact us and we will take steps to remove it.
If this policy changes materially, the updated version will be published at this URL with a revised "last updated" date. Continued use of the app after a change constitutes acceptance of the updated policy.
Questions about this policy? Email scottalancooper@gmail.com.