Grok Bot Terms — September 3, 2026

Cursor · agreement dated October 12, 2026 · Official agreement

Read the agreement

2 of 24 cards in Security & Safeguards

Security & Safeguards · Restriction or exception

Approval and automated-review controls are only aids and do not undo completed actions

Agentic Actions may be inaccurate, incomplete, delayed, unsuccessful or unintended. Approval and automated-review controls are provided as aids only. They may not identify or prevent every unintended, unauthorized or harmful action, and they do not reverse actions that are already completed. Provider is not liable for any Agentic Action that an approval or automated-review control fails to prevent.

Details
Who
Provider
What it covers
Approval and automated-review controls

Supporting quotations

Agentic Actions may be inaccurate, incomplete, delayed, unsuccessful, or unintended.
Approval and automated-review controls are provided as aids only, may not identify or prevent every unintended, unauthorized, or harmful action, and do not reverse completed actions.
Provider is not liable for any Agentic Action that an approval or automated-review control fails to prevent.

Qualifications & exceptions

  • The liability statement applies to actions that an approval or automated-review control “fails to prevent.”

Not stated here

  • This section does not say which approval or automated-review controls exist or on which plans.
  • This sentence has no stated exception; whether the exception in the all-capitals liability paragraph applies to it is not stated.

Security & Safeguards · Company practice

Bots of the same User may share an environment and are not separate security boundaries

Bots associated with the same User may share the persistent environment and must not be treated as separate security boundaries. Deleting a Bot may not delete the shared files, sessions, credentials or routines. A “User” is an individual authorized to use Grok Bot.

Details
Who
Bots associated with the same User
What it covers
Shared files, sessions, credentials and routines

Supporting quotations

Bots associated with the same User may share that environment and must not be treated as separate security boundaries.
Deleting a Bot may not delete shared files, sessions, credentials, or routines.
“User” means an individual authorized to use Grok Bot

Qualifications & exceptions

  • The sharing applies to Bots associated with the same User.
  • Deleting a Bot “may not” delete the shared items; the text does not say when it does.

Not stated here

  • The Terms do not say how Bots are associated with a User or which items are shared by default.
Also annotated in the same passage (4)