
Privacy Mode is the Cursor setting MSPs ask about first, and it is also the setting they most often misunderstand. People hear “privacy” and assume customer Microsoft 365 data will not be stored, will not leave Australia, or will never appear in a chat history. That is not what the documentation says.
Privacy Mode is about training and about how model providers retain prompts. It is not a promise that Grok Bot keeps nothing. Grok Bot needs cloud storage in order to work. If you cannot explain that difference to a customer, you are not ready to point a Bot at their tenant.
This post stays with what Cursor publishes. I will not describe my own account settings, or invent a click path that is not in the official docs. Where the docs leave a gap, I will say to check with Cursor. I covered the broader security picture, including the shared computer, in What MSPs should understand about Grok Bot security and customer Microsoft 365 data. This one is narrower: Privacy Mode itself, how to change it, and what that means if you use Grok Bot with customer data.
What Privacy Mode is, and what it is not
Cursor’s Data Use & Privacy Overview is the plain description. If you enable Privacy Mode in Cursor’s settings, customer data is not used for training by Cursor. Cursor says it maintains zero data retention (ZDR) agreements with model providers, and those providers will not store or train on your data. There is an exception you should not skip: subject to their policies, model providers, including Cursor, may run risk or abuse classifiers, and if a prompt or conversation triggers those detectors, data may be stored for investigation and later deleted under the provider’s retention policy.
If you turn Privacy Mode off, the same page says Cursor may use and store codebase data, prompts, editor actions, code snippets and other code data and actions to improve features and train models. Some inference providers may also temporarily access and store model inputs and outputs to improve inference performance, then delete that data after use.
That is the switch that matters for an MSP. With Privacy Mode on, the published commitment is no training, plus ZDR with providers, plus the classifier exception. With it off, prompts and related data may be used to improve and train.
The Grok Bot security page says Privacy Mode applies, that while a member is on a team the team’s privacy mode governs them, and that with Privacy Mode enabled, customer data is not used for training. The teams page adds that Cursor enforces this on its servers, and that when the setting cannot be verified, the system defaults to not training. The approvals, security and privacy help article says training opt-out follows the applicable Cursor account and privacy settings.
Cursor’s general privacy help article is a little more cautious on one point. It says Privacy Mode in the Cursor editor prevents your code from being used for training, and that Grok Bot runs on a separate product surface with its own data flows, then points you back to the data-use page and the sub-processor list. I am not going to pretend those two wordings are identical. For Grok Bot work, I treat the Grok Bot security and teams pages as the product-specific source, and I still tell customers to read the data-use page and, if they need a contractual assurance, to check with Cursor and look at the applicable Data Processing Agreement.
Privacy Mode does not mean “nothing is stored”. Grok Bot requires data storage. The security documentation is explicit about what persists. Each member’s computer keeps files, browser sessions and anything saved in the browser on a durable disk across sessions. Idle hibernation is not deletion. Deleting a Bot does not remove those shared files or sessions. Connector tokens stay on Cursor’s backend, not on the computer. Vault holds logins and, if you save them, payment cards, and it covers the whole account. Chats are part of the product; you come back to them. Cursor also says the production control plane is covered by daily encrypted backups. Under the Data Processing Agreement, data is deleted or returned within 30 days of written direction after the service ends. If you do not have a DPA, follow the Privacy Policy and ask Cursor how deletion works for your plan. To request deletion of Grok Bot computer files that contain personal data, Cursor’s privacy help says to contact support with your account email, the agent name and a description of the files.
Privacy Mode also does not move the computer out of the United States, and it does not replace least privilege, approvals or a cleanup habit. Those are separate controls.
Legacy Privacy Mode is a different setting
There are two privacy settings, and the names have been easy to mix up. Cursor’s documentation usually says Privacy Mode and Privacy Mode (Legacy), or Legacy Privacy Mode. In the week of 5 October 2026, Cursor’s web release notes said the privacy settings now read “Privacy Mode (no training)” and “Legacy (no storage)”. That naming is the clearest short explanation I have seen: one setting is about training, the other is about refusing cloud storage.
Grok Bot needs cloud storage, so Legacy Privacy Mode is not supported. The get started guide says that if your account is on Privacy Mode (Legacy), the app asks you to switch to Privacy Mode first. On a team, a team admin changes the team’s privacy setting. The teams documentation is blunt: move off Privacy Mode (Legacy), because that setting blocks Grok Bot entirely, and you are prompted to change it before enabling. Check the privacy setting in Team Settings.
If you are still on Legacy because you wanted no storage, understand the trade-off: that setting will not run Grok Bot. Current Privacy Mode is the no-training setting that still allows the storage Grok Bot needs. Cursor’s Privacy and Data Governance page describes it as the setting that keeps your code from being used for training, with ZDR guarantees for team members when it is enabled at the team level. Privacy Mode (Legacy) also forces Action Recording off. Action Recording is an Enterprise control, off by default, and is not a reason to stay on Legacy.
Who can set it, and how the plans differ
This is a Cursor account or team setting, not a per-Bot switch.
On an individual plan, Cursor’s Enterprise comparison describes Privacy Mode as a user choice. You should not assume it is on. Check it.
On a team, Cursor’s privacy help says Privacy Mode is enabled by default for all team members, and that it is on by default for Enterprise teams. Teams and Enterprise admins can enforce it organisation-wide so members cannot disable it. Cursor’s enterprise comparison lists that org-wide enforcement for both Teams and Enterprise. Still verify. Defaults are only useful if they are still in place on your team.
While a member is on a team, the team’s privacy mode governs them. That matters if someone also has a personal Cursor account. Cursor’s data governance documentation mentions an MDM option, Allowed Team IDs, which is designed to stop people signing into personal accounts on corporate devices. Check with Cursor whether that is available on your plan.
I have not seen a documented Privacy Mode toggle in the Grok Bot app itself. The documented Grok Bot Settings tabs are General, Computer, Vault, Usage and Billing, and Updates. Privacy Mode does not appear in that list. The approvals help article says privacy and data-sharing choices are managed through Cursor account settings and, when required, the Grok Bot access flow, which matches the Legacy prompt described above.
How to check it, and how to change it
For an individual account, Cursor’s privacy help gives this path in the Cursor app, not the Grok Bot app:
1. Open Cursor Settings with Cmd + Shift + J on a Mac, or Ctrl + Shift + J on Windows or Linux.
2. Click General in the sidebar.
3. Toggle Privacy Mode on.
If you cannot find that toggle, do not invent another path. Check in your Cursor account or team settings, and use the privacy help and data-use pages as the source.
For a team, Cursor’s Privacy and Data Governance page gives this path:
1. Go to your team dashboard.
2. Navigate to Settings.
3. Enable Privacy Mode for the team.
4. Optionally enforce it so members cannot disable it.
The teams documentation points to the same place in fewer words: check the privacy setting in Team Settings. The help article also says admins can enforce it organisation-wide via cursor.com/dashboard.
If Grok Bot is prompting you to leave Legacy Privacy Mode, follow that access flow, or ask a team admin to change the team’s setting. Do not try to “make Legacy work” with Grok Bot. The product does not support it.
One official caution when you create a team from a personal plan: the same October 2026 release notes say that a “Share Cursor Analytics” checkbox sets the new team’s privacy setting, and that Privacy Mode stays on unless you check it. If you are an MSP creating a team, read that box before you tick it.
What changes when you switch
Turn Privacy Mode on, and the published effect is that customer data is not used for training, and ZDR with model providers applies, subject to the abuse-classifier exception. Non-ZDR models, where a provider requires retention, are designated as such or need an admin to opt in. Cursor documents some models, such as the Claude Fable family, as working this way. Check the current models with data retention notes rather than treating this as a living list. Grok Bot also manages model selection and does not offer a customer-facing picker, so this is a team and provider question, not a per-chat toggle.
Turn Privacy Mode off, and Cursor may use and store prompts and related data to improve features and train models, as quoted above. For an MSP holding customer Microsoft 365 data in those prompts, that is a material change. I would not turn it off on an account that has ever been used with customer data, unless the customer has agreed and you have a reason that survives a privacy conversation.
Switching off Legacy and onto current Privacy Mode is what unblocks Grok Bot. It does not, by itself, delete data that is already stored, and I have not seen documentation that says turning Privacy Mode on wipes existing chats, memory or computer files. If you need a deletion or a confirmation of what happens to data already held, check with Cursor. The documented cleanup you can do yourself is still the practical one: pause routines, sign out of sites on the shared computer, remove sensitive files from `/workspace`, revoke connectors, and use Vault or a Secure Form rather than pasting secrets into chat.
Enforcing Privacy Mode at the team level means members cannot disable it. That is the right default for an MSP team that will see customer data.
What this means for MSPs
Customer Microsoft 365 data that a Bot reads can end up in a chat and on the shared computer even when Privacy Mode is on. Privacy Mode addresses training. It does not keep that copy inside the customer’s tenant. You still decide what the Bot is allowed to read, what you allow it to write into `/workspace`, and how long those files stay there. All of a user’s Bots share one computer, so a second Bot is not a privacy boundary for those files. If two customers’ data must never sit on the same disk, you need a separate Cursor user, as I set out in the earlier security post.
Tell customers the truth in plain language. Something like: we use Grok Bot with Privacy Mode enabled, which, according to Cursor, means customer data is not used for training, and model providers operate under zero data retention agreements, with a stated exception for abuse and safety classifiers. The Bot still stores chats and working files because the product requires storage. Grok Bot computers run in the United States. If we need a written residency commitment, that is a separate Cursor program, not the Privacy Mode toggle.
On residency, be precise. The security page and the security FAQ say Grok Bot computers run in the United States. Cursor also has a US-only data residency program. When it is enabled for a team, inference, processing and storage for Grok Bot stay in the US. That is a wider processing and storage commitment for enrolled customers, including backups; it is not automatic, it is enabled per team, and Cursor documents a pricing uplift and some exclusions, such as connectors. Contact Cursor if you need to enrol. Do not tell a customer the data never leaves Australia.
On contracts, Cursor’s privacy help is clear enough for a first pass. The Data Processing Agreement governs how Cursor processes personal data under enterprise contracts, for Teams and Enterprise customers. If you are on an individual plan, the DPA does not apply and data handling follows the Privacy Policy. Check what you actually have, and do not quote a DPA you have not signed. Current sub-processors are listed at trust.cursor.com/subprocessors.
Enterprise plans have extra controls beyond Privacy Mode, including audit logs, Action Recording, network allowlists, enforced Auto-review and related admin tooling. Those are Enterprise only. Privacy Mode itself is not an Enterprise-only feature. You can have the training commitment without those extra logs, and you should not tell a customer you have a SIEM feed unless your plan actually includes it.
What I would put in a customer conversation is short. Privacy Mode is on, or we will not use this account for your data. It is a no-training setting, not a no-storage setting. The computer is in the United States. We use least-privilege access, keep secrets out of chat, clean up working files, and will not turn Privacy Mode off without telling you.
Example prompts and Bot instructions
These are examples. They do not replace the setting, and a Bot cannot prove that Privacy Mode is on. You check that yourself in Cursor or in Team Settings.
Example: a profile instruction that treats customer data as temporary working material
You work on a single named customer at a time. Treat anything you read from Microsoft 365, email or files as customer data. Do not write customer data, secrets, tenant identifiers or mailbox content into memory, and do not ask me to paste passwords, client secrets or certificates into this chat. If a secret is required, use a Secure Form or Vault. Keep working files in a clearly named folder and be ready to list and remove them when I ask. If you are asked to confirm whether Privacy Mode is on, tell me you cannot certify that setting and that I should check it in Cursor account or team settings.
Example: asking a Bot to report what it is holding, not to invent a privacy setting
Before we start, list any files in /workspace that look like they belong to a customer, and tell me whether this chat already contains secrets or tenant identifiers. Do not guess whether Privacy Mode is on. I will check that in Cursor settings. Do not copy customer content into memory.
Example: cleaning up after a customer engagement
Pause any routines for this customer. List the connectors, browser sessions and files in /workspace that appear to belong to this engagement. Do not delete yet. I will tell you what to remove, and I will sign out of the admin centre and revoke access myself where needed. Do not keep a summary of customer data in memory after we finish.
Example: a boundary in a live request
Draft a short internal note from yesterday’s Service health for this tenant. Do not email anyone, do not change any policy, and do not store the raw export after you have drafted the note. Ask before saving anything outside this chat.
A short MSP checklist
- I have checked Privacy Mode in Cursor Settings or in Team Settings, and I have not assumed it is on.
- If I am on a team, Privacy Mode is enabled and, if my plan allows it, enforced so members cannot turn it off.
- I am not on Privacy Mode (Legacy). I understand that setting blocks Grok Bot because Grok Bot requires storage.
- I can explain to a customer, in plain language, that Privacy Mode is a no-training setting, not a no-storage setting, and that Grok Bot computers run in the United States.
- If a customer needs a written residency or DPA commitment, I have checked what Cursor actually offers for our plan, including the US-only residency program, rather than inventing one.
- Customer data in chats and on the shared computer is treated as a copy we are responsible for. I have a cleanup step, and I have not treated separate Bots as a privacy boundary.
- Secrets stay in Vault or a Secure Form, not in the transcript.
- I have not turned Privacy Mode off on an account used with customer data, and I know that doing so may allow prompts to be used to improve and train models.
- I have read Cursor’s current data-use, Grok Bot security and privacy pages, not only this post.
The practical takeaway
Privacy Mode is worth turning on, and on a team it is worth enforcing, before a Bot ever reads a customer’s tenant. It answers the training question customers will ask. It is not an answer to every privacy question they will ask. Storage, location, access and cleanup are still yours to manage.
Check the setting. Change it if it is wrong. Tell the customer what it does and what it does not do. Then use least privilege, approvals and a clean computer, so the training commitment is not the only control you are relying on.

