People must know about awareness collection and be able to stop it
Aliases: in-context notice · revocable collection · sensor control
What it is
Informed and controllable awareness means people can tell, in the context of collection, whether data are being captured, which data, and for which audience, and can pause or stop collection without leaving the service entirely. Control must affect sensing, transmission, storage, and derivation—not merely remove an indicator from view.
Why it happens
Continuous sensing fades into the background, while permissions are often granted once during onboarding. In-context notice makes the data flow perceptible, immediate controls reduce the gap between intent and effect, and verifiable state prevents a false-off condition in which backend telemetry continues. Together they make participation revocable rather than a one-time agreement.
Studying it
Role-based walkthroughs should compare notices and controls with network and backend events. Longitudinal studies can test whether people remember scope, locate controls, and predict the consequences of stopping collection. Error rates, recovery cost, and coordination loss are useful outcomes; a high opt-in rate is not evidence of understanding.
Where it stops holding
Emergency safety, mandatory records, or critical infrastructure may constrain opt-out, but fields, duration, and viewers should remain narrow and accountable. Repeated notices can become ambient noise, while default-off sensing may remove necessary coordination cues. Organizational dependence also means that a visible button does not guarantee a pressure-free choice.
Applying it
- Show active sensors, recipients, and purposes where collection occurs, not only in settings.
- Offer pause, timed resumption, and field-level controls with concrete consequence previews.
- Verify control behavior across local state, network transmission, and backend records.
- Label non-optional collection with its basis, retention period, and appeal channel.