From Settings Overload to Contextual Controls: Privacy UI for a Health App

Tech · 5 min read

Users were overwhelmed by a unified privacy dashboard listing dozens of toggles and legal jargon. Interviews revealed people wanted simple, contextual choices — control at the point of data collection — rather than centralized settings they rarely understood. The product team reframed privacy as an interaction design problem: move decisions into flows and make defaults privacy-preserving.

The redesign introduced contextual privacy chips adjacent to data inputs, one-click explanations, and tiered defaults (Private, Share with clinician, Research opt-in). Designers prototyped flows where consent was requested inline and could be changed per item, with a lightweight summary screen for users who wanted a single place to review decisions. Usability tests showed comprehension doubled and users felt more empowered because choices were explained where they mattered.

After rollout, support tickets about 'lost permissions' dropped 38%, and the product's privacy opt-in for research increased modestly because the inline explanations emphasized benefits and safeguards. The engineering team reused a permissions API to support both contextual toggles and the summary view, keeping synchronization consistent. The project highlights that simplifying privacy often requires moving from a centralized control model to contextual, just-in-time decisions.