SpaceX Super Intelligence, Grok and Cursor for UK business

Last checked: 21 Oct 2026. Every vendor fact below comes from the public pages of SpaceX Super Intelligence (SpaceXSI) at x.ai and docs.x.ai, from Cursor's documentation, help, terms and security pages at cursor.com, and from two statements published by the Information Commissioner's Office.

SpaceXSI sells Grok (an assistant for staff, with team plans), the Grok API and its voice, image and video models, Grok Bot (AI agents that work on their own cloud computer) and Cursor (an AI coding product for engineering teams). The products now share a plan family and a usage pool, yet they still sit under different contracts, data settings and hosting arrangements. Before a UK business uses any of them, it should settle in writing which contract applies, whether its data can be used for training, how long data is kept and where it is processed.

Prices are in our separate post on Grok API pricing and Grok Bot, so this one describes how the products are charged without repeating figures.

What SpaceX Super Intelligence is, and why you will see several names

SpaceX announced on 2 Feb 2026 that it had acquired xAI, the company that built Grok. On 14 Aug 2026 Cursor announced that it had been acquired by SpaceX, completing a process that began in April with a partnership on model training. Cursor says the deal means it "can provide customers with more capable models at lower cost". That is the vendor's expectation, and the post says nothing about customer contracts, data handling or terms.

The company now trades as SpaceXSI, and its partner programme page spells the name out as the "SpaceX Super Intelligence Partner Network". The rename is not complete across the vendor's own sites, so buyers will meet several names for the same organisation.

What SpaceXSI sells: the product map

Grok and the Grok team plans

