LAPD lets contract with surveillance giant Flock expire, citing ‘serious concerns’ over civil liberties and privacy

LAPD will let its three-year Flock Safety contract expire without renewal, citing “serious concerns” over civil liberties and privacy/data-sharing, after stating it needs contractual terms to address data privacy, security, and sharing. Multiple U.S. cities have already stopped using Flock cameras over similar privacy concerns, and the company has faced backlash tied to reported false positives and security lapses (including exposed cameras and lack of multi-factor authentication), adding downside risk to Flock’s government customer pipeline.

Analysis

This is less about one canceled contract than about a procurement regime shift. Municipal buyers are increasingly treating data retention, auditability, and misuse liability as first-order features, which raises sales friction for any vendor whose value proposition depends on frictionless data collection. The near-term read-through is negative for small-cap gov-tech names with concentrated public-sector exposure, because renewals get slower and discount rates rise when customers expect bespoke legal review.

The second-order impact is broader than surveillance: integrators, cloud storage, and analytics vendors can all face tighter contract language around access controls, MFA, deletion rights, and geographic restrictions. That usually compresses gross margin if vendors must absorb compliance engineering, but it also advantages firms that already have strong governance processes. For DTST, the key question is whether it has any regulated/public-sector mix; if it does, bookings visibility should be haircut until the company proves it is selling governance and retention controls, not generic infrastructure.

The contrarian take is that headline backlash can be overdone if churn is political rather than economic. The bigger risk is not immediate revenue loss, but a slower 6-18 month decline in addressable market assumptions as city councils and legal teams bake privacy review into every renewal. Falsifier: if management later guides to stable public-sector pipeline and no elongation in sales cycles, this is noise rather than thesis.

Key Decisions for Investors

• No immediate position in DTST; wait for the next earnings call / 10-Q to quantify public-sector exposure and renewal cadence. If regulated/customer concentration is material and bookings weaken, fade any relief rally rather than buying the dip.
• Relative-value expression: long CIBR / short DTST over 1-3 months if procurement scrutiny starts favoring security/compliance vendors over data-collection-adjacent names. Keep sizing small; stop out if CIBR fails to outperform on the next privacy/regulatory headline.
• If DTST later discloses meaningful municipal or regulated-storage revenue, consider a tactical short on a 5-10% post-news bounce. Risk/reward improves only if management cannot clearly show no contract losses or no sales-cycle elongation.
• Set an alert for any follow-on city exits from similar contracts. A multi-city pattern would turn this from idiosyncratic noise into a structural re-rating risk for public-sector tech multiples.