Sharing that Google identity with other websites when that identity is logged into Google is a less obvious one.
Analytics, cookies, personalized search results, etc. take it to Google's very core.
Driving around collecting WiFi data, storing WiFi passwords, reading documents via Docs and email via Gmail, and just plain crawling the web don't embody any common language notion of privacy.
Instead security stands in for it. Two factor authentication for a Google account is an example. It keeps a person's account secure but does not enhance privacy because Google will still share and slice and analyze everything that can possibly be associated with that account.
This sounds like somebody being really clever and whipping up a fancy feature, but forgetting to finish it with proper meeting requests and a freaking confirmation box and whatnot.
The idea itself is good - check for email addresses in meeting information and tying those to a Google account as invites. The problem is that the user isn't asked.
This is why it's not a privacy leak. "Privacy" has no meaning when the context is Google. It only has meaning outside their operations.
What does this mean?
Google doesn't have a category labeled "private" information". It never has and creating one is not planned. Privacy is not amenable to computer science. It is a social concept not a technical one. The closest technical concern is security. It scales and so that is where Google devotes resources.
As far as Google is concerned: All your bit are belong to us.