Find an answer

Sources and verification

Inspect the evidence behind claims, their review dates and the limits of verification.

On this pageWhat “reviewed” meansFour evidence statesHow to keep the guide currentCentral fact register

What “reviewed” means#

We review product information in official documentation and announcements. A review date means the relevant source was read; it does not mean a feature was personally tested. This edition did not test a signed-in Slovak account or local checkout.

Methods, prompts and practice materials are original editorial guidance. Example results are illustrative. We distinguish a public list price from the final checkout amount, and specify product, platform, plan and region for feature claims.

Four evidence states#

  • Documented: an opened official source describes a capability or rule within the stated scope.
  • Gradual rollout: the source describes phased or limited availability.
  • Availability unverified: evidence for a particular account, region or platform is missing.
  • Source conflict: opened sources disagree in a way that cannot safely be reconciled.

No Grok feature is labelled personally tested in this edition. When official sources disagree, we retain both references and explain the uncertainty.

How to keep the guide current#

For a changing claim, open the linked source and check its date and scope. Before a purchase, the current checkout and your account’s terms are decisive. A newer article may describe a different product or region.

The register records the last review; it is not live product monitoring. Significant edits appear in the change history.

Found outdated information? A useful correction includes the chapter URL, the specific sentence and a newer official source. For account differences, record platform and plan, never credentials. Guide author: Martin Clone.

Central fact register#

Model used in the API example

Separate API billing

Text API rates

Cost of an individual API request

API rate limits

API training and data retention

Regional API endpoints

Imagine projects and library

Canvas for writing

Connector access

Personal and team workspaces

Grok Build in the terminal

Tagging @bot on X in Europe

Public subscription prices

API access and billing

Legacy and new subscriptions

Unifying accounts

Managing plans and usage

Cancelling a subscription

Migration with app-store billing

Shared weekly usage

Credit and extra-usage caps

Usage reporting versus API billing

Regional availability

Privacy rules by product

Training and personalization controls

What private chat means

Training in private chat

Public conversation links

Sharing within a team

European users’ data

Data controls on X

Access to Grok on X

Separate API data rules

Deleting accounts and data

Where you can use Grok

Web-app controls

Slovak text responses

Slovak interface language

Slovak in voice mode

Models in consumer Grok

Models for developers

Memory, custom instructions and Canvas

The older Grok Studio name

Supported attachments

Visual content in documents

Image creation and editing

Current video generation

Differences in video information

Media labels and provenance

Voice in consumer Grok

Voice model scope

Connectors and permissions

Google Drive controls

Scheduled automations

Skills for documents

Building an app with Grok Build

Grok Bot as a separate product

Plans with Bot access

Approvals and Auto Review

Bot’s connected accounts

Cursor and Bot data settings

Cloud computer and data deletion

Bot availability for Slovakia

Bot skills and routines

Bot attachment limits

Bot projects, Pages and outputs

Sources and verification scope

Practical guide · Editorial update: 24 Oct 2026

    Product claims are based on publicly opened sources. We did not personally test a signed-in Slovak account. Prompts are original examples; sample outputs are illustrative.

    Search the guide

    Try “privacy”, “files” or “subscription”. Accents are optional.