A new feature is almost ready to ship-until someone asks, "What are we collecting here, and why?" The room goes quiet, the backlog freezes, and suddenly nobody is sure whether the design is just a little pushy or edging into surveillance territory.

Teams rarely lack ethics. They lack time, structure, and a shared way to say "this goes too far" while work is still in motion. Lengthy privacy manuals don't help during sprint planning, and legal reviews usually arrive when the build is already done.

Designing Against Surveillance turns high-level privacy principles into concrete, sprint-ready tools: focused checklists, decision trees, UX copy patterns, and one-page data maps that slot directly into backlog grooming, design reviews, and release gates. Instead of arguing from fear or abstract regulation, product managers, designers, and engineers can point to simple, reusable standards baked into their normal workflow.

Learn how to minimize data without breaking personalization, design sign-ups and logins that don't become tracking infrastructure, keep location and real-world signals on a tight leash, and give users real choices with clear, honest copy. A three-step mini audit and lightweight metrics show where risk is accumulating and how to respond before it turns into a crisis.

Written for product designers, product managers, and founders of consumer apps-especially teams too small for a dedicated privacy function-this compact playbook helps reduce surveillance risk while still shipping features on time.