What Personal Intelligence Actually Accesses
The scope is broad by design: the point is that Gemini knows what you know, because it can see what you have.
Google's announcement lists Gmail, Google Photos, Google Drive, Google Calendar, and other Google services as data sources Personal Intelligence can draw from. When you ask a question, Gemini searches these services on your behalf and uses what it finds to compose an answer. The search is real-time rather than pre-indexed: it queries your actual inbox at the moment you ask.
The integration with Gemini Gems, Google's custom persona system, means memories can be scoped to specific workflows. You could have one Gem that knows about your work calendar and another that knows about your photo library, rather than everything being pooled. Whether users actually configure this, or just accept the default, is an empirical question.
The Photos integration has a specific limitation: users in Illinois and Texas cannot enable it, because facial recognition features run afoul of local biometric privacy laws. This is a reminder that what the feature can do varies by jurisdiction and may change as laws catch up.
What Google Says About Privacy
Google's official position has several parts. First, the feature is opt-in: you have to enable it before Gemini can see your services. Second, Gemini does not train directly on your inbox content: it queries your data to answer questions but does not feed your emails into the model's weights. Third, you can use temporary chats that do not contribute to your memory, and you can review which apps are connected.
Google also says it aims to avoid making proactive assumptions about sensitive data like health information. The phrasing is careful: it aims to avoid, not it cannot. This leaves room for the system to infer things from your data that you might not expect it to know, while claiming it is not actively seeking them.
The privacy controls exist and they work. Turning off Keep Activity disables Personal Intelligence entirely. You can limit what Gemini accesses per conversation. These are real affordances, and Google deserves credit for building them. The debate is about what the defaults will be once the feature is mature, and whether the architecture allows things the policy currently forbids.
What the Critics Worry About
The concerns cluster around three themes: wording, defaults, and attack surface.
The wording sounds better than it is
One privacy researcher argues that Google's statements sound reassuring but do not actually answer the fundamental questions about data handling architecture. Saying Gemini does not train directly on your inbox is not the same as saying your inbox content is never processed by Google's models or stored in logs. The gap between what a policy says and what a system does is often where the problems live.
Opt-in may not last
Android Police expects the setting to become opt-out once Google rolls out Personal Intelligence to the free Gemini tier. This is speculation, not fact, but it matches the pattern of how features often evolve: start with privacy-conscious defaults to get past early scrutiny, then relax them once the feature is established. The concern is not that Google has done this yet, but that the architecture would allow it.
Prompt injection is now prompt extraction
A security-focused review asks what happens if an attacker can craft a prompt that causes Gemini to search your inbox and include sensitive content in its response. This is the prompt injection problem, extended to a system that has real access to real data. If Gemini can read your email, and Gemini can be tricked, then your email can be read by whoever does the tricking.
The same review asks what happens when an employee enables Personal Intelligence on a Workspace account. Does the employer now have a vector for reading employee communications? Does the employee have a vector for exfiltrating company data? The feature creates new adjacencies that did not exist before, and those adjacencies are where security problems live.
The Personal Archive Problem
Zoom out from the privacy debate and a different issue appears. Personal Intelligence is useful precisely because your email archive is a genuine record of your life. Flight confirmations, receipts, conversations, decisions: it is all there, searchable, stretching back years. That is why letting an AI read it is valuable.
But it also means your personal archive is now context for a system you do not control. The AI interprets what it finds. It synthesizes. It answers questions in ways that compress and lose the original. If you come to rely on Gemini to answer questions about your own life, you may stop going to the source material. The AI becomes the interface, and the archive becomes something you access through the AI rather than directly.
This is the familiar local-versus-cloud tradeoff, restated. Your Gmail is already hosted. You already depend on Google to keep it available. What Personal Intelligence adds is interpretation: not just storage and retrieval, but a layer that decides what your archive means. And that layer is not portable, not inspectable, and not under your control.
| Search your inbox | Ask Gemini | |
|---|---|---|
| What you see | The emails themselves | A summary the AI composed |
| What you can verify | Everything | Whatever it cites |
| What gets recorded | Your search query | Your prompt plus the response |
| Who interprets | You | The model |
| Portable to another service | Yes, via export | No, the interpretation is proprietary |
How to Think About Enabling It
The decision is not all-or-nothing. Personal Intelligence is genuinely useful for some queries and genuinely risky for others. The question is whether you can maintain the distinction.
Convenience queries are low stakes. When did my flight land? What is the confirmation number for the hotel? These are lookups, and having an AI do the looking is faster than searching yourself. The risk of misinterpretation is low because the answer is verifiable and factual.
Judgment queries are higher stakes. What did I agree to in that email thread? What did the contract say about the termination clause? Here the AI is not just retrieving, it is interpreting, and the interpretation might be wrong in ways you do not notice. The risk scales with how much you trust the answer without checking.
The practical approach is: enable it if you want, but do not let it replace direct access. When the answer matters, go to the source. When the AI is wrong, know how to find out. And keep your own copy of anything you cannot afford to lose, because Google's policies can change and your account is not guaranteed.
A second brain on your own device keeps the archive under your roof, even when you let AI help you search it. Local-first alternative →
What to Do Before Enabling
- Understand what you are connecting. Personal Intelligence can access Gmail, Photos, Drive, and Calendar. Know what is in those services before you let an AI read them.
- Review the Activity controls. If you turn off Keep Activity, Personal Intelligence stops working. If you leave it on, your prompts and Gemini's responses are logged. Decide which tradeoff you prefer.
- Consider the work/personal boundary. If your Google account mixes work and personal email, enabling Personal Intelligence exposes both. Use separate accounts if the distinction matters.
- Know how to export. Your Gmail is exportable via Google Takeout. Your Gemini memory is not. The asymmetry is real, and it matters if you ever want to leave.
- Test with low-stakes queries first. Before you ask Gemini about anything sensitive, ask it about something you can verify. See what it gets right and wrong. Calibrate your trust.