Welcome to WebmasterWorld Guest from 220.127.116.11
It would be nice to tag on something like "See google.com/privacy for more information" since this is their requirement.
...this does seem to have been poorly done.
Certainly not specifically why Google stock is tanking this morning but this can't be helping it.
The TOS that is currently displaying for me is also dated November 3, 2005, we may be witnessing a major "ooops!" for this company. If the cookies in question that we must disclose are in fact those placed by AdSense shouldn't we be given at least as much info about them up front as we are required to disclose? This seems to be a TOS chasing its own tail like a deranged pooch.
Should we also write somewhere that the NSA is likely to be following your every movement on the internet and reading your emails? Is it our responsibility to inform users of every possible legal or quasi-legal infraction third parties like Google or the government engage in?
NO. NO. NO.... but I still like getting paid every month.
I really think - especially after watching the biggest joke of the week last week, the ebay "boycott" - that people need to devote more time to runing their businesses and less time worrying about "compliance with the big dogs."
As I do with every authority figure, I act as though I am complying and then do whatever I deem appropriate. Usually, I end up not breaking any rules, only bending them a bit.
I suspect this also has something to do with Google's anticipated acquisition of DoubleClick, and the terms of the privacy lawsuit settlement into which DoubleClick entered with several states back in 2002.
Google ought to fire all but one of it's lawyers and hire some people who can kill the MFA garbage once and for all (or maybe someone who could write a coherent paragraph explaining what their legalese nonsense meant. )
Too many lawyers, not enough chum. AAArrrgghhh.
Fact is google are setting up web beacons on your sites serving ads, and other sites serving ads..
the conspiracy is they'll web beacon everything and know your visitor :)
Quote from [allaboutcookies.org...]
What are Web Beacons, otherwise known as Web Bugs, and how do the work?
A web beacon is a transparent image file used to monitor your journey around a single website or collection of sites. They are also referred to as web bugs and are commonly used by sites that hire third-party services to monitor traffic. They may be used in association with cookies to understand how visitors interact with the pages and content on the pages of a web site.
For example a company owning a network of sites may use web beacons to count and recognise users travelling around its network. Being able to recognise you enables the site owner to personalise your visit and make it more user friendly.
The part "Being able to recognise you enables the site owner to personalise your visit and make it more user friendly." gives me no doubt in question google will web beacon us all . :)
Now would be a good time to comment.
Could somebody post a legal-department approved privacy notice we can put on our sites?
The first post of this thread probably should have the actual blog details. For those who missed it, here it is verbatim?
Updated Terms and Conditions
Every now and then, we update the AdSense Terms and Conditions to make sure they're in line with policies across Google, and to prepare for future changes to the products and services we offer. As part of these regular updates, you'll soon sign in to your account and see that the Terms have been updated, prompting you to read through and accept them.
This time around, most of the changes to the Terms and Conditions fall into two broad categories: 1) future products and features and 2) privacy requirements. Specifically, one of the main changes is that the terms anticipate future products that may become available in other advertising formats and mediums, for example Gadget Ads. As we look forward to monetizing more online and offline content, we've re-worded some portions of the terms to make them applicable across a broader array of media and formats -- anticipating, for example, that future products may be priced, paid, or managed differently than current ones.
The changes aren't limited to the areas above, however; we've made small changes throughout, so it's a good idea for you to review them thoroughly before accepting.
Posted by Julie Beckmann - AdSense Publisher Support
Monday, February 25, 2008 at 2:40:00 PM
[edited by: potentialgeek at 7:53 pm (utc) on Feb. 26, 2008]
Your web server gets and logs this information as well as soon as someone visits your site (through a HTTP request). Via the web bug, a third party site can obtain the same information about your visitors.
I don't see anything in the TOS that say we are giving G the right to serve cookies or web beacons FROM our website, which makes the requirement for disclosing "that third parties may be placing and reading cookies on your users’ browser, or using web beacons to collect information, in the course of ads being served on your website," a bit confusing.
This does not strike me as a good move on G's part. They may do no evil, but they are forcing site owners to cut a deal with the devil - or opt out entirely.
Also, the liability here should be pass through. If Google's ads do something to my visitors, then Google should identify what that is and accept liability for improper notice or activity. Expecting your Adsense publishers to get this right for you is burdensome because we do not fully know or control what you do with the data collected.