News · 2026-10-24

Google adds an ad-personalization exception for connected Gmail, Drive, and Photos data

Google changed its privacy policy effective October 16 to allow an exception to its restriction on using Gmail, Drive, and Photos content for personalized advertising. The exception applies when users choose to make data from those services available to other Google services that support personalized ads. It makes connection choices more consequential without establishing that Google sends everyone’s private messages or photographs to advertisers.

Key facts

• Google’s official archive comparison dates the policy change to October 16, 2026.
• The exception concerns three named services: Gmail, Drive, and Google Photos.
• Gemini and Search expose separate controls for connected content and personalization.
• Primary source: Google’s October 1–16 policy comparison.

The consequential wording is the new condition. Google’s policy excludes private-service content from personalized advertising “unless you choose to make data from these services available” to services that support personalized ads. The rest of the clause identifies those receiving services. Read with the policy’s discussion of connected services, this establishes a possible route from private content to personalization elsewhere. It is not an assertion that every connected item is automatically used for every ad.

Consider an assistant that learns from your travel email that you are planning a trip. That information might improve a recommendation. The policy question is whether the service receiving the information also personalizes advertising. This example illustrates the permission structure; it is not a verified account of a particular campaign or a documented instance of advertiser access. The current Google Privacy Policy remains the authoritative description of the company’s stated boundaries.

Those boundaries include Google's statement that it does not share personally identifying information such as a name or email address with advertisers unless the user asks it to. It also says personalized ads are not based on sensitive categories such as health, race, religion, or sexual orientation. These qualifications matter because a broad headline about selling everyone’s inbox would collapse several different activities: making content accessible to another service, deriving an inference from it, personalizing an experience, and handing the underlying content to an advertiser.

The practical settings are not one universal switch. Google’s Gemini Help page lists connectable sources including Workspace apps, Photos in supported countries, Search services, and YouTube. Users can connect available apps together, select them individually, or decline. The documented route is Settings & help, then Personal Intelligence, then Connected Apps. Google also says that removing remembered information can require both disconnecting an app and deleting chats containing that information.

Search’s help page describes a separate Personalized Recommendations control. Consenting to content-app connections permits access across Search services, a group that includes more than the familiar search-results page: Google lists services such as Maps, Shopping, Discover, News, Flights, Hotels, and Translate. A user assessing data access therefore needs to check both the assistant connection and the receiving service’s scope.

Geographic distinctions complicate a simple Europe-versus-America story. Google’s Gemini documentation says Personal Intelligence is unavailable in the European Economic Area, the United Kingdom, and Switzerland, among other restrictions. That does not mean every form of cross-service data use is disabled there. Google’s help on linked services describes user choices for specified services while listing others as linked by default in the European Economic Area except Germany. Feature availability and broader service-linking rules are separate questions.

The strongest case for these connections is straightforward: an assistant that can use the material a person deliberately shares can produce more useful, less repetitive answers. That is a real functional benefit. The strongest criticism is that permission to improve an assistant can become difficult to distinguish from permission to personalize an advertising-supported ecosystem. Even a formally described choice can be hard to understand when controls, deletion steps, and service groups differ.

The Hacker News discussion establishes that the policy change drew attention; its vote count is a changing snapshot, not evidence of a public consensus. The useful evidentiary anchor is the official before-and-after wording. There is no need to infer a hidden universal data transfer to explain why the change matters.

For users, the concrete implication is to review which services receive connected information and which old conversations retain it. For organizations, the analogous question is whether an assistant’s access permission also authorizes downstream uses under the governing account terms. The site’s agent-memory lesson explains why deleting an original document and removing information already retained in another context are different operations. The remaining uncertainty is how this policy permission is implemented in particular features; the policy alone does not measure actual targeting behavior.

Primary source, verified: read the paper →

Ground Truth. (2026, October 24). Google adds an ad-personalization exception for connected Gmail, Drive, and Photos data. Ground Truth. https://groundtruth.day/news/google-connected-apps-ad-personalization-policy-exception.html

@misc{groundtruth:google-connected-apps-ad-personalization-policy-exception,
  title  = {Google adds an ad-personalization exception for connected Gmail, Drive, and Photos data},
  author = {{Ground Truth}},
  year   = {2026},
  month  = {oct},
  url    = {https://groundtruth.day/news/google-connected-apps-ad-personalization-policy-exception.html}
}

Topics: google · privacy · personalization · gemini · data-governance