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.
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.
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.
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.
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.
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.
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.