Organizations became generally available to Enterprise on June 3, 2026

Organizations became generally available to Enterprise on June 3, 2026: one org-level plane over teams, with Groups for cohort-level model access, spend limits and agent permissions. When memberships overlap, the most permissive setting wins.

The security one-pager to memorize: Privacy ModeCursor's setting that guarantees code data is not used for training by Cursor or its model providers, and that an admin can enforce org-wide; data-retention terms are a separate, contractual layer. Press Enter for the full definition. is on by default and cannot be turned off; zero-data-retention agreements with all major model providers; SOC 2 Type II attestations; SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool. Press Enter for the full definition. + MDM enforcement; code never leaves the US. Point customers to trust.cursor.com and the dedicated cloud-agent security page (covers repo cloning, snapshots, secrets/env-var handling).

Self-hosted clarification (top misconception): 'self-hosted' / private workersCloud-agent machines that run inside your own network so they can reach internal systems; the model inference still calls external providers. Press Enter for the full definition. run the agent container in your network - the model inference is still external (e.g. Opus still calls Anthropic's API). It is for assets that can't touch the internet, not on-prem AI.

Note on ZDRZero Data Retention. A contractual guarantee that the model provider won't store your code or train on it. Press Enter for the full definition. scope (load-bearing): zero-data-retention terms do NOT apply when a customer brings their own API keys. See the hard-questions section.