Block dangerous and deceptive sites creates a Google tracking cookie
Hi,
I was surprised to find a persistent Google cookie in my cookie jar. I use cookie destructor, and no 3rd party cookies, and despite having removed Google's cookie manually multiple times, it kept reappearing. After disabling 3rd party extensions, I was left with Firefox preferences, and it seems that Block dangerous and deceptive... is at the root. I believe you download your "dangerous" sites from Google, but leave a cookie. Since this is done outside the regular browser, the cookie is almost impossible to remove. No extensions removes it and it is probably not considered 3rd party.
I put much effort to avoid Google's all encompassing database, and I believe Mozilla is one of the few browsers that support user privacy as a policy. It's somewhat sad that it inserts this cookie through the backdoor. I hope you will resolve this issue or at least add a notification and with an opt out, if you have other sources, more anonymous, of data.
Thanks, Yuval.
Ndryshuar
Zgjidhje e zgjedhur
hi yuval, this cookie is landing in a sandboxed jar and cannot be used by google to track you during browsing if that's any consolation to you.
https://wiki.mozilla.org/Privacy/Features/Multiple_Cookie_Jars https://bugzilla.mozilla.org/show_bug.cgi?id=897516
Lexojeni këtë përgjigje brenda kontekstit 👍 0Krejt Përgjigjet (2)
Zgjidhja e Zgjedhur
hi yuval, this cookie is landing in a sandboxed jar and cannot be used by google to track you during browsing if that's any consolation to you.
https://wiki.mozilla.org/Privacy/Features/Multiple_Cookie_Jars https://bugzilla.mozilla.org/show_bug.cgi?id=897516
I appreciate the fast response. I've verified that indeed the cookie is not sent to Google from a regular browser window, however, this leaves two issues: 1. A cookie is still planted by Google and can be used by it to track the browser if I understand correctly. Why not just drop the cookie jar once we're done? There doesn't seem to be any sense in maintaining the cookie jar in this scenario. 2. Stage 2 of the multiple cookie jars (user experience design - revamp the cookie UI) seems not to have been implemented or at least I fail to see any indication that the Google cookie is marked differently. I also wonder what happens if there are two similar cookies of the same name and domain in separate cookie jars.
But I admit these are smaller issues. I won't be using the safe browsing feature but indeed it seems to have been thought out.
Thanks, Yuval.
Ndryshuar