Grok Bot approvals, security, and privacy

Set a boundary in your request

Tell the Bot what it may do and where it must stop. A strong pattern from official guidance: draft and recommend first; do not send, publish, purchase, delete, change permissions, change production, or accept legal terms without your go-ahead.

An approval covers the proposed action. It does not undo work already finished.

Review an action

When approval is required, the chat shows the proposed operation and its inputs. Check the target, scope, and values before you approve.

• Desktop: Allow once · Deny · Always allow (can save a matching rule)
• Mobile: Allow · Deny · Always allow when a rule is proposed

Don’t approve anything whose target or effect you can’t identify.

Auto Review

With Auto Review on, Grok Bot evaluates tool calls and computer actions before they run. In settings, look under Settings → General → Bot → Auto-review (wording may vary slightly by app version).

• Ask first rules always stop matching actions for you
• Allow automatically rules proceed only when automated review finds no other reason to stop
• If both match, Ask first wins
• Team-enforced rules (Enterprise) can appear locked; your personal rules may only make behavior stricter

Write narrow rules (for example: ask first before external email). Avoid “allow everything in the browser.” Auto Review is model-based — it adds a layer; it does not replace least privilege or clear boundaries in the request.

Secrets and taking control

Passwords, passkeys, two-factor codes, CAPTCHAs, and payment confirmations belong in computer takeover — not in ordinary chat. For supported connections, use the product’s secure secret request (masked; kept out of the transcript/model) when available.

Shared-computer privacy

All of your Bots share one cloud computer. Files, browser sessions, and CLI credentials can be available across your roster.

• Don’t use “a different Bot” as a security boundary
• Sign out when access should end; clear sensitive temp files; revoke connectors in the source service
• Deleting a Bot does not wipe shared-computer files or browser sessions. If the Bot is merely silent, wait before you delete — see When your Grok Bot gets stuck

Sharing a Bot isn’t sharing your computer

A public share link lets others copy configuration. It does not share your computer or logins. Still: don’t put secrets, customer data, or internal URLs in a Bot you share. Adding a third-party bot accepts the third-party bot terms (as-is; the platform does not verify or endorse third-party bots).

Local computer

Separate from the cloud computer. Typical policy choices: ask every time (default), always allow, or never allow. Official docs lean toward never allow unless you have a specific reason. Team admins can cap the policy; the stricter setting wins.

Privacy and your account

• Grok Bot needs cloud data storage; Legacy Privacy Mode is not supported and blocks Grok Bot
• Privacy and training follow your Cursor account / team settings
• For current account, team, and data-handling policy, use the official security and privacy pages

Teams (quick pointer)

On Teams / Enterprise plans, admins get extra controls (org-wide enablement, network controls, enforced Auto Review, audit options, and more — availability depends on plan). Self-serve Teams may not see every Enterprise panel. A dedicated Teams guide will come later; until then, use official Teams and security docs for rollout.

Practical least privilege

Connect only the tools you need · prefer scoped accounts where supported · start read-only / drafts · keep send, publish, purchase, delete, and production changes behind approval · review connectors and routines when sources change · pause routines when workflows shift.

Related Botski pages

• What is Grok Bot?
• What Botski is
• Shared computer security for beginners
• When your Grok Bot gets stuck

Sources

Fetched 2026-09-18 CT.