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
- Anthropic report: AI agents rebuilt malware to dodge detection, ran 4,700 fake dating personas — bigaiguy · 2026-09-11
- Anthropic Report: Criminals Used Claude to Run Hacks, Spy Ops and Influence Campaigns — bigaiguy · 2026-09-11
- Why So Many AI Researchers Think the Machines Could Kill Everyone — wiredmagazine · 2026-09-11
- California creates standards for independent AI auditors to verify lab safety testing — VraserX · 2026-09-11
- a16z podcast: why 2-3 person startups are absent from policy debates — a16z Podcast · 2026-09-11
- Researcher questions AI safety eval firm, citing 'blatantly sloppy' security and monitoring — Kyrannio · 2026-09-11