# Why Does Quietube Need Accessibility Permission?

When you first set up Quietube, Android requests permission to enable the
Quietube Accessibility Service. Many users are understandably cautious about
granting accessibility permissions to applications. This article provides
complete transparency regarding why Quietube requires this permission and how
your privacy is protected.


WHY IT IS REQUIRED

On the Android operating system, standard apps run in strict isolated sandboxes.
A normal application cannot detect if you accidentally tapped on Instagram or
opened short-form videos in Google Chrome. The Android Accessibility API is the
only official, battery-efficient mechanism that allows Quietube to:

 * Inspect the Active Foreground App: Detect when a blocked entertainment app is
   opened during an active Quiet Session.
 * Monitor Browser URL Bars: Read the active URL address in browsers like
   Chrome, Firefox, and Brave to intercept short-form video loops without
   blocking your ability to research educational articles on Wikipedia or Google
   Scholar.
 * Provide Instant Redirection: Minimize the distracting screen and immediately
   return you to your lecture.


WHAT QUIETUBE NEVER DOES (PRIVACY GUARANTEE)

Quietube's accessibility service is strictly hardcoded to uphold total student
privacy:

 * Zero Keystroke Logging: Quietube does not monitor, read, or record what you
   type. Passwords, messages, and search queries are completely untouched.
 * No Screen Recording: Quietube does not capture your screen or view private
   photos or chats.
 * Zero Data Transmission: The accessibility engine operates 100% locally on
   your phone. No app usage statistics or browsing histories are ever sent to
   remote servers.

Quietube exists to protect your focus, not monitor your personal life.