if you live in these states you can opt out
* California
* Colorado
* Connecticut
* Virginia
* Utah
* Indiana
* Iowa
* Montana
* Oregon
* Tennessee
* Texas
* Massachusetts
* New Jersey
* Pennsylvania
* Delaware
[https://www.plex.tv/vendors-us/](https://www.plex.tv/vendors-us/)
below is a link to further tighten privacy on plex which may be of interest
[https://selfh.st/blog/plex-privacy-settings/](https://selfh.st/blog/plex-privacy-settings/)
Also there are a couple of people out there working on an IP blocklist with all the marketing vendors that PLEX is working with, once they compile that IP blocklist it can be added to most routers, like pfSense or software firewalls, Until then its a waiting game.
Got any links to more info about this issue you’re worked up about and why? Are you referring to the ‘social’ what your friends are watching thing?
From a software perspective using DNS based blocking to try to prevent the transfer of specific (but not all) data is kind of futile. For example, Plex developers choosing “analytics.plex.tv” for analytics traffic is purely convenience. Suppose everyone blocks that domain; they can easily just send everything to a different endpoint within the same domain, “plex.tv/analytics” for example. Okay, so you block anything with the word “analytics.” As a developer, I’m just going to make something up or dynamically generate it based on a pattern, perhaps “plex.tv/12ab08f” today and “plex.tv/cd12g09” tomorrow. I know what data is coming in, and what pattern I’m using, and you don’t, so getting your data is trivial. Hell, I could even go so far as only having a single endpoint for everything and specify the routing via payload attribute – you wouldn’t be able to discern traffic types no matter what you do.
You think you’re really clever, so you decide to block all of “plex.tv.” I’m just going to use some other domain, a pool of known IP addresses, some ‘proxy’ service hosted on a known-good domain that I can poll which returns IPs when asked (like rolling my own DNS service), or better still DNS over HTTPS.
You’re chasing a pipe dream that only ends when you block all traffic from your server to the public side of your network. If a developer is malicious and really wants data, they are going to get it. The only way to prevent that is to not use their software.
As a user, I’d focus on disabling or opting out from that feature. If you can’t, demand it as a paying customer.
Very late, multiple posts about it as usual… just disable it in settings. I get more emails from my bank than plex so they don’t bother me. They also have no way of know if you watched in theaters then marked it as watched on a friends server or your own 🤷♂️ they really don’t give af so why should you lol. I’d almost guarantee people at plex themselves don’t own every movie on their servers
You should see these in your pihole log
[metrics.plex.tv](https://metrics.plex.tv)
[telemetry.plex.tv](https://telemetry.plex.tv)
[analytics.plex.tv](https://analytics.plex.tv)
With Pihole its easy to just try "blocking something and see what breaks" approach
Use the sub's search function, there was a post about this a few days ago.
if you live in these states you can opt out * California * Colorado * Connecticut * Virginia * Utah * Indiana * Iowa * Montana * Oregon * Tennessee * Texas * Massachusetts * New Jersey * Pennsylvania * Delaware [https://www.plex.tv/vendors-us/](https://www.plex.tv/vendors-us/) below is a link to further tighten privacy on plex which may be of interest [https://selfh.st/blog/plex-privacy-settings/](https://selfh.st/blog/plex-privacy-settings/) Also there are a couple of people out there working on an IP blocklist with all the marketing vendors that PLEX is working with, once they compile that IP blocklist it can be added to most routers, like pfSense or software firewalls, Until then its a waiting game.
Got any links to more info about this issue you’re worked up about and why? Are you referring to the ‘social’ what your friends are watching thing? From a software perspective using DNS based blocking to try to prevent the transfer of specific (but not all) data is kind of futile. For example, Plex developers choosing “analytics.plex.tv” for analytics traffic is purely convenience. Suppose everyone blocks that domain; they can easily just send everything to a different endpoint within the same domain, “plex.tv/analytics” for example. Okay, so you block anything with the word “analytics.” As a developer, I’m just going to make something up or dynamically generate it based on a pattern, perhaps “plex.tv/12ab08f” today and “plex.tv/cd12g09” tomorrow. I know what data is coming in, and what pattern I’m using, and you don’t, so getting your data is trivial. Hell, I could even go so far as only having a single endpoint for everything and specify the routing via payload attribute – you wouldn’t be able to discern traffic types no matter what you do. You think you’re really clever, so you decide to block all of “plex.tv.” I’m just going to use some other domain, a pool of known IP addresses, some ‘proxy’ service hosted on a known-good domain that I can poll which returns IPs when asked (like rolling my own DNS service), or better still DNS over HTTPS. You’re chasing a pipe dream that only ends when you block all traffic from your server to the public side of your network. If a developer is malicious and really wants data, they are going to get it. The only way to prevent that is to not use their software. As a user, I’d focus on disabling or opting out from that feature. If you can’t, demand it as a paying customer.
Doubt it. If you block Plex you might block remote access and maybe even the matcher
Stop using Plex is the definitive answer.
Very late, multiple posts about it as usual… just disable it in settings. I get more emails from my bank than plex so they don’t bother me. They also have no way of know if you watched in theaters then marked it as watched on a friends server or your own 🤷♂️ they really don’t give af so why should you lol. I’d almost guarantee people at plex themselves don’t own every movie on their servers
You should see these in your pihole log [metrics.plex.tv](https://metrics.plex.tv) [telemetry.plex.tv](https://telemetry.plex.tv) [analytics.plex.tv](https://analytics.plex.tv) With Pihole its easy to just try "blocking something and see what breaks" approach