Privacy
INFUSION collects nothing and has no server to collect it. There is no account, no analytics, no telemetry and no advertising identifier.
The short version
- There is no INFUSION account, no sign-in and no INFUSION server. Nothing about you is sent to the project that makes the app.
- Profiles, watch state, progress, settings, your configured servers and your add-ons are stored on your device.
- The app talks only to services you configure — your Jellyfin server, the add-ons you install, the tracking service you connect — plus the metadata services it uses to describe a title, and one update check.
- Android backup is switched off for the app, so its data is not copied into a cloud backup.
- There is no analytics SDK, no crash reporting, no tracking pixel and no advertising library.
What is stored on your device
- Your profiles and each profile's watch state, progress and playback position.
- Your settings, including which add-ons are installed, enabled and in which order.
- The addresses of the servers and add-ons you configured.
- Credentials for those services — a Jellyfin access token, an add-on's query material, a tracking token, an OMDb key. They are kept in the Android Keystore-backed secret store, not in plain files, and they are deleted when you disconnect that service, clear the value, or uninstall the app.
INFUSION does not synchronise any of this to the project. There is no cloud profile, no account recovery and no way for the project to read it.
What leaves your device, and where it goes
Every destination below is either one you configured yourself or one of the two metadata services that describe a title. Nothing is sent to a destination that is not in this table.
| Destination | What is sent, and when |
|---|---|
| Your Jellyfin server the address you enter |
Your user name and password when you connect, exchanged for an access token; then the requests needed to browse your libraries and play from them. Only while that server is connected. |
| The add-ons you install the addresses you add |
The requests the add-on protocol needs for catalogs, metadata, streams and subtitles. Only for add-ons you installed and left enabled. An add-on's address may itself contain a private token; INFUSION stores that part in the Keystore-backed secret store and never prints it in logs or diagnostics. |
| TMDB api.themoviedb.org, image.tmdb.org |
Metadata and artwork requests for the titles you browse or open. |
| OMDb omdbapi.com |
Ratings lookups for a title, carrying the API key you provided. Only if you have entered an OMDb key; without one, OMDb is never contacted. |
| Simkl, Trakt or MDBList only the ones you connect |
The authorisation you granted through that service's own device-code page, and the scrobbles of what you watch. Disconnecting the service stops it. |
| TheIntroDB and IntroDB.app api.theintrodb.org, api.introdb.app |
The season, episode and title identifiers needed to look up intro, recap and credits markers for an episode you play. |
| GitHub api.github.com |
The release-list request when the app starts, to see whether a newer public alpha has been published: one request per start, plus at most one confirmation read when it finds one. It carries no account, no library and no history — it is the same request any anonymous visitor makes. |
Those services see the requests you make to them, exactly as they would if you used them in a browser. Their own privacy terms apply to what they do with those requests; INFUSION has no control over that and no agreement with them about you.
What INFUSION does not do
- It does not create or require an account, and it has no user database anywhere.
- It does not host, index or supply media, and it has no catalog of its own.
- It does not include analytics, crash reporting, attribution tracking or advertising libraries, and it does not read the Android advertising identifier.
- It does not send your library, your watch history or your credentials anywhere except the service they belong to.
- It does not phone home on a schedule. Nothing contacts a server while you are not using the app: the update check runs once when the app starts, and playback progress is reported only to the server you are playing from, while it plays.
Android backup is off
Both the TV app and the mobile app declare android:allowBackup="false". Android's
cloud backup therefore does not copy the app's data, and neither does a device-to-device migration
of app data.
Removing your data
- Disconnect a service and the credential INFUSION held for it is deleted from the secret store.
- Delete a profile and that profile's watch state and settings go with it.
- Uninstall the app and everything it stored on the device goes with it. There is no copy on a server to ask us to delete, because there is no server.
- Data on a Jellyfin server you connected belongs to that server, not to INFUSION. Deleting it there is a Jellyfin operation.
This website
This site is a set of static files. It sets no cookies, runs no JavaScript, loads nothing from a third party — no CDN, no web font, no analytics, no tracking pixel — and its only outbound links go to the public releases repository on GitHub. It is served by Cloudflare Pages, which, like any web host, sees the requests needed to deliver a page.