Grok Build's Privacy Path Sparks Controversy
WesEklund · x · 2026-07-14
In a quoted discussion, the author questions Grok Build's privacy claims. Their own testing showed that while ZDR ultimately blocked an upload, the system still attempted to upload, implying this code path shouldn't have existed in the first place.
A cited reply counters that Grok Build's default settings are off, users can delete synced data via /privacy, and emphasizes that ZDR is maintained in both headless and interactive usage.
More from Safety
- Coding agents are heading toward an AI-writes, AI-reviews, human-approves workflow — aftahi_ai · 2026-07-22
- AI security course launches with a small cohort to train the next generation of hackers — wunderwuzzi23 · 2026-07-22
- OpenAI says long-horizon models need safety and alignment checks across full action sequences — rhiever · 2026-07-22
- Stanford HAI’s PNAS feature maps the legal questions around generative AI — StanfordHAI · 2026-07-22
- New Malware Lurking in Blind Spots Targets AI Infrastructure to Steal Data — Wired AI · 2026-07-22
- Generative AI Shatters SMB Security: Flawless Phishing and Voice Cloning at Scale — YvesMulkers · 2026-07-22