Privacy policy
Last updated: November 5, 2026
Reelhost is an app for Windows and Mac, with a Docker edition for NAS boxes and Linux servers, made by Wizzered Inc. ("we", "us"), 5900 Balcones Drive, Suite #32859, Austin, TX 78731, USA. It runs in the background on the computer that runs Jellyfin, you use it through a dashboard in your web browser, and it changes your Jellyfin server's settings. This policy explains what personal information the app, this website, your account and our support collect, why, who receives it, and your rights. Wizzered Inc. is the controller of that information.
The short version
- Your media never leaves your computer. Not your videos or music, artwork, watch history or passwords. Jellyfin accounts stay on your server too, except the name and id of the profile linked to someone you invite (see People you invite). File names leave your computer only if you use the library fixer (see Reelhost AI below).
- Reelhost never stores your files; it only carries them. Nothing you send or share through Signal (files, photos, videos) is saved on a server we run. See Sharing and sending files for exactly what your own server holds.
- Your video never passes through our servers. When you watch away from home, it streams straight from your home to your device.
- The app sends only what its features need: license activation (or your email address for a free trial, if you start one), update checks and, if you use them, updates for your watchhome.app address (on every plan, Free included), your Free TV channel choice and, with server alerts on, a heartbeat every 15 minutes.
- This website counts visits without cookies and without keeping your IP address. Advertising cookies and pixels from Reddit, Meta and Google load only if you choose "That's fine", and never if your browser sends Global Privacy Control. Change your choice any time with Cookie settings. Your account page sets one cookie, only to keep you signed in.
What the app sends
| When | What is sent | To whom |
|---|---|---|
| You activate your license, and afterwards when Reelhost starts and once a day to confirm it's still valid | Your license key, a random ID for this computer, the computer's name, its operating system and edition (Windows, Mac or Docker) and the Reelhost version (so you can tell your computers apart in your account when moving a license) | Our license server, api.reelhost.app |
| The app checks for updates | The app's current version | Our update service, api.reelhost.app |
| The app checks for a newer Jellyfin version | A request to GitHub's public list of Jellyfin releases. Nothing about you or your server | GitHub |
| Only if you use Free TV: when Jellyfin refreshes its channel list and guide (it does this on its own schedule) | Which channels you picked and, if known, your country, so only channels that play there are listed | Our Free TV service, api.reelhost.app. Jellyfin then plays each stream straight from the broadcaster, who sees your IP address like any website you visit |
| Only if you add channels of your own: at most once a day, by the hourly task or when you check or add a channel | Nothing about you or your channels. The app downloads Stream guard's public list of paid IPTV services and checks each address you add against it on your computer | Our Stream guard list, api.reelhost.app |
| Only for the Docker edition: when the computer that runs Docker downloads (pulls) Reelhost's image | The id of the license or free Docker key it signed in with, its IP address and network, the time, and what was pulled | Our image registry, registry.reelhost.app. We use these records to deliver the image and its updates, and to spot keys shared between many places |
| Only if you turn on server alerts: when you turn them on, then every 15 minutes while they're on | A heartbeat: whether Jellyfin is answering, the lowest free space (percent and amount) across the drives Jellyfin uses, and your computer's time zone offset, for quiet hours. Never the names of people, titles or folders. Turning alerts on sends your license key once and gets back a token that proves the alerts are yours | Our alert service, api.reelhost.app, which emails you (at your license's email, or another address you confirm) when the heartbeat stops, Jellyfin stops answering or a drive runs low, through our email provider, Resend |
| Only if someone at home uses Remind in Signal while server alerts are on | The words of the reminder: who asked and which part of the server (for example "Ava asked you to look at live tv") and how Reelhost sees it, with the alerts token | Our alert service, api.reelhost.app, which emails it to where your alerts go, at most 5 a day |
| Only if you turn on "Show this server in my Reelhost account": when you turn it on, then when it changes or once a day | Your Jellyfin server's name and id, and its addresses on your home network (private addresses only, never your public IP). Turning it on sends your license key once and gets back a token. Never people, titles, keys or passwords | Our name service, api.reelhost.app, which lists the server to Signal apps signed in with your Reelhost account. Turning it off, removing the computer from your license or removing Reelhost deletes it |
| Voice chat in Watch together: we are not involved | Nothing. Calls go directly between the devices in them, or, with Calls away from home on, through your own Reelhost computer: calls away from home pass through your own Reelhost computer; nothing goes through Reelhost's servers. We never see who calls whom, when, or from which address | Nobody at Reelhost. With Calls away from home on, your own computer passes the call's encrypted packets on (it can't hear or see them) and keeps counts only. If you add a relay server of your own (Watch together > Your own relay server), its owner sees the addresses of the people who connect through it, and its login stays on your computer, never sent to us. If you also tick Cloudflare's STUN, Cloudflare sees the public address of each device that asks, and nothing else: STUN carries no call |
| Only if you use a yourname.watchhome.app address: when you set it up, then every hour while it's on | Your chosen name, your home's public IP address (IPv4 and, if you have one, IPv6), your computer's name, and what proves the address is yours: with a license, a token; on Free, an ID for this installation (made on your computer as a one-way code of its own system ID, or at random). Our server keeps only a one-way code of that ID, so it can tell your installation apart without a license. To allow at most 3 new free names from one internet connection a day, it also keeps a one-way code of your IP address for 24 hours. When you pick a name, the suggestions come from your license's email address, which we already hold; nothing new is sent for them | Our name service, api.reelhost.app, which updates the address's DNS record at our DNS provider, Cloudflare. If you also let your phone control Reelhost from anywhere, a second record, app.yourname.watchhome.app, points at the same address while that's on |
Like any internet request, each of these also reveals your IP address to the service that receives it.
Anonymous usage (only if you say yes)
After your first check-up, or on the License screen, the app asks "Help us improve Reelhost?". It's off until you choose Share anonymous usage. If you choose No thanks, nothing is counted and nothing is sent, and you aren't asked again.
If you say yes, at most once a day the app sends our API (api.reelhost.app) only:
- A random install ID made on your computer when you said yes. It isn't your license key, your email or anything from your hardware, and it isn't linked to them.
- Your plan (free, Core, Complete or Yearly), your platform (Windows, Mac or Docker), the Reelhost version and the Jellyfin version (major and minor only, such as 10.10).
- Per week, counts of which Reelhost screens you opened and which features you used, from a fixed list (for example "ran the check-up: 3", "applied a theme: 1"), and how far you got in setup steps such as "Set up Jellyfin for me" or a web address's certificate.
It never sends titles, file or folder names, people's names, email or web addresses, anything you type, your license key, or anything about what you watch. Our API doesn't store your IP address for these reports, and anything not on the fixed list is refused.
We look at these counts only added up across everyone who shares them, to see which features are used and where setup gets stuck. They're kept for 13 months, then deleted. The legal basis is your consent.
To turn it off, untick "Share which features you use" on the License screen. Sending stops at once and the counts waiting on your computer are deleted; turning it on again later starts with a new install ID.
Problem reports (only if you turn them on)
Reelhost keeps a short log of what went wrong on your computer, such as "the TV guide download timed out", so it can fix common problems by itself and tell you when it can't. The log stays on your computer unless you turn on Send problem reports (Add-ons and advanced → Self-healing). It's off until you do.
If you turn it on, at most once a day the app sends our API (api.reelhost.app): a random install ID made for problem reports (not your license key, your email or anything from your hardware, and not the one used for anonymous usage), your plan, platform and operating system version, the Reelhost and Jellyfin versions, and for each problem which part of Reelhost it was in, what kind of error it was, the step that failed, how many times it happened and whether Reelhost fixed it by itself.
Error messages are cleaned on your computer first: names, titles, file and folder names, web, email and IP addresses, keys and numbers are taken out. When you mark an answer from Ask Reelhost as "Didn't help", and only if you choose to send it, your question (with the same details taken out) and which help topics the answer used are sent too. Our API doesn't store your IP address for these reports.
We keep problem reports for 180 days and "Didn't help" questions for 90 days, then delete them. The legal basis is your consent.
To stop, turn Send problem reports off: sending stops at once and what's waiting on your computer is deleted.
Services the app talks to on your behalf
Some features connect your computer directly to another company's service. We don't receive this data.
- HTTPS certificates (only with a public address): your computer requests a certificate for your address from Let's Encrypt. Certificates are published in public Certificate Transparency logs, so your address name becomes publicly visible. Your IP address and media are not in it.
- Antenna TV guide (only if you set it up): your computer downloads guide data from SiliconDust, the maker of HDHomeRun, using the code your tuner provides for that purpose.
- Country list (only if you turn on the country allow-list for your web address): once a month your computer downloads DB-IP's free IP to Country Lite list from db-ip.com, like any download. Nothing about you, your visitors or your server is sent; visitors' addresses are only looked up on your computer.
- Tailscale (only if you choose private watching): the Tailscale app and your Tailscale account are governed by Tailscale's own privacy policy.
- Weather on an idle TV (only if an admin turns it on): your server asks MET Norway's public forecast service for the weather, directly. What it sends is the latitude and longitude of the place the admin picked, rounded to about a kilometre, and Reelhost's name and support address, which the service requires. We don't receive the place or the forecast, and nothing goes through our servers.
- Software from other publishers (only when you ask Reelhost to set it up): your computer downloads Jellyfin, Caddy, ffmpeg, the Whisper and Kokoro voice models, ONNX Runtime, LiveKit and similar programs directly from their publishers' official download sites, such as repo.jellyfin.org and GitHub. We don't receive this data, and those publishers' terms and privacy policies apply to the download.
- Similar music (on unless the owner turns off "Use the internet to find similar music"): to choose what plays next in Signal's radio and the DJ, your server asks MusicBrainz (musicbrainz.org) and ListenBrainz (listenbrainz.org), free public music databases run by the MetaBrainz Foundation, which artists are like an artist and what styles it plays. It sends only the artist's name or its MusicBrainz id, never who is listening, what anyone plays or any account, user or device identifier, at most one request a second, identifying itself as "Reelhost" with our website address as MusicBrainz asks; like any internet request, it shows those services your server's IP address. Answers are kept on your server for up to a month. Songs only ever come from your own library. The DJ's optional facts about artists ask MusicBrainz the same way, with the artist's name only.
- Your router (only with a public address): the app asks your router, on your home network, to open the port Jellyfin needs (UPnP).
- Lookups for Signal (only when someone uses Signal's internet radio, its suggestions from outside your library or karaoke lyrics your library doesn't have): your server asks the public Radio Browser service (radio-browser.info) for station lists, Apple's iTunes Search and TVmaze for titles and pictures, and LRCLIB (lrclib.net) for lyrics, so phones, TVs and browsers don't contact those services themselves. It sends only the search words, genre, country or station asked about, and for lyrics only the song and artist asked about, identifies itself only as "Reelhost", and sends no account, user or device identifier; like any internet request, it shows those services your server's IP address. Answers are kept in memory on your server for up to a day so the same question isn't asked twice.
What never leaves your computer
- Your media files and their names, library contents, artwork and metadata
- What you watch and when
- Jellyfin passwords, and your Jellyfin user accounts except as described under People you invite. When Reelhost makes a profile for someone you invited, its random password is sent once to your Jellyfin and never kept or shown to anyone
- Which Jellyfin admin is yours. Reelhost links your account to the admin it set up or connected with, and keeps that link (the admin's id and name, never its password) only on your computer
- Sign-in approvals. When someone signs in with their Reelhost account and has no profile on your server yet, your server holds a request with their name, email address and the device's name for 5 minutes, in memory, for an admin to approve or decline in Signal. A notice of it stays in Reelhost's notices on your computer (the last 50) and in Signal's activity log. None of this is sent to us
- The dashboard. Reelhost's dashboard is served by Reelhost on your own computer to your browser. Other computers at home reach it only after you allow that and sign in, and from away only at app.yourname.watchhome.app, through your own computer. What you see and do there isn't sent to us
- Your Windows or Mac password. Reelhost never stores or sends it. On a Mac, the firewall and sleep fixes ask for it in macOS's own prompt, which Reelhost doesn't see
- In the Docker edition, Reelhost's own password. It's kept only as a one-way code in Reelhost's data folder on your server
- Backups. They're saved on your computer and, if you turn on cloud backup, encrypted in a folder you choose (such as one your own OneDrive, Dropbox, Google Drive or iCloud Drive syncs). We never receive them, and without your recovery code nobody can open them
- AI subtitles. The open-source Whisper model runs on your computer, so the audio it listens to and the subtitles it makes are never sent to us or anyone else
- The check-up results, unless you ask Reelhost AI a question (see below)
- Your own channels. The stream, playlist and guide addresses you add, and Stream guard's check of each one, stay on your computer. If you click Tell us on a blocked channel, only its domain goes into a support request you can read before sending
- Control from your phone. The phone password is kept only as a one-way code on your computer. The phones you allow are listed there by device and browser name (for example "iPhone, Safari") with the dates they were allowed and last used, and a one-way code of each phone's sign-in token. While a new phone waits for you to allow it from outside your home, its internet address is held in memory for up to 10 minutes, then forgotten. None of this is sent to us
- Files you send and photos you share through Signal, their names, the people involved and the keys that lock them. See Sharing and sending files
- Signal apps on your server. Each app's Jellyfin sign-in is checked with your Jellyfin and remembered only as a one-way code in memory for a minute. The Signal PIN is kept only as a one-way code; phones that confirm with Face ID or fingerprint are kept by name with their public key only. The activity log (who did what through Signal, and refused sign-ins with the device's address) keeps its last 2,000 entries. Watch together rooms, their chat and guests' passes exist only in memory and end with the room. None of this is sent to us
Sharing and sending files (Signal)
Reelhost never stores your files; it only carries them. This section says exactly what that means. Everything below happens on your own computer or server, between the Signal apps and the browsers of the people you share with. None of it is sent to us, and we run no storage for it.
- Send files. A file you send is encrypted on your own server and waits there, as an encrypted file, until the people you sent it to have picked it up, you take it back, or its end date (7 days unless you pick 1 to 30) passes; then it's overwritten and deleted. The other person saves it on their own device. We don't receive the file, its name, its size, a picture of it or any key.
- What your server keeps for it: the encrypted file; the file's name and size, who sent it and who it's for (as Jellyfin user ids); each person's public key and their private key only in locked form (locked by their passphrase and again by their recovery code, neither of which is kept); for each link, a one-way code of its secret and the file's key locked by that secret (and the password, if there is one); and a history the sender can read, kept 90 days, with no secrets in it. Signal's activity list says a file was sent, never its name.
- Not end-to-end. While you're signed in, your server opens your files for you, so someone who takes over your running server could read them in that time. We don't scan files for malware. If you lose your passphrase and your recovery code, nobody, including us, can open what's waiting.
- Photo sharing. Private links, shares with people, shared albums, partner sharing and event wallpapers point at photos in your own Jellyfin libraries and are served by your own server. Location and camera details are left out of shared copies unless you keep them. Event wallpapers copy nothing; they keep only a name, a start and end, the TVs and the places chosen. Links keep a one-way code of their secret, an optional password as a one-way code, and counts of how often they were opened.
- Editing. Signal's editors no longer save new copies on your server unless an admin turns that back on. Copies saved earlier stay where they are.
- Kids. Kid profiles can receive files but can't send them or make links unless an admin allows it. Reelhost collects nothing about kids' use of these features.
- Removing it. Removing Reelhost deletes waiting files, keys, links, event wallpapers and their histories from your computer. Files already picked up are on the other person's device and aren't touched.
The Reelhost Signal app
Reelhost Signal is our app for watching and listening to your own Jellyfin server on phones, tablets and TVs (Android, Android TV, Fire TV, Roku, Samsung, LG, iPhone, iPad, Apple TV and web browsers). It doesn't contain ads, analytics or tracking. You sign in with your Reelhost account (below). Signal is made for servers that run Reelhost: this version still plays a Jellyfin server without Reelhost and shows a notice on it, and from the first version released after February 1, 2027, Signal needs Reelhost on the server. What you watch, your libraries, photos and recordings go only between the app and your own server.
- Your server. The app signs in to your server through your Reelhost account or with a Jellyfin user name and password you type, and keeps that server's sign-in token on your device. Everything you play, browse or send goes to that server only. We don't receive it.
- On Roku. The channel keeps your server's sign-in token in the Roku's own channel storage and never your password. It sends nothing to Reelhost except the Reelhost account sign-in below, and it has no ads, analytics or tracking. The first time you open it, Roku asks whether to share your account details (such as your email address) with the channel. We ask only because Roku requires that for channels with sign-in. Whatever Roku returns is discarded: it isn't sent anywhere or stored, and the channel works the same if you decline. Removing the channel from your Roku deletes what it kept.
- On Samsung. The TV app keeps your server's sign-in token in the TV app's own storage and never your password. It sends nothing to Reelhost except the Reelhost account sign-in below and a check of whether Discussion is available, which carries no account or personal data. It has no ads, analytics or tracking. Removing the app from your Samsung TV deletes what it kept.
- On LG. The TV app keeps your server's sign-in token in the TV app's own storage and never your password. It sends nothing to Reelhost except the Reelhost account sign-in below and a check of whether Discussion is available, which carries no account or personal data. It has no ads, analytics or tracking. Removing the app from your LG TV deletes what it kept.
- Reelhost account sign-in. On a TV, the app asks api.reelhost.app for a short code, you approve it in your Reelhost account on another device, and the app sends no email, name or password. On a phone, tablet or browser, you type your email address and the app sends it to api.reelhost.app, which emails you a 6-digit code through Resend; the app sends the code back, with a name for itself such as "Signal on Pixel 8". Either way the app gets back a token that can list your account's servers, sign you in on them and sign itself out. If your server doesn't have a profile for you yet, it asks an admin there to approve you, showing your name, email address and device (see People you invite).
- Podcasts (only if you use them). Podcast searches and topics go through api.reelhost.app, which asks the Podcast Index for you. Episodes then play from each podcast's own address. Your subscriptions stay on your device.
- Internet radio (only if you use it). Your server looks up station lists for the app from the public Radio Browser service (radio-browser.info), so the app doesn't contact it, and stations play from their own addresses.
- Suggestions from outside your library (only on servers with Reelhost 0.10.2 or later). To suggest titles you don't have, the app asks your server, which looks up a genre or title from your viewing in Apple's iTunes Search and TVmaze and passes back titles, years and pictures. The app doesn't contact those services.
- YouTube trailers and videos (only if you play one). They play in YouTube's own embedded player, under Google's privacy policy.
- Casting (only if you use it). Casting to a Chromecast uses Google's Cast service; in a web browser, its Cast code loads from gstatic.com.
- Avatar from a photo. Signal can make your profile picture from a photo of you. Your avatar is made on your own Reelhost server at home, or right in your browser if you use Signal on the web. Your photo isn't sent to us or to anyone else, and it's deleted as soon as your avatar is made. Only the finished picture is kept, on your own Jellyfin server, with a short list of the choices it was drawn from (like "curly hair, dark brown"). Nothing about your face is stored, and you can change or remove your avatar at any time.
- Permissions. The microphone is used only while you sing karaoke, and the sound goes to your TV or your server on your home network, never to us. Photos and files on your phone are read only when you choose them to send, and go only to your server. The app lists your server's channels and suggestions on your TV's home screen; that list stays on the TV.
Like any internet request, each of these reveals your IP address to the service that receives it. To delete what the app keeps, sign out or remove the app. To remove a device from your Reelhost account, sign it out there.
Discussion (comments on movies and shows)
Discussion is optional. To join you choose a public handle and a preset picture; we don't ask for your name, photo or birth date. Kids profiles can't use Discussion, and it is for people 16 or older.
- How you're recognised. When you open Discussion, Reelhost on your own server signs a short statement that you are a signed-in, non-kids user of that server. We receive only two one-way codes made from your server's id and your Jellyfin user id, never your server's address, library or Jellyfin name.
- What we keep. What you post (comments, replies, reactions, ratings, recommendations), your friends, blocks, mutes and muted words, and the notifications we show you.
- Music. Discussion for music sends us the album, artist or song you open, recommend or pick: its MusicBrainz ids, or its name and artist when it has none. We keep what you post there, including your best-track picks and the track lists of playlists and DJ mixes you share (song names and ids, never the songs themselves).
- Who sees it. Others see your handle, picture and what you post, to the audience you chose.
- Moderation. Posts are checked by our own automatic filter (on our servers, no outside AI service), then by people we choose: our staff and community moderators, who see only your handle, trust level and the post. Reports and moderation decisions are logged.
- How long. Comments stay until you delete them or your profile is erased (purged within 30 days). Notifications: 90 days. The text of held, blocked or reported posts: 90 days after a decision. The moderation log: 3 years. Signals used to stop banned accounts coming back: while the ban lasts, then 12 months. One-time codes and anti-abuse hashes: up to 7 days.
- Your choices. Export everything Discussion keeps about you, change who sees your posts or turn Discussion off, and erase your profile at any time in Signal → Discussion → Privacy.
- Legal basis. Performing the service you asked for, and our legitimate interest in keeping it safe.
Buying Reelhost
Purchases are handled by our payment provider, Creem (Armitage Labs OÜ, Estonia), which acts as the merchant of record. It collects your name, email address, billing address and payment details under its own privacy policy. Purchases made before October 6, 2026 were handled the same way by Paddle, under Paddle's privacy policy. We receive your name, email address and order details so we can issue your license and help you with support. We email your license key through our email provider, Resend. We never see your full card number.
Free trial of Complete
You start the free trial inside the app. When you do, it sends our API (api.reelhost.app):
- Your email address, to send you the link that starts the trial and up to three emails about it (2 days before the end, on the last day, and the day after it ended), through our email provider, Resend. Each email has a one-click link to stop trial emails. The ones before and after the end may include a one-time discount on Complete that works for a few hours, only through that email's button; it's left out if you've stopped tips and offers or stopped trial emails.
- Whether you ticked "Email me tips and offers about Reelhost" (unticked unless you tick it). We record your answer once you confirm your email; see Tips and offers.
- One-way codes of your email address (written in a standard form), of the random ID Reelhost made for this computer, of your Jellyfin server's ID and, in the Docker edition, of the install's ID. The app sends the IDs already turned into one-way codes, so the IDs themselves never leave your computer. We store only one-way codes made with a secret key held on our server (HMAC), from which nobody can read the address or the IDs.
- Your computer's name, its operating system and the Reelhost version, as for any license activation.
- Your IP address, which we keep only as a one-way code, to allow at most two trials from the same network in 30 days.
We use this only to send the trial and its emails and to stop the same person, computer or server from starting trial after trial. The legal basis is taking the steps you asked for (sending and running the trial) and our legitimate interest in preventing abuse (the one-way codes and the network limit).
How long we keep it:
- Your email address: if you don't buy, until 90 days after the trial ends, then it's replaced by a placeholder. If you buy, it's kept with your order as described under "Buying Reelhost".
- The one-way codes of your email address, computer, server and install: kept, so the same ones can't start another trial.
- The one-way code of your IP address: 30 days.
- Trial requests that were refused or never verified: deleted after 30 days.
If you visited reelhost.app from an ad on the day you start a trial, the trial is counted for that ad's campaign in our visit totals, matched the same way as checkouts (see "How we count visits" below). Nothing about you is sent to an ad platform for this.
Tips and offers (only if you say yes)
On the trial form and in your account's Settings you can tick "Email me tips and offers about Reelhost". It's off unless you turn it on. We keep your answer with the date and where you gave it.
- What we send: now and then, tips for your setup and offers on Reelhost. If you start a checkout with your email (from a trial, your account or one of our emails) and don't finish it, one email the next day asking if you still want it, sometimes with a discount on Complete that works for a few hours. At most one of those in 30 days, and never while you're getting your trial's emails.
- How to stop: the "Stop tips and offers" link at the bottom of every such email (one click), or your account's Settings. Stopping trial emails stops offers too. Receipts, license keys, sign-in links and answers to your requests still arrive.
- What we keep for this: your answer and its date; for each of these emails, when it went, whether it was opened (if our email provider reports it) and whether its offer was used; and, for checkouts you start with your email, the email address, the plan and the time. Unfinished checkouts are deleted after 90 days, and an email's record loses your address after 90 days.
Leaving a yearly plan from your account, we may first offer to switch you to Complete with your yearly price taken off. If you choose that, we cancel your yearly plan with Creem once Complete is paid.
When we know your email (a trial, your account, or one of our emails), we fill it in on Creem's checkout so you don't type it again.
This website
How we count visits (no cookies)
To see which pages help people and which of our ads and links bring visitors, every page of reelhost.app tells our API (api.reelhost.app) about each visit. It sends only:
- the page's address without anything after a "?" (for example /help/plans), and the name of the site that linked to it (for example reddit.com, never the full address you came from);
- the campaign tags in the link you followed, if any (utm_source, utm_medium, utm_campaign, utm_content and utm_term), and whether the link carried a Reddit, Meta or Google ad click id, but never the id itself;
- whether you looked at our prices, clicked a download (Windows, Mac or Docker) or started a checkout (which plan);
- the discount code from a link you opened, if any (see "Discount code links" below).
We don't set a cookie or store anything in your browser for this, except a discount code from a link you opened, and we don't fingerprint your device. To count a visitor once a day, our server makes a one-way code from your IP address, your browser's user agent and a random value that is replaced every day and then deleted; the IP address and user agent themselves are never stored, and once the day's random value is gone, nobody (including us) can link that code to you or to your visits on other days. Bots and our own staff's visits aren't counted. When you start a checkout, the campaign tags of that day's visit (not the code, nothing about you) go with it to our payment provider, so we can see which ad led to a sale.
Because nothing is read from or stored on your device, this count needs no consent. Your browser's Do Not Track and Global Privacy Control signals don't change it, as it never identifies you; they do turn the ad pixels below off. Visits are kept 30 days, and daily totals (for example "120 visitors from reddit, campaign october") for 25 months. The legal basis is our legitimate interest in understanding how our website and advertising work.
Discount code links
If you open a link with a discount code in it (like reelhost.app/?code=REDDIT30), the code is kept in that browser tab's session storage ("reelhost.code") only. It isn't a cookie or local storage, nothing else is stored with it, and your browser deletes it when you close the tab. While it's kept:
- the pricing page asks api.reelhost.app whether the code is valid, to show the discounted prices;
- it's sent with the anonymous visit count above, so we can see how many visits each code brought, only as totals;
- it's sent with your checkout, so our payment provider can take the discount off.
A code that has ended is deleted from the tab when the pricing page finds out. The legal basis is our legitimate interest in offering discounts and seeing which links work.
Do not sell or share my personal information (California and other US states)
We don't sell personal information for money. When you accept ad cookies, Reddit, Meta and Google receive information about your visit, which California law (and similar laws in other states) may treat as "sharing" for cross-context behavioral advertising. To opt out, choose Cookie settings and then "No thanks", or turn on Global Privacy Control in your browser, which we honor as an opt-out. Nothing else changes for you if you opt out.
Everything else on this website
- No other cookies, analytics or tracking scripts.
- If you use Find my key, the email address you type is sent to api.reelhost.app to look up your key, and we keep a record that we emailed it (it sends at most 3 an hour to any address). Nothing else is collected.
- If you ask for a free Docker key, the email address you type is sent to api.reelhost.app. We store it with the key, to email you the key (asking again sends the same one) and, if you later buy Reelhost, to link that purchase to your free key. Requests are counted per email address and per IP address for an hour, to stop abuse.
- The thank-you page after checkout asks api.reelhost.app for your new key, using the order number in its address. That lookup only works for 2 hours after purchase.
- The website's fonts come from reelhost.app itself, not from Google Fonts or another font service. Blog pages are fetched from api.reelhost.app by our web server, which passes on nothing about you.
- Our website keeps no access logs: your IP address and the pages you visit are used only to send you the page. If something breaks, the server records the error, without who caused it.
Your account
- Your Reelhost account is your email address: the one you bought or started a trial with, or the one someone invited to their household. You sign in at api.reelhost.app/account with a one-time link we email you, or with your license key and its email. Signal, and Reelhost's dashboard on another device, can also sign you in with a 6-digit code we email you, which works for 10 minutes. We keep sign-in links and sessions only as random codes we can't reverse, plus the IP address a session started from, to keep accounts safe. A session ends after 30 days or when you sign out.
- To stop sign-in abuse, we count sign-in requests per email address and per IP address for an hour. We store those as one-way codes, not the addresses themselves, and delete them within a day.
- The account shows what we already hold for your license: your key, the computers using it, your watchhome.app address and its IP address, and your plan. Billing changes happen on our payment provider's own pages.
- The account uses one cookie, only to keep you signed in. No analytics or tracking.
- Signing in to Signal with your Reelhost account (a code shown on the TV that you approve signed in to your account, or a 6-digit code we email you) gives that app a sign-in we keep only as a one-way code, with the name the app gives itself (such as "Living room TV" or "Signal on Pixel 8") and when it was last used. It can only list the servers you chose to show and sign you in on them, and it ends after 180 days or when the app signs out. Each time it signs you in on a server, we make a pass for that one sign-in (your email, the server and your role there) that works for 2 minutes and is deleted within the hour after.
People you invite
If you invite someone to your household from Reelhost, we keep:
- Their email address, so we can send the invite (through Resend, showing your email address partly hidden) and so they can sign in with it. The invite link is kept only as a one-way code and works for 7 days.
- Which server they belong to and the Jellyfin profile linked to them there: its id and name. If you didn't pick a profile, Reelhost makes one on your server (hidden from Jellyfin's sign-in screen, never an admin, with a random password nobody is told) and tells us its id and name, so their Signal apps sign in to it.
- Whether they may invite others, when they joined and when they last signed in.
Removing a person deletes this record and their sign-ins and codes. On your own computer, Reelhost keeps a list of the profiles it made for invites (id, name, email and date) so the uninstaller can find them; removing Reelhost removes those profiles only if you choose that. The person you invited can ask us to access or delete what we hold about them (see Your rights).
Support requests and ideas
If you email us or write to us from your account, we keep the conversation so we can help you. If you choose to send diagnostics, we use them only to solve your problem. Feature ideas you post are shown to other customers, without your name or email; we keep who voted for what so each person votes once.
A few weeks after you first activate Reelhost we send one short feedback email, and at most one reminder, from hello@reelhost.app. Your answers (a score, what you use, the ideas you vote for and anything you write) are kept with your license so we can improve Reelhost and follow up if something isn't working; we quote you only if you tick the box, and then by first name only. To stop feedback emails, choose "Don't send me feedback emails" at the bottom of one, or write to support@reelhost.app. Keys, receipts and alerts still arrive.
Support requests you write in your account, and the app diagnostics you attach, may be processed by AI models through OpenRouter (which passes them to the model's provider) to draft or send an answer, after we remove license keys, email addresses, IP addresses, passwords and tokens, and the Windows user name in file paths. Your plan, purchase date and number of computers go with them; payment details never do. Answers written by our AI assistant say so, and replying "human" brings a person. In the app, Ask Reelhost sends only your question, the conversation so far, the check-up results and any log lines it attaches, cleaned the same way; the library fixer sends only file names and folders relative to your library. No video, music or other media leaves your PC. We log each AI request's size and cost, not its content.
Why we use it (legal bases)
- To provide what you bought or asked for (licenses, free trials, free Docker keys, the Docker image, updates, addresses, Free TV, Reelhost AI, support): performance of our contract with you, or steps you asked for before one.
- To keep Reelhost secure and prevent abuse (rate limits, key-sharing checks, one trial per person, fraud and chargeback handling): our legitimate interests.
- To keep records we must keep for tax, accounting and legal reasons: legal obligation.
- Optional features you turn on, such as sending diagnostics with a support request, tips and offers by email, and ad cookies and pixels on this website: your consent, which you can withdraw at any time.
- A one-time discount in your own trial's emails, about the product you're trying: our legitimate interest, with a one-click way to stop it in every email.
- Counting visits to this website without cookies, and discount code links (see above): our legitimate interests.
We don't sell your information. We don't use what we hold about you as a customer (your email, license or support requests) for advertising, and we never upload it to ad platforms. The only information that reaches ad platforms is what their pixels collect on this website after you accept ad cookies, as described above.
Who receives it
We share personal information only with service providers who process it for us under contract, and only what each needs:
- Creem (payments, as merchant of record; Paddle for purchases made before October 6, 2026), Resend (sending email), Cloudflare (DNS for watchhome.app addresses), OVHcloud (our servers, in the United States), OpenRouter and the AI model providers it routes to (Reelhost AI and support answers, as described above).
- Reddit, Meta and Google, only if you accept ad cookies on this website, through their pixels (see "Ad cookies and pixels" above). They act under their own privacy policies.
- Authorities, if the law requires it, or to protect our rights, our customers or the public.
- A buyer or successor, if Wizzered's business is sold or merged, under this policy.
International transfers
We're based in the United States and our servers are there. Some of our providers process data in other countries. Where the law requires it, transfers are protected by safeguards such as the EU Standard Contractual Clauses.
Security
License keys are stored encrypted, sign-in codes and sessions only as one-way codes, and all traffic to our services uses HTTPS. Admin access needs a password and a one-time code. No system is perfectly secure; if a breach affects your information, we'll tell you as the law requires.
How long we keep data
- Order and license records: for as long as your license is in use, and then as long as the law requires for tax and accounting (typically up to 7 years).
- Your watchhome.app name and its last known IP address: while your address is in use. Releasing the name in the app deletes its record straight away. The app.yourname.watchhome.app record for your phone exists only while that's turned on, and goes when you turn it off or release the name.
- Support conversations and diagnostics: up to 2 years after the conversation ends, then deleted.
- Sign-in links: until used or expired. Sessions: 30 days. Rate-limit counters: deleted within a day.
- Free web addresses: the one-way code of your installation's ID, with the name, while the address is in use. The one-way code of your IP address used for the limit on new free names: 24 hours. A name from a trial that ended without a purchase is released 30 days after Reelhost last updated it (and no sooner than 30 days after the trial ended).
- People you invite: while they're in your household; removing them deletes it. Invite links work for 7 days.
- Records of AI requests (size and cost, not content): up to 2 years.
- Problem reports (only if you turned them on): 180 days. "Didn't help" questions: 90 days. Turning reports off deletes what's still waiting on your computer.
- Docker image downloads (license or free-key id, IP address and network, time, what was pulled): 90 days, then deleted.
- Server alerts: your settings and the latest heartbeat while alerts are on. Heartbeat history: 90 days, then deleted. Turning alerts off in the app deletes all of it straight away; a server not heard from for 90 days is forgotten.
- Free Docker keys (your email address and the key): until you ask us to delete them. Deleting your account removes them too.
- Servers shown in your Reelhost account: while that's on and the computer is on your license. Signal sign-ins: 180 days or until the app signs out; codes for them: 10 minutes; one-sign-in passes: deleted within an hour of ending. Deleting your account removes all of it.
- Website visit counts: each visit 30 days; daily totals by page, referring site, campaign and device, and purchases by plan, amount and campaign (nothing about who), 25 months. The daily random value behind the visitor code: deleted at the end of its day.
- Free trials: your email address until 90 days after a trial you didn't buy ends, then replaced by a placeholder; the one-way code of your IP address 30 days; refused or unverified requests 30 days; the one-way codes that stop a second trial, kept (see "Free trial of Complete").
- A discount code from a link: in your own browser tab, until you close it.
- Tips and offers: your answer, while your account exists (an unsubscribe is kept so we don't email you again). Unfinished checkouts: 90 days. A tips-or-offers email's record: your address 90 days, then only counts.
- "Not now" on the app's offer: 7 days, in the app on your computer.
- Your cookie choice: 12 months, in your own browser. Ad platforms' cookies: as each platform sets them, only if you accepted.
Deleting your account in your account settings removes your personal information, except records we must keep by law.
Your rights
Depending on where you live, including under the GDPR, the UK GDPR, the California Consumer Privacy Act and the Texas Data Privacy and Security Act, you may have the right to access, correct, delete or get a copy of your personal information, to object to or restrict some processing, to withdraw consent, and to not be discriminated against for using these rights. To use them, email support@reelhost.app from the address on your license, or use your account settings. We'll verify your request and answer within the time the law sets (usually 30 to 45 days). If we decline a request, you can appeal by replying to our answer. You can also complain to your local data protection authority.
Children
Reelhost is for adults (see our terms) and isn't directed at children under 16. We don't knowingly collect their personal information; if we learn we have, we delete it. An adult may set up a kids profile on their own Jellyfin server. That profile lives on the adult's server, not with us, and Reelhost collects nothing about a child's use of it. A child can't buy Reelhost or create a Reelhost account, and household invites are for people who may have one. For a child, an adult uses a kids profile on their own server, which needs no email address and no Reelhost account.
Changes
We may update this policy. We'll post the new version here with its date, and if we change what the app sends we'll say so in the app's release notes before the change ships. For material changes we'll also tell paying customers by email.
Contact
Wizzered Inc., 5900 Balcones Drive, Suite #32859, Austin, TX 78731, USA. Email support@reelhost.app.