Why does Avast use tracking cookies in the Forums? I know its not about targeting members with advertisements about Avast Anti-Virus, because the people that are here are already using Avast.
I think most people that have Avast Anti-Virus with all of its different shields for protection, are concerned with privacy, so why would Google, and Adobe, be allowed to track every move the members make on the Internet?
Avast on the forum website uses Google Analytics tracking, abine DoNotTrackMe blocks that for me.
Ghostery reports this: http://www.ghostery.com/apps/omniture_(adobe_analytics)
Kiss Privacy blocked 3 requests.
Well blocked effectively as reported - We could not fulfill your request for /index.php?action=
This may be caused by a malfunctioning proxy server or browser privacy software.
My browser protection (also with addidtional script blocking is effective)…
And all tracking cookies should be cleansed at the end of a browser session, via Tab Cookies manager or via a SAS scan…
Good you are aware but there realy is no threat here to your privacy, your cookie value = ID + IP, but you can edit this…
Tracking lists such as ( abine, adblock, easylists ) like polonus mentioned are a good way of curbing tracking, you can also block a lot of the ad’s and tracking such as the youtube ad’s played before video’s by adding the site blocks I have shown in the pic below.
I’m concerned with Google, that sucks up information like a giant vacuum cleaner. It seems like Google Analytics is waiting at every website to see where you came from and where you are going.
I would love to see this company collapse along with all its servers.
I would add Ghostery to you’re FF add-on while you have NoScript-Better Privacy as well, I have Ghostery see my sig below I wouldn’t be wasting my time with Avast Site Blocking while Ghostery is doing all the hard work
Don’t forget to check you’re Ghostery option settings very carefully when you’re starting using it, because it not set to automatically up dating the tracking sites so double check you’re Ghostery settings
The Google privacy invasion data slurping and sucking almost cannot be circumvented.
For instance when I try to use Tor in the browser with NoScript enabled r, Google won’t allow my browser to function as it holds me for a so-called malcious bot and not a (trackable) human user. Google Sharing could help a bit…
Not to mention you can have your browser block third party cookies, so it would only accept cookies for the actual site/domain you are on. You can also have your browser clear cookies on shutdown.
I also use the FF CookieMonster add-on to manage cookies, mostly I only allow session cookies for the site/domain I’m on.
You are right, you can’t get away from Google, even if you stop using Google Search.
Firefox comes with a Google search bar by default. I removed it and replaced it with a Yahoo search bar. I also removed any reference to Google in Firefox and Thunderbird.
After doing that, I found that Avast Network connections is still allowing Google to establish a connection with Firefox and Thunderbird.
What is even worse is that Avast uses Google for some unknown purpose, and allows Google to establish a constant connection through AvastUI.exe, and if you disable this, your connection to the Internet is gone.
Thank you very much for that, CookieMonster extension, it now sits comfotably installed on my Google Chrome launched via Chrome Privacy Guard
Read Sarah Perez’s link here: http://readwrite.com/2008/12/21/three_ways_to_enjoy_google_chrome_without_privacy_concerns
I have chosen this one of that three: http://sourceforge.net/projects/chromeprivacy/
Chrome Privacy Guard is a small tool that automatically deletes the unique Client ID before each run of Google Chrome. This tool scans the “Local State” file inside the Chrome directory, removes all Client ID related info and automatically starts Chrome. (open software)
And I use this to check on cookies, third party tracking etc.: http://www.cookie-checker.com/
The only problem I have is with the bb2 screener cookie. Not because of the cookie. No way, we need this one.
As it is a third party session cookie from the bad-behaviour antispam security system. Insecurities and attacks can be blocked using bad-behaviour…
A problem because it is exploitable and for instance can be send twice (exploits to abuse for it were seen well into this year as are ongoing XSS exploits)
See for instance: http://exploitsdownload.com/search/bb2_screener_/
See: http://stackoverflow.com/questions/6418617/forensic-analysis-of-an-actual-hacked-web-site (link author vtortola)
Insecurities can be blocked using bad-behaviour…