A permission prompt can be meaningful.
The twentieth one before lunch may be less so.
Modern devices and websites ask people to make a constant stream of choices about cookies, notifications, location, microphones, cameras, contacts, advertising, personalization, tracking, analytics, and data sharing.
In theory, each prompt creates control.
In practice, attention is finite.
Repetition turns judgment into habit
A useful consent decision requires at least three things:
- the person notices the request,
- understands enough about what it means,
- and cares enough in that moment to evaluate it.
Repeated prompts make all three harder.
A person trying to read an article may not want to become a part-time privacy lawyer first. Someone installing a transit app may simply need the bus schedule. If the interface repeatedly interrupts the task, the shortest path through the interruption becomes attractive.
That does not prove every acceptance is meaningless.
It does mean clicking Accept becomes a weaker signal of considered agreement when the environment trains people to click through routine interruptions.
Research presented at the FTC’s PrivacyCon has examined cookie-consent interfaces and found that design, timing, placement, and the mechanics of changing a decision affect how usable consent actually is. See “Okay, whatever”: An Evaluation of Cookie Consent Interfaces.
The title captures the problem rather well.
More prompts do not automatically create more control
Imagine a system that asks separately about:
- analytics,
- personalization,
- advertising,
- location,
- notifications,
- nearby devices,
- background refresh,
- and partner sharing.
Granularity can be valuable.
But if every feature generates a new interruption, the system can bury important choices inside a pile of trivial ones.
The person eventually learns a behavioral rule:
Make the popup go away.
That is not the same mental process as evaluating whether a company should collect precise background location for six months.
Reducing requests can improve the requests that remain
Android’s current privacy guidance tells developers to minimize permission requests and use alternatives when an app can perform a function without broad access. It also recommends requesting only the level of location access actually required. See Android’s permission-minimization guidance.
That design philosophy has a privacy benefit beyond reducing technical access.
It preserves attention for the moments when permission genuinely matters.
A camera app asking to use the camera is unsurprising.
A calculator asking for precise background location deserves more thought.
If every app asks for everything, the second case can begin to feel as routine as the first.
Consent fatigue is therefore not an argument against giving people choices.
It is an argument against treating human attention as infinite.
A permission system succeeds only when people can still tell which questions deserve an actual answer.