Grok Bot Terms supplement the main Agreement and make Grok Bot part of the Services
These Grok Bot Terms, which state they were last updated on October 12, 2026, are added to the agreement that governs Customer’s use of the Services. The document calls that larger set the “Agreement” and lists any applicable Order Forms, data processing addendum, acceptable use policy, privacy policy and incorporated terms as part of it. Grok Bot counts as part of the Services when Customer enables or accesses it. The Terms do not change who the contracting party is and do not create a contract between Customer and any affiliate of Provider. An individual who uses Grok Bot on their own behalf is both Customer and User.
Details
What it covers
Grok Bot Terms as a supplement to the Agreement governing the Services
Condition
Grok Bot is part of the Services when Customer enables or accesses it
When
Last updated October 12, 2026
Supporting quotations
Last updated October 12, 2026
These Grok Bot Terms (“Grok Bot Terms”) supplement the agreement governing Customer’s use of the Services, which include the product identified as Grok Bot (“Grok Bot”), including any applicable Order Forms, data processing addendum, acceptable use policy, privacy policy, and incorporated terms (collectively, the “Agreement”).
Grok Bot is deemed part of the “Service” or “Services,” as applicable under the Agreement, when Customer enables or accesses it.
These Grok Bot Terms do not change the contracting party or create a contractual relationship between Customer and any affiliate of Provider.
If Customer is an individual using Grok Bot on their own behalf, Customer is also the User, and references to Customer’s Users mean Customer.
Qualifications & exceptions
Grok Bot is treated as part of the Services only “when Customer enables or accesses it.”
The listed documents are part of the Agreement only to the extent they are “applicable.”
The no-affiliate-contract statement is about the contracting party under these Terms.
Not stated here
The underlying Agreement and the documents it lists (Order Forms, data processing addendum, acceptable use policy, privacy policy) are not part of this document and are not read here.
This document does not name the entity that is Provider.
Provider, User and Customer Data are defined for Grok Bot
“Provider” is the entity providing Grok Bot to Customer under the Agreement, and “User” is an individual authorized to use Grok Bot. Capitalized terms not defined in these Terms take the meanings given in the Agreement. For these Terms, “Customer Data” includes inputs and other content submitted or made available by or for Customer.
Details
Who
Provider: the entity providing Grok Bot to Customer under the Agreement
What it covers
Customer Data includes inputs and other content submitted or made available by or for Customer
Supporting quotations
“Provider” means the entity providing Grok Bot to Customer under the Agreement, and “User” means an individual authorized to use Grok Bot.
Capitalized terms not defined here have the meanings given in the Agreement. In these Grok Bot Terms, “Customer Data” includes inputs, and other content submitted or made available by or for Customer.
Qualifications & exceptions
The Customer Data definition says it “includes” inputs and other content; it does not say that is a complete list.
Undefined capitalized terms take their meaning from the Agreement, which is not supplied here.
Not stated here
The definitions in the underlying Agreement are not part of this document.
Customer may let Users use Grok Bot for internal business purposes and must configure its controls
Subject to the Agreement, the Provider’s acceptable use policy, and the applicable account settings and permissions, Customer may permit its Users to use Grok Bot for Customer’s internal business purposes. Customer is responsible for configuring and administering the available settings, permissions, approval requirements, integrations and usage limits. Which controls are available may depend on Customer’s plan, configuration and deployment.
Details
Who
Customer, through its Users
Why
Customer’s internal business purposes
Condition
Subject to the Agreement, acceptable use policy, account settings and permissions
Supporting quotations
Subject to the Agreement, the Provider’s acceptable use policy, and the applicable account settings and permissions, Customer may permit its Users to access and use Grok Bot for Customer’s internal business purposes.
Customer is responsible for configuring and administering available settings, permissions, approval requirements, integrations, and usage limits.
Available controls may depend on Customer’s plan, configuration, and deployment.
Qualifications & exceptions
Use is permitted for Customer’s “internal business purposes.”
Subject to the Agreement, the acceptable use policy, and applicable account settings and permissions.
Available controls may depend on plan, configuration and deployment.
Not stated here
The definition of Customer covers an individual using Grok Bot on their own behalf, but this section speaks only of internal business purposes; it does not say whether or how personal use by an individual is covered.
Which controls exist on which plan or deployment is not stated here.
Legal Rights & Agreement Rules · Restriction or exception
Customer and Users must follow the Documentation, which promises no feature will stay available
Customer and its Users will use Grok Bot in accordance with Provider’s Documentation, which describes functionality, requirements, limits, controls and recommended practices. The Documentation does not create a service level, a warranty, or a commitment that any feature, integration, model or configuration will remain available.
Details
Who
Customer and its Users
What it covers
Provider’s Documentation
Supporting quotations
Customer and its Users will use Grok Bot in accordance with Provider’s Documentation, which describe functionality, requirements, limits, controls, and recommended practices.
The Documentation does not create a service level, warranty, or commitment that any feature, integration, model, or configuration will remain available.
Qualifications & exceptions
The no-commitment statement covers features, integrations, models and configurations.
Not stated here
The Documentation is not supplied here.
The sentence ties use to Documentation that includes “recommended practices”; it does not say which parts of the Documentation are mandatory.
Use & Processing · Company practice
Grok Bot may take autonomous actions on Customer’s behalf, such as running code and sending communications
The Terms define “Agentic Actions” as autonomous actions Grok Bot may perform on Customer’s behalf, including without limitation accessing websites, executing code, modifying files, sending communications, processing data, invoking tools and interacting with third-party services.
Details
Who
Grok Bot
What it does
autonomous actions on Customer’s behalf, including accessing websites, executing code, modifying files, sending communications, processing data, invoking tools and interacting with third-party services
Supporting quotations
Grok Bot may perform autonomous actions on Customer’s behalf (“Agentic Actions”), including without limitation accessing websites, executing code, modifying files, sending communications, processing data, invoking tools, and interacting with third-party services.
Qualifications & exceptions
The list is introduced by “including without limitation,” so it is not exhaustive.
The actions are performed on Customer’s behalf.
Not stated here
This section does not say which actions Grok Bot takes by default and which only after Customer enables or approves them.
Account & Service Control · Permission or license
Customer authorizes agentic actions it requests, approves, configures or permits, including ones Grok Bot starts itself
Customer authorizes Agentic Actions that Customer or its Users request, approve, configure or permit. That includes Agentic Actions that Grok Bot starts on its own, as long as they are within the scope of access, permissions and authority that Customer or its Users have granted.
Details
Who
Customer and its Users
Condition
Within the scope of access, permissions and authority granted by Customer or its Users
Supporting quotations
Customer authorizes Agentic Actions requested, approved, configured, or permitted by Customer or its Users, including Agentic Actions that Grok Bot initiates autonomously within the scope of access, permissions, and authority granted by Customer or its Users.
Qualifications & exceptions
Autonomous actions are covered only “within the scope of access, permissions, and authority granted by Customer or its Users.”
Not stated here
This sentence does not say what happens when Grok Bot acts outside the scope that was granted; a later all-capitals paragraph assigns responsibility for actions “whether or not” Customer authorized them.
Cross-references
contrast (model-proposed): Customer is responsible for all Grok Bot actions, even ones it did not intend or authorize — Section 2.2 ties Customer’s authorization to actions it requested, approved, configured or permitted, or that Grok Bot started within the access Customer granted. The all-capitals paragraph makes Customer solely responsible for all Agentic Actions taken by Grok Bot whether or not Customer intended, anticipated or authorized them. The document does not say how the two fit together.
Legal Rights & Agreement Rules · Restriction or exception
Customer is solely responsible for the legality, permissions, spending limits and monitoring of agentic actions
Customer is solely responsible for ensuring that Agentic Actions are authorized and lawful and comply with applicable laws and third-party terms, for configuring appropriate permissions, approval requirements and spending limits, and for monitoring recurring or unattended activities. Customer is also solely responsible for deciding the scope of access, permissions and authority given to each Bot, and for any Agentic Action that results from its or its Users’ configuration, instructions, permissions, approval settings, or failure to implement available safeguards.
Details
Who
Customer
What it covers
Agentic Actions, permissions, approval requirements, spending limits and unattended activities
Supporting quotations
Customer is solely responsible for ensuring those Agentic Actions are authorized, lawful, and comply with all applicable laws and third party terms, configuring appropriate permissions, approval requirements, and spending limits, and monitoring recurring or unattended activities.
Without limiting the foregoing, Customer is solely responsible for determining the scope of access, permissions, and authority granted to each Bot and for any Agentic Action that results from Customer’s or its Users’ configuration, instructions, permissions, approval settings, or failure to implement available safeguards.
Qualifications & exceptions
Responsibility reaches actions resulting from Customer’s or its Users’ configuration, instructions, permissions, approval settings, or failure to implement available safeguards.
The duty to monitor is stated for “recurring or unattended activities.”
Not stated here
“Bot” is capitalized but is not defined in this document, which defines “Grok Bot.”
Which safeguards count as “available” is not stated here.
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.
Account & Service Control · Restriction or exception
Customer will use appropriate human review before permitting agentic actions
Customer will use appropriate human review before permitting Agentic Actions, including those involving external communications, financial transactions, data deletion, permission changes, production systems, legal commitments, or material effects on third parties.
Details
Who
Customer
Condition
Before permitting Agentic Actions, especially external communications, financial transactions, data deletion, permission changes, production systems, legal commitments or material effects on third parties
Supporting quotations
Customer will use appropriate human review before permitting Agentic Actions, including those involving external communications, financial transactions, data deletion, permission changes, production systems, legal commitments, or material effects on third parties.
Qualifications & exceptions
The listed kinds of actions are introduced by “including,” so they are examples rather than a closed list.
Not stated here
“Appropriate” human review is not defined.
This paragraph has no number; it follows section 2.3 and precedes 2.4, and the document does not say which section it belongs to.
Charges & Financial Obligations · Restriction or exception
Customer bears the charges and consequences of agentic actions; Provider disclaims accuracy, safety and legality
Customer is solely responsible for charges, commitments, communications and other consequences resulting from Agentic Actions authorized or initiated by Customer or its Users. Provider makes no representations about the accuracy, safety or legality of any Agentic Action and disclaims all liability for Agentic Actions to the fullest extent permitted by law. Agentic Actions are provided “as is” and “as available” without warranty of any kind.
Details
Who
Customer
What it covers
Charges, commitments, communications and other consequences of Agentic Actions
Condition
Disclaimer applies to the fullest extent permitted by law
Supporting quotations
Customer is solely responsible for charges, commitments, communications, and other consequences resulting from Agentic Actions authorized or initiated by Customer or its Users.
Provider makes no representations regarding the accuracy, safety, or legality of any Agentic Action and disclaims all liability for Agentic Actions to the fullest extent permitted by law.
Agentic Actions are provided “as is” and “as available” without warranty of any kind.
Qualifications & exceptions
Customer’s responsibility here is for actions “authorized or initiated by Customer or its Users.”
The liability disclaimer applies “to the fullest extent permitted by law.”
Not stated here
This paragraph states no exception to the disclaimer; exceptions appear in separate paragraphs that follow it.
Legal Rights & Agreement Rules · Restriction or exception
Customer is responsible for all Grok Bot actions, even ones it did not intend or authorize
In an all-capitals acknowledgement, Customer accepts that Agentic Actions are probabilistic and may contain errors or produce results that are inaccurate, incomplete, incorrect, offensive, harmful or unsuitable for its intended purpose. Customer is solely responsible for all Agentic Actions taken by Grok Bot, whether or not Customer intended, anticipated or authorized them. That includes actions that result from configuration, instructions, permissions, approval settings, connected services, routines, or failure to implement available safeguards.
Details
Who
Customer
Condition
Whether or not the actions were intended, anticipated or authorized by Customer
Supporting quotations
CUSTOMER ACKNOWLEDGES THAT AGENTIC ACTIONS ARE PROBABILISTIC, MAY CONTAIN ERRORS, AND MAY PRODUCE RESULTS THAT ARE INACCURATE, INCOMPLETE, INCORRECT, OFFENSIVE, HARMFUL, OR OTHERWISE UNSUITABLE FOR CUSTOMER’S INTENDED PURPOSE.
CUSTOMER IS SOLELY RESPONSIBLE FOR ALL AGENTIC ACTIONS TAKEN BY GROK BOT, WHETHER OR NOT SUCH ACTIONS WERE INTENDED, ANTICIPATED, OR AUTHORIZED BY CUSTOMER
INCLUDING ANY AGENTIC ACTION THAT RESULTS FROM CUSTOMER’S OR ITS USERS’ CONFIGURATION, INSTRUCTIONS, PERMISSIONS, APPROVAL SETTINGS, CONNECTED SERVICES, ROUTINES, OR FAILURE TO IMPLEMENT AVAILABLE SAFEGUARDS.
Qualifications & exceptions
The acknowledgement covers actions “whether or not such actions were intended, anticipated, or authorized by Customer.”
Not stated here
This is wider than the earlier statements that tie Customer’s authorization and responsibility to actions it requested, permitted or authorized or that Grok Bot took within granted access. The document does not say how the two fit together.
“Routines” and “connected services” are not defined in this paragraph; connected services and routines are described later.
Cross-references
contrast (model-proposed): Customer authorizes agentic actions it requests, approves, configures or permits, including ones Grok Bot starts itself — Section 2.2 ties Customer’s authorization to actions it requested, approved, configured or permitted, or that Grok Bot started within the access Customer granted. The all-capitals paragraph makes Customer solely responsible for all Agentic Actions taken by Grok Bot whether or not Customer intended, anticipated or authorized them. The document does not say how the two fit together.
Legal Rights & Agreement Rules · Restriction or exception
Provider is not liable for agentic-action losses unless directly caused by its gross negligence or willful misconduct
Provider is not liable for any loss, damage, cost, charge, commitment or other consequence arising from any Agentic Action, except to the extent directly caused by Provider’s gross negligence or willful misconduct.
Details
Who
Provider
Exception
Except to the extent directly caused by Provider’s gross negligence or willful misconduct
Supporting quotations
PROVIDER IS NOT LIABLE FOR ANY LOSS, DAMAGE, COST, CHARGE, COMMITMENT, OR OTHER CONSEQUENCE ARISING FROM ANY AGENTIC ACTION, EXCEPT TO THE EXTENT DIRECTLY CAUSED BY PROVIDER’S GROSS NEGLIGENCE, OR WILLFUL MISCONDUCT.
Qualifications & exceptions
The exception applies only “to the extent directly caused by” Provider’s gross negligence or willful misconduct.
Not stated here
The source reads “GROSS NEGLIGENCE, OR WILLFUL MISCONDUCT” with a comma; this card reads the exception as covering both.
The document does not say whether this exception also applies to the separate no-liability statements in sections 2.3 and 2.4.
Any limitation of liability in the underlying Agreement is not supplied here.
The liability terms do not limit Provider’s personal data obligations under the Agreement
The paragraph states that “This Section” does not limit Provider’s obligations under the Agreement with respect to the processing of personal data, as defined in the applicable data processing addendum or applicable data protection laws.
Details
Who
Provider
What it covers
Provider’s obligations under the Agreement for processing personal data
Supporting quotations
This Section does not limit Provider’s obligations under the Agreement with respect to the processing of personal data (as defined in the applicable data processing addendum or applicable data protection laws).
Qualifications & exceptions
Covers Provider’s obligations “under the Agreement” about processing personal data.
“Personal data” is defined by the applicable data processing addendum or data protection laws.
Not stated here
“This Section” is not numbered or named; the paragraph follows the liability text in section 2 (Agentic Actions), so it most likely refers to that section, but the document does not say so.
The data processing addendum and the Provider’s personal data obligations are not supplied here.
Content & IP Rights · Permission or license
Provider may remove content or disable agentic actions it reasonably finds violate the rules
Provider may remove content or disable Agentic Actions that Provider reasonably determines violate the Agreement, the applicable acceptable use policy or applicable law. Provider may do this without prior notice when delay would pose a risk to safety, security or third parties.
Details
Who
Provider
What it does
Remove content or disable Agentic Actions
Condition
Without prior notice when delay would pose a risk to safety, security or third parties
Supporting quotations
Provider may remove content or disable Agentic Actions that Provider reasonably determines violate the Agreement, the applicable acceptable use policy, or applicable law,
without prior notice when delay would pose a risk to safety, security, or third parties.
Qualifications & exceptions
Provider must “reasonably determine” a violation of the Agreement, the acceptable use policy or applicable law.
Prior notice is dispensed with when delay would pose a risk to safety, security or third parties.
Not stated here
The section does not say whether Provider gives notice, before or after, when no such risk exists.
It does not say which content may be removed or how Customer can challenge a removal.
Use & Processing · Permission or license
Customer consents, for itself and its Users, to Grok Bot listening, transcribing and creating content in meetings
On behalf of itself and its Users, Customer consents to using Grok Bot in meetings to, for example, listen, process audio or video, process content that is explicitly provided or inferred, capture, transcribe, take notes, communicate, or create any content or its derivatives. The Terms call these the “Meeting Features.”
Details
Who
Customer, on behalf of itself and its Users
What it does
Consents to Grok Bot listening, processing audio or video, capturing, transcribing, taking notes, communicating and creating content in meetings
Supporting quotations
Customer, on behalf of itself and its Users, consents to using Grok Bot in meetings to, for example, listen, process audio or video, process explicitly provided or inferred content, capture, transcribe, take notes, communicate, or create any content or its derivatives (“Meeting Features”).
Qualifications & exceptions
The consent is given by Customer “on behalf of itself and its Users.”
The activities are introduced by “for example,” so the list is not exhaustive.
The text covers content that is “explicitly provided or inferred.”
Not stated here
The Terms do not say which meeting services Grok Bot works with, when it joins a meeting, or how long meeting content is kept.
This consent is Customer’s own; the text does not treat it as consent by other meeting participants.
Legal Rights & Agreement Rules · Restriction or exception
If Meeting Features are used, Customer must give notices, get consents from all participants and follow recording laws
If Customer or its Users use Meeting Features, Customer represents, warrants and agrees that it will, and will cause its Users to, (a) give all required notices to, and obtain all required consents from, all meeting participants; (b) comply with applicable laws, regulations, contractual obligations and, if applicable, organizational policies about communications, privacy, interception, wiretapping, consumer protection, recording, monitoring, transcription and processing of communications; and (c) not use Meeting Features in a way that violates anyone’s privacy or other legal rights. Customer is responsible for deciding whether notice or consent is required for a particular meeting, and it will not begin the affected activity, or will stop it, if a required consent is refused or withdrawn.
Details
Who
Customer and its Users
Condition
If Customer or its Users use Meeting Features
What it does
Give notices, obtain consents from all meeting participants, comply with applicable laws, and stop if consent is refused or withdrawn
Supporting quotations
If Customer or its Users use Meeting Features, Customer represents, warrants, and agrees that it will, and will cause its Users to (a) provide all required notices to, and obtain all required consents from, all meeting participants;
(b) comply with all applicable laws, regulations, contractual obligations, and, if applicable, organizational policies relating to, for example, communications, privacy, interception, wiretapping, consumer protection, recording, monitoring, transcription, and processing of communications;
(c) not use Meeting Features in a manner that violates any person’s privacy or other legal rights.
Customer is responsible for determining whether notice or consent is required for a particular meeting and will not begin, or will stop, the affected activity if a required consent is refused or withdrawn.
Qualifications & exceptions
The duties apply “If Customer or its Users use Meeting Features.”
Notices and consents are required only to the extent “required”; Customer decides whether they are required for each meeting.
The laws and policies are listed “for example,” so the topics are not exhaustive.
Customer must stop the affected activity if a required consent is refused or withdrawn.
Not stated here
The Terms do not say how Provider checks or enforces these duties, or what follows from a breach of the stated representations and warranties.
Legal Rights & Agreement Rules · Restriction or exception
Provider says it provides technology only, gives no legal advice and does not guarantee a use is lawful
For Meeting Features, Provider says it provides technology only. It does not provide legal advice, does not act as an interceptor or recorder, and does not guarantee that any use is legal.
Details
Who
Provider
Supporting quotations
Provider provides technology only and does not provide legal advice, act as an interceptor or recorder, or guarantee legality of any use.
Not stated here
The statement that Provider does not “act as an interceptor or recorder” is Provider’s own description; the Terms do not explain how that fits with Grok Bot capturing and transcribing meetings for Customer.
Connecting a third-party service authorizes Grok Bot to access, send and use Customer Data through it
When Customer or its Users connect an account, application, website, add-on or other third-party service to Grok Bot, Customer instructs and authorizes Grok Bot to access, transmit and interact with Customer Data through that service, as directed or configured by Customer or its Users.
Details
Who
Customer, authorizing Grok Bot
What it covers
Customer Data accessed and transmitted through connected third-party services
Condition
By connecting an account, application, website, add-on or other third-party service to Grok Bot
Supporting quotations
By connecting an account, application, website, add-on or other third-party service to Grok Bot, Customer instructs and authorizes Grok Bot to access, transmit, and interact with Customer Data through that service as directed or configured by Customer or its Users.
Qualifications & exceptions
The authorization applies “as directed or configured by Customer or its Users.”
It follows from connecting a service to Grok Bot.
Not stated here
The Terms do not name which services can be connected or what data Grok Bot sends to each.
Customer Data is defined as including inputs and other content; the text here does not say whether other information is also sent to connected services.
Legal Rights & Agreement Rules · Restriction or exception
Customer answers for authority and third-party terms; Provider disclaims responsibility for connected services
Customer represents that it has authority to grant the access and is responsible for accepting and complying with applicable third-party terms, permissions and charges. Provider says it is not responsible for, does not endorse, makes no warranty about, and does not support any third-party service, and is not responsible for the availability, security or operation of third-party services. Use of connected services is at Customer’s own risk, and Provider disclaims liability to the greatest extent permitted by law. This fits with other terms: the Agentic Actions section also makes Customer responsible for ensuring actions comply with third-party terms, and the all-capitals paragraph there covers actions that result from “connected services.”
Details
Who
Customer
Who
Provider
What it covers
Third-party services connected to Grok Bot
Supporting quotations
Customer represents that it has authority to grant such access and is responsible for accepting and complying with applicable third-party terms, permissions, and charges.
Provider is not responsible for, does not endorse, makes no warranty regarding, and does not provide support for, any third-party service. Provider is not responsible for the availability, security, or operation of third-party services.
Use of any connected services is at Customer’s own risk and Provider disclaims any liability to the greatest extent permitted by law.
comply with all applicable laws and third party terms
CONNECTED SERVICES, ROUTINES
Qualifications & exceptions
The liability disclaimer applies “to the greatest extent permitted by law.”
The disclaimer covers any third-party service connected to Grok Bot.
Not stated here
The third-party terms, permissions and charges are not supplied and vary by service.
Grok Bot may keep Customer Data, files, sessions, credentials, memory and routines in a persistent cloud environment
Grok Bot may retain Customer Data, files, browser sessions, credentials, memory and routines in a persistent cloud environment. Customer Data is defined in these Terms as including inputs and other content submitted or made available by or for Customer.
Details
Who
Grok Bot
What it covers
Customer Data, files, browser sessions, credentials, memory and routines
Supporting quotations
Grok Bot may retain Customer Data, files, browser sessions, credentials, memory, and routines in a persistent cloud environment.
“Customer Data” includes inputs, and other content submitted or made available by or for Customer.
Qualifications & exceptions
The text says “may retain”; it does not say that all listed items are always kept.
Not stated here
The Terms give no retention period and do not say where the cloud environment is located or who can access it.
The text does not say whether Provider ever deletes the retained items on its own.
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.
Customer must delete or disable bots, remove data, revoke access and disable routines when no longer needed
Customer is responsible for deleting or disabling bots, removing data, revoking access and disabling routines when they are no longer required. The previous paragraph of the same section says deleting a Bot may not delete the shared files, sessions, credentials or routines.
Details
Who
Customer
Condition
When deleting, disabling, removing or revoking is no longer required
Supporting quotations
Customer is responsible for deleting or disabling bots, removing data, revoking access, and disabling routines when no longer required.
Qualifications & exceptions
The duty applies “when no longer required.”
Not stated here
The Terms do not say how Customer removes shared data or revokes access, or who decides when something is “no longer required.”
Legal Rights & Agreement Rules · Permission or license
Provider may update the Terms; materially adverse updates get reasonable notice, and continued use is acceptance
Provider may update these Grok Bot Terms from time to time. An update that is not materially adverse to Customer takes effect on posting or other notice to Customer. For a materially adverse update, Provider will give Customer reasonable notice, subject to applicable laws, before it takes effect; the Terms call this the “Update Notice Period.” Customer’s continued use of Grok Bot after the Update Notice Period counts as acceptance of the updated Terms.
Details
Who
Provider
Condition
Materially adverse updates need reasonable notice before they take effect; continued use after the Update Notice Period is acceptance
Supporting quotations
Provider may update these Grok Bot Terms from time to time. Unless an update is materially adverse to Customer, updates take effect upon posting or other notice to Customer. If an update is materially adverse to Customer, Provider will provide Customer with reasonable notice (subject to applicable laws) before the update takes effect (“Update Notice Period”).
Customer’s continued use of Grok Bot after the Update Notice Period constitutes acceptance of the updated Grok Bot Terms.
Qualifications & exceptions
Updates that are not materially adverse take effect “upon posting or other notice.”
Notice for materially adverse updates is “reasonable notice (subject to applicable laws).”
Not stated here
The Terms do not give the length of the Update Notice Period, say who decides whether an update is materially adverse, or say what “other notice” means.
The acceptance-by-use sentence refers to the Update Notice Period, which is defined only for materially adverse updates; the text does not say how acceptance works for other updates.