Grok Mobile Gets Phone Calendar and Contacts Access: What Is Verified

A headline circulating on October 22 says Grok now links to calendar and contacts on iOS and Android. The product naming is muddled. The underlying report, from AlphaSignal, describes the Grok mobile app reaching your phone's Calendar, Reminders and Contacts, and cites a post from the Grok bot account on X. Grok Bot is the separate agent we have covered in posts like Grok Bot's own email address, so it is unclear which product the feature belongs to. This post separates what is reported from what xAI's own pages confirm.

TL;DR: claimed versus verified

What the primary pages actually say

Two xAI pages are relevant. The Connectors announcement of May 6, 2026 launched cloud integrations on web, iOS and Android, including Outlook ("create calendar invites", triage inbox) and Google Workspace (Gmail, Drive, Docs, Sheets, Calendar), plus Bring Your Own MCP. Those work through OAuth sign-ins to your accounts, not through your phone's local data. We covered the Outlook side in our Grok Outlook connector post.

The Grok Bot for Mobile docs describe a different thing. They say the mobile app "connects to the same Bots, conversations, routines, connectors, and shared cloud computer as the desktop app" and that work continues in the cloud when the app is closed. Requirements are iOS 18 or later or Android 9 or later, with an eligible Cursor or SuperGrok plan. The page lists messaging, voice, photos, reviewing the computer and routines. It does not mention Calendar, Reminders or Contacts permissions.

So the phone-data feature, if it exists as described, is reported as part of the Grok mobile app, and the primary announcement appears to be a post on X that we could not retrieve. That is why this stays a "reported" item.

What the report says the feature does

According to AlphaSignal, the Grok mobile app can retrieve supported records and perform available actions once you grant permission:

• Calendar: find free time, create events, update appointments.
• Reminders: list overdue tasks, sort them, create reminders, mark items complete.
• Contacts: find people, prepare messages, add company or role context.

It also reports practical limits: sending iMessages or emails is not covered by the Contacts grant and needs a supported messaging action or a handoff to you; Grok cannot control arbitrary app interfaces; and teach-by-demonstration and some advanced desktop controls are unavailable on mobile, which matches the Grok Bot mobile docs.

Why the Grok Bot confusion matters

Two products with similar names make it easy to grant the wrong permission. Grok Bot is an always-on agent with a shared cloud computer and, per its docs, plan eligibility tied to Cursor or SuperGrok. The Grok app is the chatbot. Our comparisons of Claude Duet, OpenAI Dots, Meta Muse and Grok Bot show how crowded personal agents have become, and naming drift between app, bot and model is a recurring source of mistakes. If a story says "Grok Bot can now see your contacts", check which app and which settings screen it refers to before changing anything.

Local access versus cloud connectors

The two access paths differ in ways that affect your risk.

A key phrase in the report is that "on-device" describes only how Grok reaches system data. It does not tell you whether the contents are sent to xAI's servers for the model to read, which for a cloud-hosted model they must be in order to answer questions about them. Assume that anything the assistant can summarize has been transmitted for processing.

The questions xAI has not answered

AlphaSignal lists items it says xAI still needs to document, and we agree they are the ones that matter:

1. Exact read and write scopes for each data type.
2. Whether writes, such as creating or editing an event, require confirmation and can be undone.
3. How mixed personal and work accounts on one device are handled.
4. Retention, and whether this data is used for training.
5. Defenses against prompt injection hidden in calendar invitations, contact notes or reminder text.

The last point is not hypothetical. Calendar invites and shared reminders are text written by other people that an agent will read as input, which makes them an obvious channel for injected instructions. The risk pattern is the same as in other agent incidents we have tracked, such as the bank balance posted to Slack and the Apple Full Disk Access debate over agents.

What to do before you grant access

• Grant the narrowest option. If your OS offers add-only calendar access or selected contacts, pick that first and widen later.
• Check your plan and app version. The report says rollout is gradual and covers all plans, including free; if you do not see a prompt, you may not have it yet.
• Test with a dummy calendar. Ask for something harmless, such as finding free time next Tuesday, and watch what it asks to do.
• Read the permission page inside the app and compare it with your OS settings so you know where to revoke.
• Treat shared invites as untrusted. Do not ask an assistant to act on instructions inside an invite from someone you do not know.
• Add a guardrail if you build on agents. AgentBeam, the agent security platform from the explainx.ai team, stops agents before they take dangerous actions.

How this fits the larger pattern

Every major assistant is converging on the same move: from answering questions to holding your calendar and contacts. Meta's Muse reaching into Messages, OpenAI's Dots and Anthropic's Duet each bring their own permission trade-offs, which we compared in our proactive agents analysis. The benefit is real: scheduling, reminders and finding the right person are the daily jobs people want automated. The cost is that your most personal structured data becomes model input.

How to check it yourself in five minutes

You do not have to wait for xAI to settle this. A short test on your own device shows what is real.

1. Update the Grok app from the App Store or Google Play and note the version.
2. Open the app's settings and look for a permissions or connected-data page; the report says one exists.
3. Ask for something that needs a phone data store, such as "what is on my calendar tomorrow", and see whether the app triggers an OS permission prompt. If it instead asks you to connect Google or Outlook, you are being offered the cloud connector path, not phone access.
4. On iOS, open Settings, then Privacy and Security, then Calendars, Reminders or Contacts, and confirm Grok appears in the list. On Android, check the app's permission screen.
5. Revoke the permission and repeat the request. A correctly built integration should fail cleanly and say it lacks access.

If steps 3 and 4 do not behave as described, the feature has probably not reached your account yet, which matches the report's note about gradual rollout.

Why the details of the permission matter

Modern phone operating systems split permissions finely, and the report says Grok's access depends on the OS version. A calendar grant can mean add-only access, which lets an app write events without reading existing ones, or full access, which lets it read everything. A contacts grant can be limited to the contacts you pick. Picking the narrow option changes what an assistant can leak or be tricked into doing. For example, an assistant limited to adding events cannot be coaxed into summarizing a private meeting title, though it could still be manipulated into adding a misleading event.

The report also says sending iMessages or emails is not covered by the Contacts grant. That is a sensible boundary: knowing who someone is differs from messaging them on your behalf. It is also a boundary users tend to forget when a later update adds a messaging action, so re-check your permissions after major app updates.

What this means for people who build on Grok

The report says no third-party developer API or SDK for these phone data stores has been announced. For builders, that means this is a consumer feature, not a platform capability: you cannot call it from your own app. If you need the same effect, you would use the cloud route, with the Google Calendar or Outlook connectors and the Bring Your Own MCP option from the May launch, and take on the OAuth scopes and consent screens yourself. That route is documented, scoped and revocable at the provider, which is a stronger position than a local grant whose retention rules are not yet published.

What would settle this

Three things would turn a report into a verified feature: xAI's original post or release notes naming the feature and the apps affected, an update to the Grok docs describing scopes and retention, and independent hands-on tests showing the permission prompts and behavior. We will update this post when any of them appears.

Related reading

• Grok Bot gets its own email address
• Grok Outlook mail and calendar connectors
• Claude Duet vs OpenAI Dots vs Meta Muse vs Grok Bot
• Grok Bot bank balance and Slack permissions
• Apple Full Disk Access and AI agents
• Hark Pro vs Muse, Dots and Grok Bot

Details reflect sources available on October 23, 2026 and may change.