Google Chrome privacy worse than you think

The difference between other vendors here is that you can just remove that feature from the source and distribute it to people who care. It is BSD licensed after all.

I would assume this also happens every time I search on Google with ANY browser, if I also happen to be logged into GMail from the same computer at that time. The auto-complete there, I imagine, works the same way as it does in Chrome.<p>Not going to let it keep me from using either one, though obviously (this is the... 4th? OMG Chrome security! post on YC in 2 days) it's going to be a hot button issue for awhile.

I often use Google instead of typing in a URL because it requires less typing anyway, so this changes nothing for me.

Just don't log into google and remove cookies each time you restart the browser (I guess you can configure this, I don't have windows, so I couldn't try). If you have a dynamic IP you should be quite safe. But I'm not an expert at all.

This is a repost from the same topic as this: <a href="http://news.ycombinator.com/item?id=293947" rel="nofollow">http://news.ycombinator.com/item?id=293947</a><p>Perhaps the dumbest thing of all is bloggers don't actually read up before posting blogs like this particular one. One of the developers debunked the idea, he listed when the browser communicates with Google ( here: <a href="http://www.mattcutts.com/blog/google-chrome-communication/" rel="nofollow">http://www.mattcutts.com/blog/google-chrome-communication/</a> ), and he insisted that they hold no rights in a public blog post that can be cited by any two-bit lawyer from the way-back-machine. Scandalous of them, huh?

meh. I suppose if this level of hyper-privacy is required by the user, you shouldn't be using any google product, or MS product, or Apple product.<p>Me, I couldn't care less if google knows that I visited awsomenekkidpics.com or whatever.

Blogga please.