| 11:32 pm on Feb 25, 2008 (gmt 0)|
Nope, me too.
| 11:33 pm on Feb 25, 2008 (gmt 0)|
*am waiting for someone to spot what we should watch out for before i click accept*
but everyone has to accept it anyway otherwise no account ...
| 11:33 pm on Feb 25, 2008 (gmt 0)|
| 11:38 pm on Feb 25, 2008 (gmt 0)|
No way out, you MUST sign it to be in, if not, forget AdSense revenues.
| 11:42 pm on Feb 25, 2008 (gmt 0)|
Hmmm I want to use my email address that is already registered, but now way it will let me.
1) Yes I'm the only one who logs in to this AdSense account.
Now at 2.. What do I pick?
a) I have an email address and password (Google Account) I already use with Google services like Gmail, Orkut, or the personalized home page.
b) I do not use these other services. I would like to create a new Google Account.
I think (b), but than I get an error: "A user with the email you specified already exists. Already have a google account? Try logging in."
| 11:44 pm on Feb 25, 2008 (gmt 0)|
| 11:56 pm on Feb 25, 2008 (gmt 0)|
Okay got it: I needed option(a) again..
| 11:57 pm on Feb 25, 2008 (gmt 0)|
k I read it, what's different?
| 12:43 am on Feb 26, 2008 (gmt 0)|
Oh dear... that means we must notify our users on our site about adsense?
| 12:44 am on Feb 26, 2008 (gmt 0)|
| 1:18 am on Feb 26, 2008 (gmt 0)|
|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. |
Grab your wallet.
| 1:55 am on Feb 26, 2008 (gmt 0)|
I've stuck this on the about page on my site, as a starter:
|Your privacy is important to us. |
You should know that third parties may be placing and reading cookies on your browser, or using web beacons to collect information, in the course of ads being served.
But I'm going to wait for jensense to get back from SMX and go through it with her fine tooth comb to make sure I got everything before I agree.
Man, I hate these things! I couldn't even tell you what a web beacon is, but I have to warn my visitors about them? And given that people don't enter a site on the about page, they will have the cookie before they read that they might get it. Silly!
| 2:04 am on Feb 26, 2008 (gmt 0)|
We've always prided ourselves on a NON-cookie-ized site and mention it to our readers. From the casual, non-alertist mood of the above mentioned blog my opinion upon reading it says we don't need to worry about notifying readers unless we opt into the new features like "gadget ads". They BETTER be opt-in only. Otherwise they better start posting officially sanctioned, legalese text for us to copy in as a template and specifying exactly WHERE it needs to be posted (every page, home page, pop-up which must be accepted before admission to our site). Of course doing so might also be considered unduely drawing attention to the ads and thus against other Terms. After all it's not US that is providing the tracking cookies, etc. but the distrusting advertisers. Why should I apologize for some other site's behavior when I don't even have any control over which ones I'm linking? I can't control where the reader might go to after my site so I might as well warn them that browsing the internet in general could be hazardous to their computers health. I say make THE ADVERTISER pop up a warning requiring reader acceptance upon all affected clickthrus before entering THEIR site and still pay US whether the reader accepts it or NOT! GagSense just keeps getting more disgusting every day.
[edited by: MikeNoLastName at 2:20 am (utc) on Feb. 26, 2008]
| 2:10 am on Feb 26, 2008 (gmt 0)|
|They BETTER be opt-in only. |
Don't bet on it.
| 2:15 am on Feb 26, 2008 (gmt 0)|
I think this is the perfect opportunity for ASA to pay a visit. Maybe he/she should clarify some of the questions raised here.
| 2:31 am on Feb 26, 2008 (gmt 0)|
I have put this notice on every page that has an AdSense ad:
|This page places no cookies, no user information is collected by [website name] beyond ordinary server logs. |
| 2:44 am on Feb 26, 2008 (gmt 0)|
| 3:16 am on Feb 26, 2008 (gmt 0)|
Has anyone found a FAQ on this change? Something that can help us COMPLY with the new T&Cs.
If not, might I suggest that ASA help us with the type of language we would need to verify is in our privacy notices. After all, I believe the intention is to make sure Google publishers are notifying their visitors what Google might be doing and many of us would be guessing at this point.
| 3:51 am on Feb 26, 2008 (gmt 0)|
Re privacy policies:
"As a mom-and-pop operation owned by liberal-arts types, we don't even know how to spy on you. (When we hear the term 'privacy issue,' we're likely to think of an open bathroom window facing the street.)"
| 3:57 am on Feb 26, 2008 (gmt 0)|
I didn't get the paragraph about the cookies. Do we need to notify the users about cookies on every page with adsense products or does this only concern "new adsense products" that haven't benn released yet?
| 5:36 am on Feb 26, 2008 (gmt 0)|
| 5:46 am on Feb 26, 2008 (gmt 0)|
Google these days:
1) Take a really big gun.
2) Hold down, aim at own feet.
Why do they always come up with these half-baked, not thoroughly thought-through instructions, options, products, solutions, services? Why is there no FAQ? They can't be serious to have just this blog post to communicate?
To me it looks like someone from legal department said: "Hey Adsense group, I've been thinking... Shouldn't we explain that we are collecting private data? This is a huge risk for us!", and someone from Adsense replied: "But the sites where the data collection appears to happen are beyond our control...! You know, these are not Google property." - "Ah, I understand. Well, then let's make it mandatory for the site owners to explain the data collection in their privacy policies." - "Not all of them have privacy policies." - "Heck, then let's make THAT mandatory. I'm going to change the T&C right now. Thanks for the chat."
| 5:59 am on Feb 26, 2008 (gmt 0)|
| 6:13 am on Feb 26, 2008 (gmt 0)|
| 12:12 pm on Feb 26, 2008 (gmt 0)|
What's new and scary is you must notify users that your ads use beacons.
This is going to be an adsense killer if they enforce it.
web beacons to collect data in the ad serving process.
Just wait until newbies learn that means you are being tracked across sites whether you click on ads or not, even if you have cookies disabled.
This should be a front page topic, no? It's huge.
Wasn't Yahoo forced by law to give people an opt-out for beacons?
Here's yahoo's version: [info.yahoo.com...]
[edited by: amznVibe at 12:16 pm (utc) on Feb. 26, 2008]
| 12:58 pm on Feb 26, 2008 (gmt 0)|
| 1:16 pm on Feb 26, 2008 (gmt 0)|
interestingly, I'm no longer being prompted to agree to the terms when I log in. Anyone else?
I wonder if someone over there has been listening? :)
| 1:36 pm on Feb 26, 2008 (gmt 0)|
Since when was cookies suable? I place a cookie when I ban someone from my site, does that mean that their isp will sue me ?
Why would google state for you to make this known to your users?
This poses a good question, why would google now make it manadatory for you to explain to users that google are dropping cookies @ your site.
The answer in my opinion is google will be tracking user data, for that user data to be 'known' globaly across all domains.. (smartpricing v2) there will be paid per clicks happening @ other domains external to that of your site... learning what your visitor wants to get from the internet... wether or not he wants to buy new shoes one week, and a new car the next week... google will learn 'by dropping a session cookie' and them (the google bots) can work out where that user is, what he's doing, how he's surfing, what he wants to buy ...
Does anyone realise that? :]
google cookies = user spy = smartpricing v2
A detailed explaination of my theory:
1) User visits google.com and searches for Shoes./
2) Google sends a cookie to the client browser with a session id
3) google database updates with 'shoes' as a search indication the person is interested in buying 'shoes'
4) he visits a clothes dealer site and this has 'google ads' at the top... google cookie was sent from the browser to the database and the database came back 'shoes'.
5) Ads for 'shoes' now display at 'clothes + shoes website'
6) User clicks 'shoes' ad because Google knows he wanted shoes really.
7) User purchases pink shoes and walks down the street tapping his feet.
8) Advertiser =Sale, Google=Win, Publisher=Win
The bad side to this is that they could also be tracking that if a user clicked domain1.com at somesite.com and then visited youriste.com the advertisement for domain1.com may of not converted well so they decided to decrease the COST PER CLICK of the advertiser, decreasing the payout.
So this can be for and against publishers, depending on the user data google collects and the cookies stored by google ads / google services / etc.
| 1:50 pm on Feb 26, 2008 (gmt 0)|
I have had the pleasure of millions of unique visitors that have been to my sites in the last few years. My Privacy/ToS page (which is linked to from every single page on the sites) has been visited a grand total of 1,500 times, and most of those were probably bots of some type.
I'd guess that I could put "My name is Rumpelstiltskin and you owe me your first born if you use this site" and not lose a dollar a year in AdSense revenue. Not that I would put in such a clause. ;)
I just need someone, preferably AdSense, to tell me exactly what language would satisfy this requirement since I have no control over the cookies or beacons and don't know under what circumstances they would be employed. Or if they just want "Ads appearing on this site may employ cookies or web beacons."
It would be nice to tag on something like "See google.com/privacy for more information" since this is their requirement.
I hate to say it, but this does seem to have been poorly done.
[edited by: RonS at 2:06 pm (utc) on Feb. 26, 2008]
| This 225 message thread spans 8 pages: 225 (  2 3 4 5 6 7 8 ) > > |