Google’s connected-app privacy change makes the permission boundary matter

Connecting Gmail to a more helpful search assistant also changes where information from an email can travel. Google's current privacy policy allows content that a user makes available to another Google service to fall under that service's personalization rules, including advertising. The practical decision is therefore bigger than whether an assistant can find a booking confirmation.

The policy's advertising section retains restrictions on sensitive categories and on giving advertisers personally identifying information without permission. It also makes an exception to its exclusion of Gmail, Drive and Photos content when users choose to make that content available to services supporting personalized ads. That conditional wording matters: this is not an announcement that every inbox is automatically an advertising database.

The important boundary is between services

Consider a hypothetical request for restaurants near a booked hotel. An assistant needs the destination and dates to produce a useful answer; it does not need the user to copy those details manually if the relevant app is connected. The convenience comes from moving information out of one context and into another. That movement deserves attention even when both products carry the same company name.

Google's connected-app documentation says Search may use summaries, excerpts and inferences from connected content to personalize responses, and that the same information may inform ads. It says advertisers do not receive access to the inbox or photo library. Those statements can both be true: an advertisement can be selected using a derived preference without its buyer receiving the original email.

That is a more useful distinction than a binary argument about whether Google is “selling emails.” What changes the experience is the use of information, not simply whether a copy crosses an advertiser's desk. A travel preference inferred while answering a question can be commercially valuable even after names and reservation numbers are removed.

Disconnecting is not the same as deleting history

The support page also distinguishes future app access from existing Search Services History. Disconnecting an app does not erase that history. Google says some processed content can be used for model improvement, including summaries that may contain an entire short email; human review is also described. Advertising, history retention and model improvement therefore need separate consideration.

The privacy policy's controls section points to activity controls and My Ad Center. A sensible review starts with the actual connected apps, then the relevant history and advertising settings. Changing one setting should not be treated as proof that the other two changed with it. This is an account-level issue that a browser extension alone cannot resolve; our look at Privacy Badger concerns a different layer of tracking protection.

Availability adds another complication. The connected-app help page lists supported countries and languages separately, and individual connections have narrower restrictions. A language being supported does not establish that every country using it has the feature. Nor should Search's instructions be assumed to describe every Gemini configuration.

Judge the bargain at the point of connection

There is real value in an assistant that can answer a specific question without another round of copying, pasting and searching. The corresponding cost is that a private document may become context for a service with broader uses. Neither the usefulness nor the cost disappears because the permission screen is short.

The clearest choice is to connect the smallest set of apps that supplies a benefit you actually want, and examine the receiving service's rules before doing so. The relevant question is not just “Can Google read this booking?” It is whether the help obtained from that booking is worth the additional purposes for which its information may be used.