Beyond the apps, SpaceXSI announced Grok add-ins for PowerPoint, Word, Excel and Outlook, and Grok in Google Workspace, during June and July 2026. For organisations, it launched Grok Business and Grok Enterprise on 30 Dec 2025: Business as a self-serve plan for small and medium teams, and Enterprise adding custom single sign-on and directory sync. The Business page lists SOC 2 compliance, no training, custom data retention and connectors (these are the vendor's own lists). The pricing page now shows Teams and Enterprise columns instead of Business, so check it for the current name of the team plan.

The Grok API, voice, image and video

The Grok API is how a developer builds Grok into your own systems. SpaceXSI released Grok 4.7 on 21 Sep 2026, and the models page lists it with a 500k-token context window and a knowledge cut-off of May 2026, alongside earlier Grok 4 models, the Imagine image and video models and grok-voice-3.0. New Grok models have been arriving every few weeks, so treat any named model as correct only at the date of writing.

Grok Voice 3.0 was released on 14 Oct 2026 with speech-to-speech, and the release notes mark the previous voice model as deprecated. The custom voices feature "is currently only available in the United States, with the exception of Illinois", so UK teams cannot use it today. Our guide to which AI vendors do voice sets Grok against the alternatives.

Grok Build is a separate product from Cursor

SpaceXSI uses the name Grok Build for three things. It is the vendor's own coding agent, which it made open source in July 2026. It is a mode in Grok chat where you describe an app, game, website or dashboard and Grok builds a working version in the conversation. It is also a model name, grok-build-0.1. Cursor is a different product with its own documentation, settings and terms.

Grok Bot

Grok Bot gives each user a persistent cloud computer with "a browser, filesystem, and terminal, so tasks finish in your real tools instead of as chat drafts". Cursor's documentation describes a Bot as "a durable AI teammate with a name, a job, its own conversation, and working context that develops over time". SpaceXSI launched Grok Bot in beta on 11 Aug 2026. Its documentation says it "uses Cursor authentication and account data settings", although SpaceXSI also describes a shared sign-in route for The X Subscription. Our post on Grok Bot or Cursor cloud agents covers which suits which job.

Cursor

We use Cursor in our own engineering. Its cloud agents "run in isolated VMs in the cloud with full development environments instead of on your local machine", produce pull requests and need a paid plan. Automations run cloud agents on a schedule or in response to events from GitHub, GitLab, Slack, webhooks, Linear and other tools. Bugbot reviews pull requests for bugs, security issues and code quality problems. The Cursor SDK was announced in public beta on 29 Apr 2026 and lets developers call Cursor's agent from their own code. Self-hosted machines move file edits and terminal commands to hardware you manage, while Cursor still runs the agent loop, inference and planning.

Cursor's model documentation says it "supports frontier models from OpenAI, Anthropic, Google, SpaceXSI, and more". Buying Cursor does not commit a team to Grok models, and model choice inside Cursor carries its own billing, covered in Cursor spend controls and model choice.

How the products share a plan and a usage pool

On 12 Oct 2026 SpaceXSI introduced The X Subscription, which "brings together Grok, Grok Bot, Cursor, and X Premium in one plan". The pricing page lists Free, Plus, Premium, Super and Ultra for individuals, then Teams and Enterprise. The plan was still rolling out when we checked, so expect the names to move. According to the vendor's pages:

• Every tier includes a pool of AI usage shared across Grok and Cursor, which refreshes weekly and, within Grok, covers chat, Imagine, Voice and Bot.
• Third-party models in Cursor stay available on Premium and above, billed separately at API list prices through top-ups.
• Paid plans include Grok API access, but API usage is billed separately and does not draw from the pool.
• Cursor's business plans are Teams, charged per active paid seat, and Enterprise, priced by agreement.
• Published prices exclude VAT.

Moving to The X Subscription is optional and permanent: "It can't be undone, and Support can't undo it for you." Existing Enterprise customers are not moved automatically, and the eligibility table answers "Not yet" for a company on Enterprise for both products, on a negotiated contract or on Grok Enterprise. Cursor teams created before the change keep working as they are. Since the switch cannot be reversed, decide on paper before anyone clicks.

Contracts: which paper applies to you

The contracts are mid-migration, and which set applies depends on what you bought and when. We describe roles rather than naming a counterparty, because the answer differs between customers.

The Cursor addendum also says that even if a customer opts out of training, SpaceXSI may still use customer content "for safety, security, and evaluation purposes" when the customer gives feedback or content is flagged. Cursor's terms add that using Grok Bot brings in the separate Grok Bot terms.

The standard SpaceXSI enterprise terms contain points a UK legal or procurement team will want to raise. A negotiated order form can differ, and none of this is legal advice:

• Texas law governs, and the courts of Wichita County, Texas, have sole jurisdiction.
• The initial term is one year and renews automatically unless either party gives 30 days' written notice.
• Fees are stated to be non-cancellable and non-refundable.
• Either party may assign the agreement without consent to an affiliate or to a successor in a merger, reorganisation or acquisition.

Ask which company is named on your order form, which data processing addendum applies to each product you use, and what happens to your terms if your plan is converted.

Will SpaceXSI or Cursor train on your data?

For business products, the written position is no, with qualifications. The enterprise terms say SpaceXSI "will not use any User Content to train any foundation models, large language models, or other artificial intelligence systems", "subject to disclosures to Customer and Customer-controlled user settings". The same terms let SpaceXSI use de-identified or aggregated data derived from your use, except under zero data retention. The enterprise FAQ adds that "in some instances we may offer free credits in exchange for you agreeing to permit us to train on your business data", so read any credit offer for a training permission.

Consumer Grok has an "Improve the model" setting that each user controls. When staff use personal Grok accounts for work, the business has no say over that setting. Our guide to auditing shadow AI explains how to find out what people already use.

For Cursor, the deciding setting is Privacy Mode. Cursor's data use page says that with Privacy Mode on, customer data will not be used for training, and with it off, Cursor may use code data to train its models. The enterprise documentation says Privacy Mode is on by default for Enterprise teams, and the help centre says admins can enforce it. Anyone on a personal plan should check their own setting.

Grok Bot follows Cursor's settings. The Grok Bot security documentation says that with the team's Privacy Mode enabled, customer data is not used for training. The Grok Bot terms contain no training clause, and Cursor's help centre says Grok Bot runs "on a separate product surface with its own data flows". If a contractual no-training commitment for Grok Bot matters to you, ask for it in writing.

How long data is kept, and what zero data retention costs you

By default the Grok API stores requests and responses for 30 days for abuse monitoring, encrypted at rest, then deletes them. Zero data retention (ZDR) removes that storage, and the vendor is open about the cost: "For most customers, we do not recommend enabling ZDR." It switches off features that depend on stored data, including the stateful Responses API, Files and Collections, the Batch API, deferred completions, stored image and video outputs and voice agent conversation history. ZDR applies to the whole team and cannot be enabled for individual API keys. The enterprise terms add that it "may limit Customer's ability to respond to legal proceedings or audits requiring historical data".

Here is the point most UK buyers miss. The data processing addendum says the customer "will process Personal Data through the Services only using SpaceXSI's ZDR-Enabled API", and that failing to do so "will constitute a material breach of the Agreement". So a business that wants customer names, emails or support conversations to pass through the Grok API is directed to the mode that removes the stored-data features. The addendum page carries a "previous version" label, so a newer text may exist. Raise this with the vendor and your own legal adviser before designing anything that touches personal data.

For Cursor, cloud agents are the only feature that requires Cursor to store code, and they are optional: "If your security policy prohibits code storage, don't enable Cloud Agents." The cloud agent security page says each agent runs in its own virtual machine, snapshots are deleted after 30 days of inactivity, and conversation state is kept indefinitely by default but can be deleted on demand.

Grok Bot requires data storage and does not support Cursor's Legacy Privacy Mode, so a team relying on that setting cannot use it without changing it. The Grok Bot security documentation says hibernation is not deletion, data is deleted or returned within 30 days of written direction after the service ends, and a per-organisation retention policy is not available.

Where your data is processed

None of the documents we read offers UK processing or storage by default for any of these products.

Cursor's "inference-only" coverage means the model runs in the region, and says nothing about where processing and storage happen. SpaceXSI's regions page says a regional endpoint "is not, by itself, a comprehensive data-residency guarantee", and the Enterprise plan advertises data residency without naming a region. Treat any residency promise as something to obtain in writing, with the region named.

On transfers, the SpaceXSI data processing addendum allows processing "on a global basis outside Europe ... including in the United States", provides for UK transfers under the International Data Transfer Addendum issued by the Information Commissioner and commits to notifying security incidents within 48 hours. The subprocessor list shows US locations apart from one UK row for a SpaceXSI subsidiary providing services and support. That row does not mean your data is processed in the UK.

On 3 Feb 2026 the ICO opened formal investigations into the processing of personal data in relation to the Grok system and its potential to produce harmful sexualised image and video content. It concerns that image and video harm, rather than the enterprise API or Grok Bot. Our guide to UK data residency across the major AI vendors sets these products alongside the others.

Controls for Grok Bot and other agents

All of one user's Bots share the same cloud computer, including its files, browser sessions and app logins, and the documentation says "Do not use separate Bots as a security boundary." With Team Bots, released in public beta on 28 Sep 2026, each teammate's conversation stays private and "A Team Bot never lends one person's access to another."

Plan level decides which controls you get. On the Teams plan, Grok Bot is enabled by default for every member and "There is no switch to turn it off." On Enterprise an admin turns it on, and the documentation says Enterprise access is still rolling out and varies by organisation. The security documentation lists as Enterprise only the organisation-wide enable switch, network controls, team secrets, action recording, audit logs, OpenTelemetry export, the MCP allowlist and SCIM. Teams without a network policy default to allowing all destinations. If a self-serve Teams plan is in use anywhere in your business, those staff may already have Grok Bot.

Model choice sits with the product. Cursor's Grok Bot security page says there is no customer-facing model picker, requests go to SpaceXSI's own models or to third-party providers on the subprocessor list, and the team model allowlist does not govern Grok Bot. If your contract restricts subprocessors, raise it with the account team.

Responsibility sits with you. The Grok Bot terms make the customer "solely responsible" for ensuring a Bot's actions are authorised and lawful, and require "appropriate human review" before actions involving external communications, financial transactions, data deletion, permission changes, production systems or legal commitments. That matches the approach in our security review for AI agents. The ICO's call for evidence on agentic AI, open until 20 Nov 2026, makes the same point: "the fact AI agents act with autonomy is not an excuse for poor compliance."

Tagging @bot on X is not yet available for X accounts based in the United Kingdom or the European Union. No page we read names the UK as supported or unsupported for Grok Bot as a whole. For Cursor's agents, see Cursor cloud agent security and self-hosted Cursor agents.

Plan for model changes

SpaceXSI retires model names by redirecting them. After 15 May 2026, requests to retired model names were redirected to grok-4.3, which "is priced differently than the various models it replaces". A second notice retires an image model name on 2 Nov 2026, with requests served by a newer model at a low quality setting. The models page says a dated model name "will not be updated and is for workflows that demand consistency", so pin dated names for anything in production.

A sensible order for adopting SpaceXSI products

This is our own sequence, built from the facts above. It leaves room for concluding that a different product, or the AI you already pay for, fits better. If UK processing is a hard requirement, nothing in the documents we read provides it today, and that should shape the decision early.

Find out what is already in use

Staff may already use personal Grok accounts or have Grok Bot through a Teams plan. List the accounts, plans and who pays for them before choosing a plan structure, because the switch to The X Subscription is permanent.

Settle the paper and the data rules before anyone signs

Agree which data classes may go into which product. Then get written answers on the company named on the order form, the data processing addendum for each product, any training permission tied to credits, how personal data squares with the ZDR clause, and the region for each workload. Our AI policy template gives you clauses to record those decisions.

Set up engineering tools with Privacy Mode enforced

For engineering teams, Cursor with Privacy Mode enforced by an admin is a contained starting point. Put shared configuration in place before widening use, as described in rolling out Cursor to an engineering team and Cursor rules, skills, subagents and hooks. Add cloud agents once your policy allows Cursor to store code, pick a first job from Cursor cloud agents and automations, and calibrate code review with Cursor Bugbot.

Choose API workloads that fit the retention you accept

Start API work with content that holds no personal data, so you keep standard retention and the full feature set. Treat any workload involving personal data as a separate decision under the ZDR clause, and pin dated model names from the start. If you want Cursor's agent inside your own tools, read building on the Cursor SDK first.

Add agents last, with narrow access

Grok Bot reaches furthest, because it works inside other systems under a person's own logins. Introduce it once the controls you need are on your plan, give each Bot a narrow job, and keep human review on anything external, financial or irreversible. Regulated firms should read Cursor in regulated businesses. A time-boxed pilot, as in how to run an AI pilot, is the safest way to test it.

How SpotDev helps

SpotDev is a registered SpaceX Super Intelligence Transformation Partner. Partner status is not an endorsement of our services by SpaceXSI. We use Cursor in our own engineering, and the work we do with clients on these products is set out on our SpaceXSI and Cursor implementation page. Where another product, or AI you already pay for, fits your requirements better, we will say so.

Common questions

Does SpaceXSI train on our business data?

Not under its enterprise terms, which bar training on customer content subject to disclosures and customer-controlled settings. The enterprise FAQ notes that free credits are sometimes offered in exchange for permission to train, so check any credit offer. For Cursor, Privacy Mode prevents training and is on by default for Enterprise teams. Consumer Grok has a training setting each user controls.

Can we keep our data in the UK?

Not by default, on the documents we read on 21 Oct 2026. The Grok API has a global endpoint and a US endpoint. Grok Bot computers run in the United States. Cursor offers US-only residency to Enterprise customers and says UK inference-only coverage is available on request. Get any residency commitment in writing, with the region named.

Can we put personal data through the Grok API?

The data processing addendum says personal data may be processed only through the ZDR-enabled API, and treats any other route as a material breach. Zero data retention switches off features such as stateful responses, files and batch processing, and the vendor says most customers should not enable it. Raise this with the vendor and your legal adviser before you build.

What is the difference between Grok, Grok Build, Grok Bot and Cursor?

Grok is the assistant and model family, available in apps and through the Grok API. Grok Build is SpaceXSI's own coding agent, a build mode in Grok chat and a model name. Grok Bot is a set of named agents working on a persistent cloud computer. Cursor is a separate AI coding product with cloud agents, automations, Bugbot and an SDK.

Who do we contract with if we use Cursor through a SpaceXSI plan?

It depends on the plan and when you joined. Existing Cursor plans stay on Cursor's own terms until merged. Bundled plans are sold by a separate company acting as merchant of record. For converted Teams plans, claims about Cursor, Grok Bot and third-party models sit with Cursor's maker. Read your order form and ask which data processing addendum applies.

If you want a view of how these products would sit alongside your existing systems and data rules, start with a diagnostic, or visit our SpaceXSI implementation page to Request a Quote.

John Kelleher holds the SpaceX Super Intelligence Partner Network Accreditation: Forward Deployed Engineer.