Customer Choice goes too !!!
It may just be a 'technical glitch' but customer choice seems to have disappeared too.
The Webwise Q&A section asks:
"How can I distinguish between cookies that were placed by Webwise and those given to me by websites I visited?
The Webwise cookie is clearly named "webwise-uid" so it can be easily identified. It will either contain the unique identifier string if you’re opted in or it will contain "OPTED_OUT" if you are not.
As explained on the >>>Customer Choice<<< Process page, when a user opts into the BT Webwise service, a Webwise UID cookie, containing a unique random number is placed on the user’s computer. This master cookie is held is the Webwise.net domain. When the user then visits other websites, the Webwise system stores a copy of the Webwise UID cookie within the browser in each the website domains visited by the user. The cookies are clearly labelled as belonging to Webwise as noted above and as a result can be easily identified as different to those cookies which may be placed by the website itself."
The link to the customer choice page now returns a 404 error
http://www2.bt.com/static/i/btretail/webwise/customer-choice
This page was the home of the diagram which showed the browser hijack that enabled the forged cookies to be set. It is still visible in the Google cache for those who have not seen it before.
http://216.239.59.132/search?q=cache:4eivn4MyRSQJ:www2.bt.com/static/i/btretail/webwise/customer_choice.html+site:www2.bt.com+%22customer+choice%22&hl=en
Are they trying to remove evidence that can be used in a class action by websites that object to BT adding forged cookies that claim to be from every domain visited but are really evidence of BT fraudulently impersonating other websites?
If you find a webwise-check or webwise-uid cookie on your computer, please make a copy of the cookie file before deleting the cookie. The class action needs evidence which has so far been the one problem with any legal action re the 2006 and 2007 trails where cookies and cache were quickly deleted by anyone who discovered the hijacked performed during those trials.
If you can also save browser logs showing the hijack / redirection that sets the cookies, even better.