Something I seldom see listed here is simply the possibility of splitting the profile: - My ISP knows all my normal internet traffic, and all the caveats that

Something I seldom see listed here is simply the possibility of splitting the profile: - My ISP knows all my normal internet traffic, and all the caveats that apply (HTTPS, SNI, IPs, etc) - My VPN knows a much smaller subset of traffic used for a different purpose. Also, do this in a VM, or on a separate computer, or otherwise somehow containerize your cookies and browser and things. (no, I still don't think people are correlating between profiles using webgl in any large-scale way. If they were, I'd be getting fewer CAPTCHAs.) Yes, the VPN could presumably violate their privacy statements and sell your information, but that still avoids the primary concern: an ad domain that lives on the two websites you'd like to visit (ie, the normal vs the private site) With a new IP, and a different host (VM, physical computer, etc) there's nothing to correlate. The website in question doesn't know it's you -- only the VPN does. And it doesn't seem likely they're going to sell your information in such a way that the website can figure out which cookie to correlate with which identity. So, the primary tracking method of the internet should be defeated in this way.