

Shut off and leave your phone at home, buy a pay-as-you-go to bring with you for emergency contact
/coordination
Leave the pay-as-you-go phone powered off too, and only power it up if you actually have to use it. If you have to use it once, you need to get a replacement for a future event.
I’m thinking perhaps something like Meshtastic transmitters and receivers should be used for coordination instead.







I wonder if a segregated system design could address this. Similar in-system segregation like a TPM for the actual detection/matching part of the system separated from the command and control part.
As in, the camera and OCR operations would be in their own embedded system which could never receive code updates from the outside. Perhaps this is etched into the silicon SoC itself. Also on silicon would be a small NVRAM that could only hold requested license plate numbers (or a hash of them perhaps). This NVRAM would be WRITE ONLY. So it would never be able to be queried from outside the SOC. The raw camera feed would be wired to the SoC. The only input would be from an outside command and control system (still local to our SoC) that and administrator could send in new license plates numbers to search against. The output of the SoC would “Match found against License Plate X”. Even the time stamp would have to be applied by the outside command and control system.
This would have some natural barriers against dragnet surveillance abuse.