Privacy
Last updated 18 November 2026. Short version: this page collects nothing, and the software only reads what your household's server already knows.
1. This website
These pages are static files. There are no cookies, no analytics, no advertising, no third-party scripts, and no fonts loaded from anywhere else. The web server keeps ordinary access logs (time, requested path, IP address, user agent) for debugging and abuse handling; they are rotated and not used to build profiles.
2. What the relay does with data
- Reads the request queue, library status, and artwork for your household from the bridge running on your household's Plex server.
- Caches that data — including artwork — in a folder next to the executable on your own device, so the TV feels immediate. Cache is yours to delete.
- Stores one secret: the access key from your invite, in
relay.envwith0600permissions. It is used to talk to your bridge and nothing else. - Does not send anything to a third party. There is no telemetry endpoint, no crash reporting service, and no usage counter.
3. What the server side holds
The bridge runs on the household's Plex server and holds, at most: the list of requests and their status, the names of household Plex users as they appear in Plex, and cached artwork. It does not store passwords, payment details, or anything imported from outside that server.
Everything the software shows already exists in the household's own Plex, Seerr, and download tools. ESPLEX Companion does not create a new copy of your viewing history anywhere else, and it does not publish any of it.
4. Who can see it
- People on the household's own network, and anyone holding the household's access key.
- The person who runs the beta, when debugging a reported problem — with your knowledge, and only the data needed for that problem.
- Nobody else. There is no public endpoint showing any household's queue.
5. Children and shared devices
A TV is shared. The channel shows the household's request queue, which is visible to anyone who picks up the remote. It is not a private profile system, and it does not try to be one.
6. Retention and removal
The relay's cache stays on your device until you delete it. Server-side data is kept for as long as the household is part of the beta. Ask, and it is removed — esplexops@gmail.com. Written requests get a written confirmation once the data is gone.
7. Changes
If this policy changes materially, this page is updated and the change is announced to beta households. The "last updated" date at the top is the source of truth.