- Trains on your data by default
- Unknown
Official Grok Bot pages exist, including Grok Bot Terms, product, FAQ, and security docs on x.ai. Those security docs say Grok Bot uses Cursor authentication and account data settings, that training opt-out follows Cursor Privacy Mode, and that with Privacy Mode enabled, customer data is not used for training. Cursor's data-use page, last updated September 3, 2026, says that if Privacy Mode is on, Cursor will not train on customer data and model providers are under zero-data-retention agreements, with a carve-out if abuse detectors fire; if Privacy Mode is off, Cursor may use and store prompts and other data to train models. Cursor's privacy help page, however, answers whether Privacy Mode prevents xAI from training on Grok Bot data by saying Grok Bot runs on a separate product surface with its own data flows, and it does not give a direct yes. Privacy Mode is on by default for Teams and Enterprise, and those admins can enforce it. The pages we read do not state the default for a new personal account. Grok Bot does not support Legacy Privacy Mode, because it requires cloud storage. Grok Bot also picks the model for each task, which can be a first-party SpaceXSI model or a third-party model from the sub-processor list, and a team's Cursor model allowlist does not apply.
- How to opt out
- Steps
Grok Bot docs say training opt-out follows the applicable Cursor account and privacy settings, including during the Grok Bot access flow when required. In the Cursor editor, Privacy Mode is under Settings, then General. For teams, Cursor's help page says Privacy Mode is enabled by default and admins can enforce it organization-wide so members cannot turn it off. Turning on Legacy Privacy Mode is not a path: Grok Bot requires data storage and is blocked on that setting. Because Cursor's help center does not clearly confirm that Privacy Mode stops training on Grok Bot data, treat the Grok Bot security docs and the Cursor help page together, and do not assume the editor setting covers every Grok Bot data flow until your contract says so.
- Data retention
- What they keep
Not published as one period for ordinary Grok Bot files and chats. The Grok Bot Terms say Grok Bot may retain customer data, files, browser sessions, credentials, memory, and routines in a persistent cloud environment, and that deleting a Bot may not delete shared files, sessions, credentials, or routines. Cursor's privacy help page says storage location, retention, and deletion for Grok Bot computer files depend on the account type and how the files were created, and it points personal-data deletion requests to support. The Grok Bot FAQ says that deleting the Cursor account, which is also the Grok Bot account, removes that data within 30 days. Grok Bot security docs say deletion under the Data Processing Agreement is within 30 days of written direction after the service ends, and that this DPA applies to Teams and Enterprise contracts, not to individual plans. Enterprise admins can set optional auto-deletion windows of 30 to 365 days for bots, computers, and messages. If Action Recording is turned on, those recorded events are kept for 90 days.
- BAA / HIPAA
- Unknown
The Grok Bot legal and security pages we read do not offer a Grok Bot business associate agreement. Cursor's HIPAA BAA page says a BAA is available only with an Enterprise agreement, and that a signed BAA is required before submitting protected health information. The public Eligible Services list on that page names the desktop IDE, Cloud Agents, Cursor for iOS, the CLI, Tab, BugBot, and Automations. Grok Bot is not on that published list. The same page says a BAA does not automatically cover every product or third-party integration, and that the HIPAA Guide in the Trust Center has the latest eligible services. Individual Cursor plans are not covered by Cursor's DPA; those plans follow the Privacy Policy.
- Certifications
- 2 listed
- ISO/IEC 27001
- ISO/IEC 42001
- Enterprise and admin controls
- Controls
Members sign in with their Cursor account, so existing Cursor SSO can apply, and SCIM is Enterprise only. Grok Bot security docs say Anysphere, the company behind Cursor, holds ISO/IEC 27001 and ISO/IEC 42001 certifications issued by Schellman, and that Grok Bot is included in the current ISO scope, with reports at trust.cursor.com. They also say hosted computers run in the United States, with an optional Cursor US-only residency program, and that on-premises or customer-hosted deployment is not offered. Many of the stronger admin controls are Enterprise only, including the org-wide enable switch, Network Controls, inference hooks, enforced Auto Review and team rules, audit logs, Action Recording, OpenTelemetry export, Team Setup Scripts, computer management, and custom retention periods. Self-serve Teams get Grok Bot by default but do not see those Enterprise-only settings, and teams without a network policy default to allow-all. Auto Review is on by default for individuals, but a member can turn it off unless an Enterprise admin requires it. All Bots for one user share one cloud computer, so separate Bots are not a security boundary. Enterprise admins can cap local-computer execution, disable Cloud Agent delegation, and restrict connectors. Grok Bot Terms also cover agentic actions such as sending communications, running code, meeting features, and phone calls, and they put responsibility for those actions on the customer.