Security

Your code stays on your machine.

Groking is built so the agent runs where you already trust the hardware. We never train on your code. Approvals decide what the shell can touch. Payments never see your card.

Local by design

Grok Build executes on your computer — your folders, your Grok/xAI account, your network. Project files, sessions, and transcripts live in a local database on that machine. Groking does not upload your repositories to train models, and we do not retain your source code on our servers.

Approvals control shell & file access

Every command and sensitive write can require your say-so. Pick a mode that matches the risk of the task:

askPrompt before each shell command and risky action.
editsAuto-apply file edits; still ask before running shell.
alwaysTrusted allowlists run without a prompt. Use carefully.

Recommended default: Auto edits · ask to run — Grok can write files, you approve what executes.

🔑 Auth cookies & login

  • Passphrase and license session cookies are marked HttpOnly (not readable by page scripts).
  • Login is rate limited to blunt brute-force attempts.
  • License activation is scoped to the machine you install on.

Network surface

The workspace server binds to 127.0.0.1 by default — only processes on that machine can reach it. When you expose it remotely (phone, another laptop), put TLS in front. A common setup is a Cloudflare Tunnel so traffic is encrypted end-to-end without opening a raw port.

$ Payments

  • Card: processed entirely by Stripe. Card numbers never touch Groking’s server.
  • SOL: receive-only Solana address. You send; we confirm on-chain and issue a license. No private keys on our side.

Hardening tips

← Back to home Open workspace Install Changelog
© 2026 Groking Compare · Terms · Privacy · Support