Legal

Privacy policy

NoFlex is software you run yourself. Your library, your account and what you watch live on a server you or someone you know controls, never with us.

Last updated 11 November 2026

The short version

  • We don't collect anything through the apps. No analytics, no crash reporting, no advertising, no tracking, and no account with us.
  • Your data lives on your NoFlex server. Whoever runs that server (its operator) holds your account and watch history and is responsible for them. If you run your own server, that's you.
  • The apps talk only to the servers you connect them to. Media never passes through us.
  • By default, a server contacts three outside services to identify what's in its library: TMDB, TheTVDB and MusicBrainz. Others are only contacted if the operator sets them up.

What this covers

This policy covers the NoFlex apps for phones, tablets, computers and TVs, the web client built into the server, the NoFlex server software, and this website, noflex.dev. NoFlex is made by Christopher Tam (“we”, “us”), who maintains the project.

Because NoFlex is self-hosted, there are two parties in it: us, who make the software, and the operator of each server, who runs it. We have no access to anyone's server and can't see, change or delete what's on it.

What we collect

Through the apps and the server

Nothing. The apps and the server contain no analytics, telemetry, crash reporting, advertising or tracking code, and don't check in with us for updates or anything else.

On this website

This site sets no cookies and runs no analytics. It's hosted by Cloudflare, which, like any web host, processes your IP address and browser details to deliver pages and protect the site from abuse, under Cloudflare's privacy policy. We don't use that data to identify you.

When you contact us

We're reached through GitHub. Issues, discussions and pull requests there are public, and governed by GitHub's privacy statement. You can edit or delete what you post.

Your NoFlex server

To work, a server keeps the following about each person with an account. It's stored in the server's database and is visible to its administrators.

WhatWhy
Username, display name, role, and an optional profile pictureTo sign you in and show who's watching. Pictures are re-encoded so only the pixels are kept.
Your password and PIN, as one-way hashesTo check them. Nobody, administrators included, can read them back.
Watch history, positions, ratings, favorites and playlistsTo resume where you left off, keep track of what you've seen, and recommend what to watch next.
Your devices and sessions: device name, app and version, what the device can play, IP address, and when it was last usedTo keep you signed in, choose a version each device can play, and let you see and sign out your devices.
An activity log of sign-ins and administrative actions, which can include IP addressesSo administrators can see what happened on their server.
If you use them: the email of an account you sign in with through your operator's single sign-on, tokens for services you link (such as Trakt), and keys for friends' servers you linkTo sign you in that way, and to act for you with those services.

Operators also keep database backups and server logs, which hold copies of this data for as long as their settings say (a week of backups by default).

On your device

  • Apps for phones, tablets and computers keep your sign-in tokens in the system's secure storage (Keychain on Apple devices), plus the server's address, a random identifier for the device, your settings, anything you download for offline viewing, and a cache of artwork. Downloads are excluded from iCloud backups.
  • The web client keeps your sign-in for the browser tab only (session storage), and remembers a random device identifier and a few preferences such as volume. It sets no cookies.
  • The TV app keeps your sign-in, the server's address and your settings in the TV's app storage.

The apps send your device's name (for example, the model of your phone or your computer's name) to your server, so you can tell your devices apart in your account, where you can also sign any of them out.

Services your server may contact

On by default

To identify titles and fetch artwork, a server sends what it read from your file and folder names (titles, years, episode numbers) and the IDs those services use, along with the server's IP address, to:

No account information, watch history or media is sent to them. Your apps load artwork from your server, not from these services.

Only if the operator sets them up

  • Single sign-on (OpenID Connect): your sign-in goes through the provider your operator chose.
  • Trakt: if you link your Trakt account, what you watch and how far you got is sent to Trakt.
  • OpenSubtitles: if the operator adds an OpenSubtitles API key and you search for subtitles, the server sends OpenSubtitles.com the title's name, year and IDs, the languages you asked for, and a fingerprint of the file (its size and a hash of its first and last 64 KB), along with the server's IP address. Nothing about you or your account is sent. OpenSubtitles' privacy policy applies.
  • OMDb: if the operator adds an OMDb API key, the server sends OMDb each title's IMDb ID with that key, along with the server's IP address, to fetch its IMDb, Rotten Tomatoes and Metacritic ratings. Nothing about you or your account is sent. OMDb's terms apply.
  • Webhooks: events such as what's playing, including usernames and titles, go to the address the operator configured.
  • A remote embedding service: NoFlex understands searches with a model that runs on the server itself. If an operator points it at an outside service instead, synopses and the searches people type are sent there.
  • Live TV: channel lists, programme guides and channel logos are fetched from the sources the operator adds.
  • Google Cast: if the operator turns it on, the web client loads Google's Cast software from Google when you use it in Chrome, and a Cast device you play to receives the stream's address, the title and its artwork. NoFlex's receiver also receives a limited playback token to report your place directly to your server while you watch, even after the sender disconnects; it does not receive your sign-in or refresh token. Google's privacy policy applies.

Friends' servers

If you link a friend's server, your app connects to it directly and signs in with a key it issued you. To keep what you've watched in step between them, your app shares your watch history for titles both servers have (which title, whether you finished it, and how far you got) with that server. You can turn this off for each linked server. That server's operator then holds that data under their own practices.

App stores and platforms

When you download NoFlex from an app store, the store (such as Apple, Google, Amazon, Samsung, LG or Microsoft) handles the download under its own privacy policy. Stores may share aggregate statistics with us, such as download counts, and crash reports if you've agreed to share them with developers in your device's settings. Your device's operating system may also have its own services, such as the system web view on Android TV, that work under the platform's policies.

App permissions

  • Network and local network: to reach your server, which is often on your home network. On iPhone, iPad and Mac, the system asks before the app can see devices on your local network.
  • Notifications (Android): to show the progress of downloads. Nothing is pushed from a server.
  • Background activity: to finish downloads and keep Smart Downloads up to date while the app isn't open.
  • Picture-in-picture: to keep playing in a small window.
  • Photos you pick: only the picture you choose as your profile picture, which is uploaded to your server.

Deleting your data

  • Your account: delete it yourself from your account settings in the app or the web client. How to delete your account has the steps. This removes your account and everything tied to it from the server, though the operator's backups and logs keep copies until they expire.
  • On your device: signing out removes that account's sign-in and downloads from the app. Uninstalling the app removes everything it stored.

Children

NoFlex isn't directed at children, and we collect no data from anyone, children included. Operators can give younger viewers their own accounts with parental controls: allowed ratings, libraries, and a PIN on the profile.

Your rights

Depending on where you live, laws such as the GDPR or the CCPA give you rights to access, correct, delete or move your personal data. For data on a NoFlex server, the server's operator is the one who can act on them, and NoFlex gives them the tools to: you can see your own sessions and devices, change your details, and delete your account yourself. We hold no personal data from the apps or servers to act on, and we don't sell or share personal data.

Changes

We'll post any change to this policy on this page with a new date, and note significant changes in the release notes.

Contact

Christopher Tam maintains NoFlex. Ask about this policy in GitHub Discussions, and report a security issue privately through GitHub's security advisories.