Gemini can now use your email, calendar and photos while you drive

Google [announced on October 20](https://blog.google/products‑and‑platforms/platforms/android/android‑auto‑cars‑with‑google‑built‑in‑gemini‑personal‑intelligence/) that Gemini is available globally on Android Auto and that Personal Intelligence is beginning to roll out there. The personalization feature is planned for cars with Google built‑in in the coming months. With permission, the assistant can connect context from Gmail, Google Calendar, Google Photos, Google Maps, YouTube and Search. Google’s examples include finding a flight gate and current status, navigating to an appointment whose address is in a calendar entry, or locating a place shown in a recent photo. The practical change is cross‑app reasoning through voice. Drivers may need fewer screen interactions, but they are also giving an in‑car assistant access to records that can reveal travel, health, relationships and routines.

Personal Intelligence is opt‑in and currently rolling out to eligible personal Google accounts for users aged 18 and older. Google’s footnote excludes Workspace business, enterprise and education accounts, as well as users in the European Economic Area, Switzerland, the United Kingdom and Nigeria. That distinction matters because the headline availability of Gemini on Android Auto is broader than the availability of personalized answers. A driver may have the assistant without the connected‑app feature, and cars with Google built‑in have a later, unspecified rollout. Before relying on it, check the exact Google account active in the vehicle, the account’s eligibility, the connected apps and whether a particular vehicle uses Android Auto or its own built‑in Google system.

Google says apps are not connected until the user turns the feature on and that it can be disabled in Gemini settings. For cars with Google built‑in, the company says personal responses are shared only when the user is in the car with the connected phone. Those are useful product controls, but they do not resolve every social boundary. A car is often shared with partners, children, coworkers, rental users or passengers who can hear responses. A personalized answer can expose a message subject, appointment, route or photo‑derived location without showing a screen. Drivers should use an account and connection pattern that matches who has access to the vehicle and who may hear it. Voice assistants can also misunderstand requests or retrieve the wrong record. Confirm consequential details such as flight changes, addresses and medical appointments through the underlying app when an error would matter.

Start by reviewing which Google apps are connected and removing any that do not serve a clear driving task. Test ordinary queries while parked, including ambiguous names, old calendar items and multiple saved locations. Confirm that disabling Personal Intelligence returns the experience to non‑personalized navigation, media, calls and general questions. Households should decide whose account is active, when the phone connection is required and which answers should never be spoken aloud. Employers should not assume the consumer feature is available for managed Workspace identities. Vehicle owners should also treat the later built‑in rollout as pending until their manufacturer or system shows the setting. This is a meaningful consumer expansion because it brings connected personal context into an everyday hands‑free environment. Its usefulness will depend on accurate retrieval and deliberate permissions, not simply the presence of Gemini in the dashboard. *Figure by OpenTools Team; no third‑party expressive material used. It maps connected data, spoken requests and the checks that protect a shared in‑car setting.*