Grok Bot Terms

Grok · agreement dated October 31, 2026 · Official agreement

Read the agreement

7 of 34 cards in Account & Service Control

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.

Cross-references

Also annotated in the same passage (1)

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.
Also annotated in the same passage (1)

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

Cross-references

Also annotated in the same passage (1)

Account & Service Control · Permission or license

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.
Also annotated in the same passage (5)

Account & Service Control · Restriction or exception

Customer must delete or disable bots, remove data, revoke access and disable routines when no longer needed

The Customer is responsible for deleting or disabling bots, removing data, revoking access and disabling routines when they are 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 arises “when no longer required.”

Not stated here

  • The text does not say how the Customer removes data or revokes access, or whether the Provider removes anything itself.
Also annotated in the same passage (2)

Account & Service Control · Permission or license

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.
Also annotated in the same passage (1)

Account & Service Control · Permission or license

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.