@Trotter999 said:
As far I can see, they have not updated the Privacy Policy to reflect what they were collecting, but changed it to collect more info, without stating what exactly is collected.
They actually stated what is collected, although in a clumsy way (the infamous “such as” sentence), but the new communication from the CEO seems to promise a more transparent, more granular approach to opt-out and data harvesting. Also if you read the latest CEO message, it’s useful to point out that there were exceptions to the opt-out, making the “old” opt-out option actually quite misleading.
One of the posts in the thread that I created contained this
"After forwarding your comments to the DEV Team I have been told that there is work being done to update/improve the Privacy Policy, and in addition to that you can use the following URL to see what info Plex sees about your server:
Assuming this still works after 20th September, it may be a good idea to run this before the 20th September and then after the change, to see if the info sent has changed.
I was on the road when I replied, so I didn’t quite compose my thoughts. And for the record, I’m not against all data gathering.
What it boils down to (for me…probably others) is level/source permissions are fine, but why not consolidate them in one spot (as adrianwi wrote? You don’t necessarily know if these permissions are absolute or qualified until you find something elsewhere.
@Core-Lokt said:
What it boils down to (for me…probably others) is level/source permissions are fine, but why not consolidate them in one spot (as adrianwi wrote? You don’t necessarily know if these permissions are absolute or qualified until you find something elsewhere.
I agree, best of both worlds would be a “privacy panel” where you can see some “status lights” regarding what data gathering you have enabled and what not, together with some links to the relevant sections in the preferences, so that you can go in the context and see what’s that stuff and decide if it’s ok for you to keep it enabled or not.
How do I request a refund for my lifetime Plex Pass, since Plex is changing the terms of our arrangement? I have zero interest in having any of my data collected, and shouldn’t have to play whack-a-mole to disable tracking of what I’m doing on my own personal server.
We hope this allays the concerns many of you have expressed. We’ll work on getting the Privacy Policy and summary page updated over the next few days. We’d do it today, but…lawyers. Again, thank you for all your thoughtful feedback and recommendations!
What’s happened, Keith? Or is it still with the lawyers? Tomorrow is the 20th!
I raised a support ticket earlier in the week asking basically the same thing. Here’s the response I got:
“We’re definitely still working hard to get everything ready so things can go into effect, ideally on September 20. We don’t have specifics to share about it right now, though, sorry.”
I’m not sure what to make of the lack of info. I want to trust them, but I’m wary.
@adrianwi said:
So it’s gone in the plexpass 1.9.0 release?
it has for me, i’m currently building a fresh virtual machine to install it on, just in case there’s something odd in my setup causing it to disappear. but it certainly seems like the original policy is the plan.
Spinning up in a VM sounds like a good idea! It’s times like this where your glad the FreeBSD version doesn’t automatically update Although I suspect the checkboxes can just be overridden at their end on older versions
UPDATE - yes, in 1.9.1 the “Send anonymous usage data to Plex” checkbox has been replaced with “Send crash reports to Plex” so it looks like Plex really don’t give a f**k, even after making it sound like they did
@adrianwi said:
Spinning up in a VM sounds like a good idea! It’s times like this where your glad the FreeBSD version doesn’t automatically update Although I suspect the checkboxes can just be overridden at their end on older versions
Although I suspect the checkboxes can just be overridden at their end on older versions 
Although I suspect the checkboxes can just be overridden at their end on older versions 
