Is Grok Bot safe? Permissions, approvals and your data
Grok Bot has some of the clearest published security docs of any consumer agent, and its defaults are cautious. The risk sits in cleanup: all your Bots share one persistent computer, and deleting a Bot does not wipe its files or signed-in sessions.
Checked October 20, 2026. We summarise what xAI says and flag what it doesn't say. We don't speculate.
The consent form
Five things to know before you connect your accounts. Each line is from xAI's own pages unless it says otherwise.
- Where it runs
- On Cursor-hosted cloud computers, currently in the United States. Each user's work is isolated from other users, but all of one user's Bots share one persistent computer.
- What it can reach
- Bots start with no access and act as the signed-in member; connector tokens stay on Cursor's backend, not on the computer. Local-computer access is a separate setting (ask every time, always allow, or never).
- When it stops to ask you
- Approval prompts offer allow once, always allow, or deny. An 'Auto Review' model screens risky actions first. For logins, 2FA and payments the Bot hands the computer to you instead of typing.
- What happens to your data
- With Privacy Mode on, customer data is not used for training. Under the DPA, data is deleted or returned within 30 days after the service ends. Enterprise action recordings are kept 90 days. Idle computers hibernate, which is not deletion.
- How to cut it off
- Deleting a Bot does not wipe the computer's files or browser sessions. xAI says to sign out of sites on the computer, uninstall plugins and revoke them at the source service, and remove sensitive files; admins remove members and revoke sessions in their identity provider.
How to use it carefully
Bots run only on Cursor-hosted cloud computers in the US, isolated per user but not per Bot. A Bot begins with no access and acts as you, the signed-in member, while connector tokens stay on Cursor's backend. Access to your own machine is a separate switch: ask every time, always allow, or never. Approval prompts offer allow once, always allow or deny, and an Auto Review model screens risky actions first. For logins, 2FA and payments the Bot gives you the controls. With Privacy Mode on, your data is not used for training, and under the DPA it is deleted or returned within 30 days of the service ending. Idle computers hibernate, which is not deletion. To revoke, sign out of sites on the computer, uninstall plugins and revoke them at the source service, and remove sensitive files.
Sources
- xAI's security docs say Bots run only on Cursor-hosted cloud computers located in the US, with per-user isolation and no on-premises option. docs.x.ai official, read Oct 20, 2026
- Bots have no identity of their own and act as the signed-in member; for login, 2FA and payment steps they hand the computer back to the person. docs.x.ai official, read Oct 20, 2026
- Approval prompts let members allow once, always allow, or deny, and an independent Auto Review model screens risky actions before they run. docs.x.ai official, read Oct 20, 2026
- Deleting a Bot leaves the computer's files and browser sessions in place; xAI advises signing out of sites and revoking plugins at the source service. docs.x.ai official, read Oct 20, 2026
- With Privacy Mode on, data is not used for training; under the DPA data is deleted or returned within 30 days of the service ending, and enterprise action recordings are kept 90 days. docs.x.ai official, read Oct 20, 2026
- xAI's Bot page says all of a user's Bots share one persistent computer, so isolation is per user rather than per Bot. x.ai official, read Oct 20, 2026
- Hosted computers send traffic from shared static egress IP ranges used by all Grok Bot customers; dedicated IPs are not offered. docs.x.ai official, read Oct 20, 2026
- A third-party bot directory reports a 'GrokAgent' user-agent token with signed requests, sourced to Cloudflare's registry; xAI does not publish this string. aicrawlercheck.com third-party, read Oct 20, 2026