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
- Should platforms serve third-party AI agents? The antitrust question — sjgadler · 2026-10-27
- Thieves spoofing GPS steal $100M+ in data center cargo since June — Ars Technica AI · 2026-10-27
- Johns Hopkins Alerts 3,000+ Patients After Data Was Sent to an AI Tool — beingmodest · 2026-10-27
- Alignment Hub launches with 120+ documented AI misbehavior incidents and a reporting template — Thom_Wolf · 2026-10-27
- US senator slams AI industry for proposing 50-death threshold for 'catastrophic incident' — peterwildeford · 2026-10-27
- Dev training a guard model to block prompt injection, tool and memory poisoning — gnukeith · 2026-10-27