Fixes / Access & platform
Grok Bot blocked by Legacy Privacy Mode
Grok Bot requires cloud data storage and won't start on Cursor accounts using Legacy Privacy Mode. What the setting change means for your code and data before you flip it.
Short answerGrok Bot requires cloud data storage. Accounts on Legacy Privacy Mode must switch to a supported Cursor data setting. Before you do, understand that this changes what Cursor retains for your account, not just for Grok Bot; review with whoever owns your data policy.
Why
Bots keep state: memory, files, run records. That lives in the cloud. Legacy Privacy Mode was designed around not retaining data, so the two are incompatible.
Before you change it
The setting is account-wide. If your team chose Legacy Privacy Mode because of client code confidentiality or a compliance commitment, switching it for Grok Bot changes that commitment. Options:
- Use a separate Cursor account (or Teams seat) for Grok Bot with the supported setting, and keep the privacy-mode account for coding.
- Confirm what the supported setting retains and for how long, in Cursor's current privacy documentation, and get sign-off.
Then
Open Cursor privacy settings, select the supported data setting, restart Grok Bot.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.