Published 3 months ago • loading... • Updated 3 months ago
Elon Musk’s Grok Faces a Trust Crisis After Developers Flag a Major Privacy Concern
Cereblab said the CLI transmitted full Git histories and deleted secrets until a server-side flag stopped the uploads, and Musk promised to delete prior data.
On Sunday, Cereblab reported that the Grok Build CLI was uploading entire repositories to Google Cloud Storage, prompting SpaceXAI to implement a global flag stopping the transmissions.
Grok Build, launched alongside Grok 4.5 as a secure tool, was transmitting data roughly 27,800 times greater than the coding task required, exposing full Git history and secrets.
Cereblab tested the CLI by instructing it to reply with "OK" and not open any files, yet the tool transmitted entire repositories unlike Claude Code or Cursor, which open individual files.
Elon Musk promised all user data uploaded before the fix would be "completely and utterly deleted," while technical staff Andrew Milich and Jason Ginsberg repeated company assurances.
SpaceXAI documented a Zero data retention policy, yet no independent audit has confirmed the deletion, and confusion persists about the per-session retention toggle that did not fix the issue.