Crowdsourced surveillance camera avoidance map

What to build

A browser extension and mobile-friendly web map for privacy-conscious drivers, journalists, and gig/delivery drivers that overlays crowdsourced ALPR, Flock Safety, red-light, and municipal surveillance camera locations on a route planner, with zone alerts when entering a monitored area.

MapQuest just normalized showing ALPR camera locations to mainstream users, validating demand for surveillance-aware navigation while leaving an opening for a more complete, cross-network, privacy-first tool that incumbents are unlikely to build aggressively.

Demand

Privacy-conscious drivers, journalists, activists, and rideshare/delivery workers who want to know where they're being tracked are underserved by mainstream nav apps; the MapQuest feature's traction shows this crossing into mainstream awareness right now.

• Hacker NewsEngagement

  "MapQuest will now show you where Flock cameras are in your neighborhood" — 276 points, 51 comments on HN, indicating high engagement with the underlying idea of surfacing surveillance camera locations to everyday users.

• DeFlock (community ALPR mapping project)News

  Prior crowdsourced efforts to map ALPR and surveillance camera locations already exist and have built community contributor bases, showing people are willing to manually report camera locations absent any app prompting them.

Stack

• Mapbox GL JS or Leaflet
• OpenStreetMap data layer
• Supabase (crowdsourced submissions + auth)
• Flock Safety / municipal open-data feeds where available
• Chrome/Firefox WebExtension APIs
• Mapbox Directions API for route avoidance

Solo + AI difficulty

The map UI, extension shell, and basic crowdsourced-pin submission flow are straightforward for one person with AI help and could reach an MVP in 2-4 weeks; the hard parts are sourcing and maintaining accurate, legally defensible camera location data at scale and building route-avoidance logic that actually routes around zones rather than just displaying them.

Entry threshold

Low capital barrier; requires scraping or crowdsourcing camera location data (some already exists via projects like deflock.me or community spreadsheets) and a simple map UI, buildable solo in 1-3 weeks using mapping APIs; main friction is sourcing accurate, continuously updated location data without legal exposure.

Window

3-6 months

Where to find first users

• r/privacy and r/PrivacyGuides
• r/deliverydrivers and rideshare driver forums
• Product Hunt launch
• Journalism/security Twitter and Mastodon privacy communities

Competitors

• DeFlock

Counter-signals & risks

• If MapQuest's move is followed by Google Maps or Waze adding native camera overlays, a standalone tool loses its core differentiation to free, pre-installed incumbents.

• Publishing precise ALPR and surveillance camera locations may draw legal or political pushback from law enforcement and municipalities, risking takedown requests or liability.

• Crowdsourced camera data can be incomplete or stale since cameras are added or moved faster than community reporting, undermining reliability for route planning.