The access.
The boundaries.

iOS: Apple Screen Time

Screen Time access is required to protect selected apps. You approve Apple’s authorization prompt and choose apps in Apple’s picker. Apple supplies usage events and system shields; RageQuit runs the selected challenge inside its own app. It does not overlay effects on another app’s live screen or inspect its contents.

Saving an eligible rule starts protection. Usage events and updates can be delayed by iOS. On iOS 26.5 and later the shield’s Rage Bait button can open RageQuit; earlier supported versions direct you to open it yourself. After completion, switch back through normal iOS navigation.

Optional access stays optional

• Microphone: only Humiliation needs it. iOS can ask when you first hold the control. Allow access when prompted, then resume or play again if needed and hold to hum. Granting permission never starts recording by itself. Listening stops on release, exit or backgrounding. All other baits work without microphone permission.
• Notifications: optional alerts. Denying them does not disable protection or any Rage Bait.
• Motion and compass: visible challenges use available device sensors. Compass input does not request GPS location access.

You can complete setup with Screen Time access alone. Manage permissions in Rage HQ or iOS Settings. The Rage Code protects in-app rule changes; it does not replace the device passcode or prevent changes to iOS system controls.

Choose challenges that work for you

RageQuit includes spoken control labels, adjustable controls where supported, larger-text layouts and reduced-motion behavior. Individual tasks can still require precise touch, multiple fingers, hearing, vibration, memory or phone movement. Preview tasks before assigning them; this page does not promise that every bait works with every assistive technology or device.

iOS support · iOS privacy · iOS monitoring and output controls

Android: Accessibility access

The Android app uses its Accessibility service for the behavior described below. iOS does not use this service.

Why RageQuit needs this access

Your rules depend on knowing when a selected app is in use. Accessibility supplies app and window information so RageQuit can count eligible use, identify where an effect belongs, and display its own visual or interactive challenges. It also signals when the screen changes so effects can stop or move out of the way.

Android’s permission grants broad capabilities. RageQuit uses the limited information below for these features. Reading this page does not grant access: you must choose to continue in RageQuit and explicitly enable its service in Android’s Accessibility settings.

Information used during ordinary app use

• App identity: the package identifier tells RageQuit which app owns a window and whether you selected it for your Hit List.
• Window information: window identity, bounds, type, focus and visibility help place effects and distinguish ordinary use, split screen, floating video and Android system surfaces.
• Event information: window-change events and the occurrence of clicks or scrolling help keep the current app state and supported interaction effects up to date. RageQuit does not read the text attached to those events or the content of the item you clicked.

RageQuit does not read messages, typed input or the ordinary screen content of your selected apps. It does not walk through their content, capture screenshots, or record the screen. Its challenges receive touches on RageQuit’s own controls; it does not replay those gestures into the app underneath.

Managing stored data

On supported Android Settings pages, the app-storage management button opens RageQuit’s own Manage RageQuit storage screen. You can read what a reset removes without entering the Rage Code. Resetting from that screen requires a fresh Rage Code check and a separate explicit confirmation. If no Rage Code has been set, an explicit confirmation is still required.

This storage screen works independently of Accessibility. RageQuit does not read Android Settings screen text to manage storage. Opening App info or Storage, clearing the cache, uninstalling RageQuit and changing its Accessibility toggle remain available without a Rage Code. The code still protects configuration changes inside RageQuit.

This is a supported Android Settings route, not a guarantee against every reset. Uninstalling and reinstalling, privileged tools such as ADB, device recovery or manufacturer-specific routes can bypass this page. Clearing stored data or uninstalling removes RageQuit’s local records.

What is stored or shared

Accessibility observations are processed on your phone. RageQuit saves your selected apps, rules, tracked-use totals and necessary challenge progress locally. It does not save screen content or a click-by-click browsing history.

RageQuit does not transmit Accessibility information to G&K Studios LLC or an analytics service, and does not sell that information. Google Play billing uses network services separately from local app recognition and effects. Opening this website uses your browser’s network connection. See our privacy policy for local records, purchases and website handling.

Your choices and controls

Review access in Rage HQ → Update Rage Access. The app shows a separate Accessibility disclosure before taking you to Android’s settings. Agree and open settings records your agreement; opening a help link does not. You can cancel instead of enabling access. Accessibility, Notifications, Microphone and Media Playback are required to finish first-time setup.

The Rage Code protects changes to your rules. Android still owns permission controls, navigation and the service lifecycle. When required access is lost or RageQuit cannot safely identify the active app, affected tracking and effects pause.

Use Stop on a preview or Stop outputs in the active output notification to stop the corresponding session. Read output controls and their limits, including what a Stop action does to saved rules and Volume Drop.

Get help with access ↗