Google links Gmail and Photos access to ad targeting in new privacy terms

For millions of people in the Mid-Atlantic and beyond, the way they interact with their digital photos and emails may now have a direct impact on the advertisements they see. If you have connected your personal files to Google's artificial intelligence tools for better search results, a recent policy shift suggests that this convenience comes with a new cost. Your private data is now explicitly eligible to be used for targeting ads, a change that was not clearly stated in previous versions of the company's privacy rules.

The core of the issue lies in a subtle but significant addition to Google's privacy policy, which was identified by the tech publication Android Authority. Previously, the company stated that it would not use data from Drive, Gmail, or Google Photos for personalized advertising. However, as of October 16, 2026, an exception has been added. The new language clarifies that Google may use this data if you choose to make it available to other Google services that support personalized ads. This effectively ties the benefit of smarter AI responses to the potential for more targeted marketing.

This change specifically affects users who have enabled the Personal Intelligence feature. By connecting their Drive, Gmail, or Photos to AI Mode and other search tools, users allowed these systems to provide more tailored recommendations. Under the new terms, that same access now opens the door for advertisers to target users based on the content within those personal files. The policy states that if you allow search services to access data from other apps, those services may process that information to personalize content, including the ads you see.

Despite this broadening of data usage, Google maintains that it is not handing over your raw files. Advertisers do not receive direct access to your Drive, Gmail, or Photos information. Furthermore, personally identifying details such as your name or email address remain protected. The company also insists that it will not show you ads based on sensitive categories, such as race, sexual orientation, religion, or health, ensuring that the most private aspects of your data are not used for commercial targeting.

The policy provides a specific example to illustrate how this works in practice. If you search for mountain bikes, you might see ads for sports equipment on YouTube. This connection is made possible because the search engine is now permitted to reference data from other services you have linked. It is a shift from a model where these data silos were separate to one where they are integrated for the purpose of personalization, with ads being the primary vehicle for that personalization.

For those who feel uneasy about this new linkage, there are ways to regain control. Users can choose which specific apps they want to disconnect from the search Personal Intelligence features. Alternatively, you can disable Personalized Recommendations entirely through the Search Services Personalization settings page. This requires a proactive step on the part of the user, as the default setting for those who have already enabled the AI features appears to be that data sharing is permitted for ad personalization.

The update raises questions about the trade-off between utility and privacy in the era of large language models. While knowing your preferences allows for more helpful search results, the new terms make it clear that this knowledge is not just for your benefit. It is also for the benefit of the advertising ecosystem. Users are left to decide if the improved accuracy of their AI tools is worth the increased visibility of their personal history to advertisers.

As of now, there is no indication that Google will roll back this change. The policy has been in effect since mid-October 2026. For readers in the region, the key takeaway is to check your settings if you rely on Google's AI features. If you prefer to keep your email and photo library separate from your ad profile, you must now actively manage those connections rather than assuming they are protected by default.