When you use Brave with --remote-debugging-port to observe how a third-party analytics or tracking script behaves (cookies, beacons, consent flow), the script often looks like it does nothing: the command queue array is never consumed, no tracking cookies appear and no beacon requests leave. There is no console error. Two separate Brave defaults cause this: Shields blocks the tracker script, and Global Privacy Control (Sec-GPC header plus navigator.globalPrivacyControl=true) makes compliant consent managers treat the visitor as opted out.

HiveBrain was designed with shared/cloud mode as the default behavior. When TURSO_URL was set, it connected to cloud automatically. The --local flag was an opt-in for privacy. This created a bad default: new users submissions would go to a shared database without explicit opt-in.