Seattle writes its own broadband privacy rules requiring user opt-in before ISPs can share data, pushing back against US government; ISPs must comply by May 24
Hardly anyone was pleased by the rollback of the broadband privacy rule last month, opening up the possibility of ISPs collecting …
Context & Ripple Effects
Seattle's move is a direct response to a federal about-face: the FCC approved opt-in privacy rules for ISPs in October 2016 covering location, financial information, and browsing history, then voted in March 2017 to stay those rules before they took effect. With Washington stepping back, the city is re-imposing the same opt-in standard locally, with a May 24 compliance deadline.
It also fits a broader Seattle pattern visible in the coverage — the city has already moved unilaterally on Uber and Lyft driver pay, police surveillance tech, and dockless bike-share fees — making municipal government, not the FCC, the active regulator for tech platforms operating there.
First-order effects
- ISPs serving Seattle customers must build opt-in consent flows for sharing sensitive data like browsing history by May 24, effectively restoring the stayed FCC rules within city limits.
Second-order effects
- ISPs that lobbied for 'flexible' rules letting them innovate with customer data now face a patchwork: federal deregulation paired with city-level mandates that vary jurisdiction by jurisdiction.
Third-order effects
- If other cities copy Seattle, broadband privacy enforcement migrates from a single national regulator to dozens of municipal ones — costlier for ISPs but arguably stricter in aggregate.
The trend: As the FCC retreats from broadband privacy oversight, US cities are writing their own data rules, shifting platform regulation down to the municipal level.