Google AI privacy: what the available documents do—and do not—say

The documentation reviewed does not support the claim that Google has recently announced a general change in how data is handled across its artificial intelligence services. There are announcements about Gemini products and features, but an announcement about capabilities does not, by itself, show that privacy terms have changed. The useful question here is therefore not whether to declare a new rule, but which sources to consult before sharing information.

The distinction matters. A policy describes commitments and practices in general terms; help documentation may explain a service’s features and controls; a product post presents something new. These documents are not interchangeable. Based on what could be verified, reporting a privacy change as news would go further than the sources justify. This article is therefore a reading guide, not a warning about a newly announced change. It sets out what each kind of source can establish, and where its limits lie, so readers do not mistake a product announcement for a statement about data practices.

Google maintains a page titled Privacy Policy. It is a starting point for understanding the general privacy information the company publishes, but its existence is not enough to answer a specific question about an AI feature. For that, check whether the product has its own documentation, whether the feature is enabled, and which version of the terms applies to the user’s account and market. A general policy should not be treated as a comprehensive fact sheet for every service. The name of a service or feature alone does not fill in details that its documentation has not confirmed.

The research also identifies a Gemini Apps Privacy Hub in Google Help. Its title confirms that there is a resource specifically for that group of apps; the material available here does not, by itself, allow us to reconstruct every condition, retention period or control it explains. The prudent approach is to open the page and review its current sections, rather than attribute to the hub details that could not be confirmed in the text retrieved. If an answer depends on a particular setting, check it directly in the account. This avoids treating a general description as proof of what a user can actually do in a given service.

On March 13, 2025, Google published a post about personalising Gemini with Google apps. The announcement establishes that the company presented a feature with that approach, but its available title and metadata are not enough to establish what information is used, how long it is retained, or which options are available to each user. Those answers require specific, current documentation; they cannot be inferred from a feature’s name. A product post can identify what was announced without supplying all the privacy details needed to assess its use.

There is also a post dated April 14, 2026, titled “Gemini introduces Personal Intelligence.” Its date and subject identify it as a product announcement, not as independent evidence of a review of the privacy policy. The same caution applies to Google I/O announcements in May 2026 about Gemini and Search: publicly describing a new capability does not, on its own, determine how all related data is managed. A new feature and a new rule are different questions. To establish the latter, consult the relevant policy or service documentation rather than drawing a conclusion from an announcement’s title or timing.

Before using a generative tool, identify the exact service and feature you intend to use. Then consult its help centre and the terms linked there. Look for explicit answers about what data is processed, for what purpose, which controls are available, and whether terms vary by account type, age or region. If there is no clear answer, do not fill the gaps with assumptions based on a policy for another service. A careful check means matching the question to the product and account at hand, rather than relying on a broad description that may not address the feature.

As a practical check, you can follow this list:

• Identify the product and account: do not assume that the rules for a personal app are identical to those for a product for organisations or educational institutions.
• Find the service documentation: start with the Gemini Apps Privacy Hub if your question concerns those apps; use the general policy as context, not as a substitute.
• Review the controls available in your account: Google’s Privacy Checkup page is an entry point for reviewing settings, but the link alone does not prove which specific options are available to each user.
• Limit the information you share: if the documentation does not give you enough to assess a risk, avoid entering sensitive or identifying data until you have clarified the issue.

This list is a method for reading the documentation, not a claim that all these controls exist in every product. Availability may depend on the service and account, so it must be confirmed in the current documentation. A control mentioned in a general setting or help page should not be assumed to apply to every feature. Check the relevant account and service rather than generalising from one experience.

The identified sources support a limited conclusion: Google has a general privacy policy, a privacy hub dedicated to Gemini apps, and feature announcements with verifiable dates. They do not, however, suffice to describe precisely the complete data-handling lifecycle for every type of data in every product. Nor do they, by themselves, establish a recent, cross-cutting change to the rules. Not finding that evidence in the material reviewed does not prove it is absent from other documentation or regions; it means it would be incorrect to claim it without verification. This distinction keeps the conclusion within the limits of the sources.

The responsible choice for someone using these tools is to consult the product-specific document and check the controls in their account before sharing sensitive information. If the question is legal—for example, about third-party data, professional obligations or rights that apply in a country—a corporate webpage is not a substitute for appropriate advice or information from the competent authority. This guide does not promise a universal answer because the available evidence does not support generalising across services, features, account types and jurisdictions. The right source may differ with the question, and uncertainty should be acknowledged rather than filled with an unsupported assumption.