Mobile applications may request access to your camera, microphone, contacts, photos, location, or other information.
Some permissions are necessary for the features you want to use. Others may be optional.
A navigation application may need location information while providing directions, for example, but that does not automatically mean every application needs access to your location all the time.
Modern mobile operating systems often let users grant permissions only while an application is being used or limit access to selected content.
Reviewing permissions periodically can help you understand what information applications can access.
Which permission requests concern you most?
Do you usually review them before installing an application, or only when something seems unusual?
What would make permission explanations easier for everyday users to understand?
THE TAA COMMUNITY FORUM
Real People.
Real Conversations.
A Fairer Tomorrow.
Meet people, share experiences, ask questions, exchange ideas, and explore conversations about everyday life, consumer issues, businesses, technology, and more.
β
Open Discussions
β
Evidence Matters
β§
Everyone Welcome
β
Fairness for Both Sides
54
Open discussions
140
Visible posts
10
Conversation categories
App permissions: what should you review before tapping Allow?
One feature I appreciate in modern permission systems is the ability to give access only when a particular function needs it.
It is also useful when an application explains why a permission is requested before showing the operating system prompt.
That gives people some context instead of forcing them to guess.
Should security applications include a central dashboard where users can review potentially unnecessary permissions across their installed applications?
THE CONVERSATION CONTINUES
Add Your Perspective.
Join the conversation by signing in with your TAA account.