Grok Bot Terms add to the main agreement and apply once Grok Bot is enabled
These terms are a supplement. They sit on top of the separate agreement that governs the Customer's use of the Services, and the text names Order Forms, a data processing addendum, an acceptable use policy, a privacy policy and incorporated terms as part of that agreement. Grok Bot counts as part of the Service or Services under that agreement from the moment the Customer enables or accesses it. The page is dated October 31, 2026.
Supporting quotations
Last updated: October 31, 2026
supplement the agreement governing Customer’s use of the Services
Grok Bot is deemed part of the “Service” or “Services,” as applicable under the Agreement, when Customer enables or accesses it.
Qualifications & exceptions
Grok Bot becomes part of the Services only “when Customer enables or accesses it.”
The text supplements the agreement and does not say which of the two controls if they conflict.
Not stated here
The main agreement, any Order Forms, the data processing addendum, the acceptable use policy and the privacy policy are not supplied in this text, so their terms are unknown here.
This text does not say which of the listed documents applies to any particular Grok Bot user.
Legal Rights & Agreement Rules · Context
Provider and User are defined; no contract with Provider's affiliates is created
“Provider” is the entity that provides Grok Bot to the Customer under the main agreement, and a “User” is an individual the Customer authorizes to use Grok Bot. These terms do not change who the contracting party is and do not create a contract between the Customer and any affiliate of the Provider. An individual who uses Grok Bot on their own behalf is both the Customer and the User, and references to the Customer's Users then mean that individual.
Supporting quotations
“Provider” means the entity providing Grok Bot to Customer under the Agreement
“User” means an individual authorized to use Grok Bot
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
The individual-as-Customer rule applies only “If Customer is an individual using Grok Bot on their own behalf.”
Not stated here
The text does not name the Provider entity; it is whichever entity provides Grok Bot under the main agreement, which is not supplied here.
Content & IP Rights · Context
Customer Data includes inputs and other content the Customer submits or makes available
For these terms, “Customer Data” includes inputs and other content submitted or made available by or for the Customer. Other capitalized terms that these terms do not define take the meanings they have in the main agreement. The text says “includes”, so the definition is not stated to be limited to these items.
Supporting quotations
Capitalized terms not defined here have the meanings given in the Agreement.
“Customer Data” includes inputs, and other content submitted or made available by or for Customer.
Qualifications & exceptions
The definition applies “In these Grok Bot Terms” only.
Not stated here
The wording reads “includes inputs, and other content”; the text does not say what other kinds of content, such as outputs, are covered.
Terms defined only in the main agreement are not supplied here.
Account & Service Control · Permission or license
Customer may let its Users use Grok Bot for internal business purposes
The Customer may permit its Users to access and use Grok Bot for the Customer's internal business purposes. That permission is subject to the main agreement, the Provider's acceptable use policy, and the account settings and permissions that apply.
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.
Qualifications & exceptions
Subject to the agreement, the acceptable use policy and “the applicable account settings and permissions.”
Limited to “Customer’s internal business purposes.”
Not stated here
The acceptable use policy is not supplied in this text.
The text does not say how “internal business purposes” applies when the Customer is an individual using Grok Bot on their own behalf, a case it recognizes elsewhere.
Account & Service Control · Restriction or exception
Customer is responsible for configuring and administering Grok Bot settings and limits
The Customer is responsible for configuring and administering the available settings, permissions, approval requirements, integrations and usage limits. Which controls exist can depend on the Customer's plan, configuration and deployment, so the text does not promise the same controls to every Customer.
Supporting quotations
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
“Available controls may depend on Customer’s plan, configuration, and deployment.”
Not stated here
The text does not list which controls each plan or deployment includes.
Legal Rights & Agreement Rules · Restriction or exception
Customer and Users must follow the Documentation, which promises no availability
The Customer and its Users must use Grok Bot in accordance with the 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 stay available.
Supporting quotations
Customer and its Users will use Grok Bot in accordance with Provider’s Documentation
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 “any feature, integration, model, or configuration.”
Not stated here
The Documentation is not supplied in this text, so its requirements and limits are unknown here.
Account & Service Control · Restriction or exception
Users must be at least 18, and Customer must keep younger people out
Users must be at least 18 years old, or the age of majority where they live if that is higher. The Customer must ensure that no one under that age uses Grok Bot through its account.
Supporting quotations
Users must be at least 18 years old (or the age of majority where they live, if higher) to use Grok Bot, and Customer will ensure no one under that age accesses Grok Bot through its account.
Qualifications & exceptions
The age is 18 “or the age of majority where they live, if higher.”
Provider may verify or estimate Users' ages using signals and email-based estimation
The Provider may use a variety of age assurance measures to verify or estimate whether Users meet the age requirement. The text names existing highly reliable signals and email address-based estimation as examples, and the words “without limitation” mean these examples are not the full list.
Supporting quotations
Provider may employ a variety of age assurance measures to verify or estimate whether Users meet this age requirement, including, without limitation, existing highly reliable signals and email address-based estimation.
Qualifications & exceptions
The measures are listed “including, without limitation”, so other measures may be used.
Not stated here
The text does not say what “existing highly reliable signals” are, what data the measures use beyond email address-based estimation, or what happens to a User an estimate flags.
Legal Rights & Agreement Rules · Restriction or exception
Grok Bot may place or receive phone calls for the Customer, who is caller of record and solely responsible
Grok Bot may place or receive phone calls on the Customer's behalf, called Calls. Calls are Agentic Actions. The Customer is the caller of record and is solely responsible for them, including compliance with all applicable cellular, landline, telemarketing, robocall, caller ID and call-recording laws, such as the Telephone Consumer Protection Act.
Supporting quotations
Grok Bot may place or receive phone calls on Customer’s behalf (“Calls”).
Calls are Agentic Actions, and Customer is the caller of record and solely responsible for them, including compliance with all applicable cellular, landline, telemarketing, robocall, caller ID, and call-recording laws, such as the Telephone Consumer Protection Act.
Qualifications & exceptions
The legal-compliance list is introduced by “including,” and the text gives the Telephone Consumer Protection Act as one example.
Not stated here
The text does not name which laws apply beyond the example, and does not say in which countries Calls can be placed.
Legal Rights & Agreement Rules · Restriction or exception
Customer may call only people who agreed, and may not use Calls for marketing, fraud or emergency services
The Customer may only call people who have agreed to hear from it. It represents, warrants and agrees that it will obtain all required consents and permissions from anyone it calls. The Customer may not use Calls for marketing or mass calls, fraud, harassment, impersonation, emergency services, or any purpose prohibited by the acceptable use policy.
Supporting quotations
Customer may only call people who have agreed to hear from it, and represents, warrants, and agrees that it will obtain all required consents and permissions from any callees.
Customer may not use Calls for marketing or mass calls, fraud, harassment, impersonation, emergency services, or any purpose prohibited by the acceptable use policy.
Qualifications & exceptions
The consent duty covers “all required consents and permissions from any callees.”
Not stated here
The acceptable use policy is not supplied in this text.
The text does not define “mass calls” or say how many calls make a call mass.
Calls say they come from a virtual assistant and may be recorded; Customer may not turn that off
Calls identify themselves as made by a virtual assistant on the Customer's behalf, and they may be recorded. The Customer may not alter or disable these disclosures.
Supporting quotations
Calls identify themselves as made by a virtual assistant on Customer’s behalf and may be recorded.
Customer may not alter or disable these disclosures.
Qualifications & exceptions
Calls “may be recorded,” which is permissive; the text does not say Calls will always be recorded.
Not stated here
The text does not say who records, how recordings are stored or used, or how long they are kept.
The text does not say whether people on a Call are told about the recording beyond the virtual-assistant disclosure.
Provider may honor opt-outs, block numbers or regions, and limit, end or suspend Calls at any time
The Provider may honor opt-out requests, block numbers or regions, limit or end Calls, and suspend access to Calls at any time in its sole discretion. Calls are not a telephone service and cannot be used to reach emergency services.
Supporting quotations
Provider may honor opt-out requests, block numbers or regions, limit or end Calls, and suspend access to Calls at any time in its sole discretion.
Calls are not a telephone service and cannot be used to reach emergency services.
Qualifications & exceptions
Provider's powers are exercisable “at any time in its sole discretion.”
Not stated here
The text does not say whose opt-out requests are meant or whether the Provider must honor them, only that it “may.”
The text does not say whether the Customer gets notice before access to Calls is suspended.
Charges & Financial Obligations · Restriction or exception
Temporary phone numbers stay Provider's property, and Customer indemnifies Provider for Calls claims
The Provider may assign the Customer temporary phone numbers solely for Calls. The numbers remain the property of the Provider or its providers and may be reclaimed or reassigned at any time. The Customer will indemnify the Provider for claims arising from its Calls or its use of any temporary phone numbers.
Supporting quotations
Provider may assign Customer temporary phone numbers solely for Calls, which remain the property of Provider or its providers and may be reclaimed or reassigned at any time.
Customer will indemnify Provider for claims arising from its Calls or use of any temporary phone numbers.
Qualifications & exceptions
The numbers are assigned “solely for Calls.”
Not stated here
The text does not cap the indemnity or say which kinds of claims or costs it covers.
Legal Rights & Agreement Rules · Permission or license
Customer and its Users agree to receive Calls, including AI-voice Calls, from Grok Bot and from Provider and affiliates
The Customer, for itself and its authorized Users, agrees to receive Calls, including in an AI-generated voice. These come from Grok Bot acting on behalf of other users, and from the Provider and its affiliates about the Services.
Supporting quotations
Customer, for itself and its authorized Users, agrees to receive Calls, including in an AI-generated voice, from Grok Bot on behalf of other users and from Provider and its affiliates about the Services.
Qualifications & exceptions
Covers Calls from Grok Bot “on behalf of other users” and from “Provider and its affiliates about the Services.”
Not stated here
The text does not limit how often or at what times such Calls may be made, or describe how the Customer or its Users can decline them.
The affiliates are not named; the text elsewhere says it creates no contract with the Provider's affiliates.
Connecting a third-party service authorizes Grok Bot to access and send Customer Data through it
By connecting an account, application, website, add-on or other third-party service to Grok Bot, the Customer instructs and authorizes Grok Bot to access, transmit and interact with Customer Data through that service, as directed or configured by the Customer or its Users. The Customer represents that it has authority to grant this access and is responsible for accepting and complying with the third party's terms, permissions and charges.
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.
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.
Qualifications & exceptions
Access is “as directed or configured by Customer or its Users.”
Not stated here
The third-party terms are not supplied in this text.
The text does not say what Customer Data Grok Bot sends to a connected service beyond that it may “access, transmit, and interact with” it.
Legal Rights & Agreement Rules · Restriction or exception
Provider disclaims responsibility for connected third-party services and use is at Customer's own risk
The Provider is not responsible for, does not endorse, makes no warranty about, and does not support any third-party service. It is not responsible for the availability, security or operation of third-party services. Use of any connected service is at the Customer's own risk, and the Provider disclaims any liability to the greatest extent permitted by law.
Supporting quotations
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.
Qualifications & exceptions
The liability disclaimer applies “to the greatest extent permitted by law.”
Not stated here
The text does not say whether the Provider is responsible for what Grok Bot itself does with Customer Data when it uses a connected service.
Bots of the same User share an environment that is not a security boundary; deleting a Bot may not delete shared items
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 shared files, sessions, credentials or 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.
Qualifications & exceptions
Applies to Bots “associated with the same User.”
Deletion “may not” remove shared items, so shared items can remain.
Not stated here
“Bot” is capitalized but not defined in this text.
The text does not say which items a Bot deletion does remove, or how a User can delete shared items.
Legal Rights & Agreement Rules · Permission or license
Provider may update these terms; materially adverse updates get reasonable notice, and continued use means acceptance
The Provider may update these terms from time to time. Unless an update is materially adverse to the Customer, it takes effect on posting or other notice to the Customer. For a materially adverse update, the Provider will give the Customer reasonable notice, subject to applicable laws, before it takes effect; this is called the Update Notice Period. Continued use of Grok Bot after the Update Notice Period counts as acceptance of the updated terms.
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
Reasonable notice for adverse updates is “subject to applicable laws.”
The Update Notice Period is defined only for updates that are materially adverse.
Not stated here
The text does not say how long the Update Notice Period is, what form notice takes, or who decides whether an update is materially adverse.
The text does not say how acceptance by continued use works for updates that are not materially adverse, since it ties acceptance to the Update Notice Period.
Updates will not reduce Customer's rights under the main agreement for data submitted before the update
Updates to these terms will not diminish the Customer's rights under the main agreement with respect to Customer Data submitted before the update takes effect.
Supporting quotations
Updates will not diminish Customer’s rights under the Agreement with respect to Customer Data submitted before the update takes effect.
Qualifications & exceptions
Protects rights only for Customer Data “submitted before the update takes effect.”
The protected rights are those “under the Agreement.”
Not stated here
The Customer's rights under the main agreement are not supplied in this text.
The text does not say whether updates may change rights in Customer Data submitted after the update.
Grok Bot may take actions on the Customer's behalf, including sending communications and running code
Grok Bot may perform actions for the Customer, called Agentic Actions. The text lists accessing websites, executing code, modifying files, sending communications, processing data, invoking tools and interacting with third-party services, and “without limitation” means the list is not complete.
Supporting quotations
Grok Bot may perform 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 actions are taken “on Customer’s behalf.”
The list is introduced by “including without limitation.”
Not stated here
The text does not say which actions Grok Bot performs by default, or which require the Customer's approval.
Customer authorizes Agentic Actions, including ones Grok Bot starts on its own within granted access
The Customer authorizes Agentic Actions that it or its Users request, approve, configure or permit. This includes Agentic Actions that Grok Bot starts autonomously, as long as they are within the scope of access, permissions and authority the Customer or its Users have granted.
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
The text does not say how the scope of access, permissions and authority is set or shown, beyond the Customer's settings and instructions.
Legal Rights & Agreement Rules · Restriction or exception
Customer is solely responsible for lawfulness, permissions, spending limits and monitoring of Agentic Actions
The Customer is solely responsible for making sure Agentic Actions are authorized, lawful and compliant with applicable laws and third-party terms. It is also solely responsible for configuring appropriate permissions, approval requirements and spending limits, and for monitoring recurring or unattended activities. The text adds that the Customer alone decides the scope of access, permissions and authority given to each Bot, and is solely responsible for any Agentic Action that results from its or its Users' configuration, instructions, permissions, approval settings or failure to implement available safeguards.
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.
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
The responsibility is stated “Without limiting the foregoing,” so the broader sentence adds to the earlier duties.
The sentence on resulting actions covers configuration, instructions, permissions, approval settings and “failure to implement available safeguards.”
Not stated here
“Bot” is capitalized but not defined in this text; it appears to refer to a Grok Bot instance, which the text does not state.
Which safeguards are “available” depends on controls described in the Documentation and the Customer's plan, which are not supplied.
Legal Rights & Agreement Rules · Restriction or exception
Agentic Actions may be wrong, and approval controls may not stop harmful ones or undo completed ones
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 completed actions. The Provider is not liable for an Agentic Action that such a control fails to prevent.
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 controls are described as “aids only.”
The no-liability statement covers actions a control “fails to prevent.”
Not stated here
The text does not describe what the approval and automated-review controls are or how they work.
Legal Rights & Agreement Rules · Restriction or exception
Customer must use appropriate human review before permitting Agentic Actions
The Customer must use appropriate human review before permitting Agentic Actions. The text gives external communications, financial transactions, data deletion, permission changes, production systems, legal commitments and material effects on third parties as examples of what this covers.
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 areas are introduced by “including,” so they are examples and not a full list.
Not stated here
The text does not say what counts as “appropriate” human review or how the Provider would judge it.
Charges & Financial Obligations · Restriction or exception
Customer is solely responsible for charges, commitments and communications from authorized or initiated actions
The Customer is solely responsible for the charges, commitments, communications and other consequences of Agentic Actions that it or its Users authorize or initiate.
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.
Qualifications & exceptions
Limited here to actions “authorized or initiated by Customer or its Users.”
Not stated here
A later paragraph in the same section uses broader wording, “whether or not such actions were intended, anticipated, or authorized by Customer.”
Cross-references
contrast (model-proposed): Customer solely responsible for all Agentic Actions; Provider liable only for gross negligence or willful misconduct — One paragraph makes the Customer solely responsible for consequences of Agentic Actions it or its Users authorize or initiate. The later capitalized paragraph makes the Customer solely responsible for all Agentic Actions whether or not intended, anticipated or authorized. The two differ in reach and the text does not say which controls.
Legal Rights & Agreement Rules · Restriction or exception
Provider makes no promises about Agentic Actions and disclaims liability for them
The Provider makes no representations about the accuracy, safety or legality of any Agentic Action. It disclaims all liability for Agentic Actions to the fullest extent permitted by law, and Agentic Actions are provided “as is” and “as available” without warranty of any kind.
Supporting quotations
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
The liability disclaimer applies “to the fullest extent permitted by law.”
Not stated here
The text does not say which laws limit this disclaimer.
A later paragraph in the same section carves out gross negligence and willful misconduct from the Provider's non-liability.
Legal Rights & Agreement Rules · Restriction or exception
Customer solely responsible for all Agentic Actions; Provider liable only for gross negligence or willful misconduct
In capitalized text, the Customer acknowledges that Agentic Actions are probabilistic and may be inaccurate, incomplete, incorrect, offensive, harmful or unsuitable for its purpose. The Customer is solely responsible for all Agentic Actions Grok Bot takes, whether or not the Customer intended, anticipated or authorized them. This includes actions that result from the Customer's or its Users' configuration, instructions, permissions, approval settings, connected services, routines or failure to implement available safeguards. The Provider is not liable for any loss, damage, cost, charge, commitment or other consequence of an Agentic Action, except to the extent directly caused by the Provider's gross negligence or willful misconduct.
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.
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 Provider's exception applies only “to the extent directly caused by” its gross negligence or willful misconduct.
The responsibility statement covers actions “whether or not such actions were intended, anticipated, or authorized by Customer.”
Not stated here
The text does not say who decides whether a loss was directly caused by gross negligence or willful misconduct.
This paragraph is broader than the earlier statements that tie responsibility to actions the Customer or its Users authorized or initiated; the text does not say which controls if they differ.
contrast (model-proposed): Customer is solely responsible for charges, commitments and communications from authorized or initiated actions — One paragraph makes the Customer solely responsible for consequences of Agentic Actions it or its Users authorize or initiate. The later capitalized paragraph makes the Customer solely responsible for all Agentic Actions whether or not intended, anticipated or authorized. The two differ in reach and the text does not say which controls.
Section on Agentic Action liability does not limit Provider's personal data obligations in the main agreement
The paragraph says that “This Section” does not limit the Provider's obligations under the main agreement for the processing of personal data, as defined in the applicable data processing addendum or data protection laws. As the text puts it, the section's statements do not reduce those obligations.
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
Applies to obligations “with respect to the processing of personal data.”
Not stated here
The text says “This Section” without naming it; it follows the Consequences and Liability heading, and the text does not say whether it means that subsection or all of Agentic Actions.
The data processing addendum and the Provider's personal data obligations are not supplied in this text.
Provider may remove content or disable Agentic Actions it reasonably finds in violation, without notice if urgent
The Provider may remove content or disable Agentic Actions that it reasonably determines violate the main agreement, the applicable acceptable use policy or applicable law. It may do so 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
The Provider must “reasonably determine” a violation.
No prior notice is required only “when delay would pose a risk to safety, security, or third parties.”
Not stated here
The text does not say what notice, if any, applies when delay does not pose such a risk, or whether removed content can be restored or appealed.
Use & Processing · Permission or license
Customer consents, for itself and its Users, to Grok Bot's use in meetings
The Customer, on behalf of itself and its Users, consents to using Grok Bot in meetings. The text says Grok Bot may, for example, listen, process audio or video, process explicitly provided or inferred content, capture, transcribe, take notes, communicate, or create content or derivatives of it. These are called Meeting Features.
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 activities are introduced by “for example,” so the list is not complete.
The consent is given “on behalf of itself and its Users.”
Not stated here
The text does not say where Meeting Features run, whether recordings or transcripts are kept, or for how long.
Legal Rights & Agreement Rules · Restriction or exception
Customer must give notices, obtain consents and follow the law for meeting participants, and stop if consent is refused
If the Customer or its Users use Meeting Features, the Customer represents, warrants and agrees that it will, and will make its Users, provide all required notices to and obtain all required consents from all meeting participants. It must also comply with applicable laws, regulations, contractual obligations and organizational policies on communications, privacy, interception, wiretapping, consumer protection, recording, monitoring, transcription and processing of communications, and must not use Meeting Features in a way that violates anyone's privacy or other legal rights. The Customer decides whether notice or consent is required for a particular meeting, and must not begin the affected activity, or must stop it, if a required 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; and (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
Applies “If Customer or its Users use Meeting Features.”
Organizational policies matter only “if applicable.”
Not stated here
The laws and policies named are examples; the text does not say which apply to a given meeting.
Legal Rights & Agreement Rules · Restriction or exception
Provider says it provides technology only for meetings, not legal advice, interception or recording
The Provider says it provides technology only. It does not give legal advice, does not act as an interceptor or recorder, and does not guarantee that any use is legal.
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 text does not say whether the Provider's own systems capture, store or process meeting audio or video when Meeting Features are used, or where that happens.