Finding the story behind the story…

Chapter 1 of 5▾

1The Boston Mistake: How Pilot Programs Leak Before Launch2Inside Flock: The Vendor Building America's Surveillance NetworkNot ready3The Data Sits Unguarded: Why Security Gets ForgottenNot ready4When Cities Wake Up: Boston's Reckoning and What Came AfterNot ready5The Pattern Nobody Wants to See: Why This Will Happen AgainNot ready

Why Surveillance Systems Leak Before They Launch

The Boston Mistake: How Pilot Programs Leak Before Launch

A Boston street at dusk with traffic lights and parked cars, a traffic camera mounted on a utility pole in sharp focus, its dark lens reflecting city lights while a data stream of license plate numbers glows faintly across the asphalt below.

Boston drivers had no idea their movements were being recorded. License plates, timestamps, locations—all feeding into a trial system called Flock. The company promised security. The city believed them.

Then the data leaked.

Not through a sophisticated hack. Not stolen by a rival intelligence agency. The files simply sat exposed on an unsecured server, accessible to anyone with the right link. City officials would later call it a "vendor error." A slip. A mistake made during setup.

But the timing was darker. The breach happened during the pilot phase—before Boston had finished deciding whether to keep the system at all. Before the public debate. Before real safeguards could be installed.

Flock eventually left Boston. The city canceled the contract. Yet the question lingered: If a surveillance vendor couldn't protect data during a careful trial run, what would happen once the cameras were permanent? What fails when the stakes are highest?

Keep reading.

Create a free account to unlock the next chapter, save your progress and choose your narrator.

Your first chapter is always free.

Back to feed