What Is Usage Access on Android? What It Lets an App See

The permission, precisely

Usage Access is Android's name for the special permission behind PACKAGE_USAGE_STATS. It is not in the normal runtime permission list with camera and location. You grant it in a separate settings screen, one app at a time, which is why apps that need it have to send you there rather than showing a popup.

What it exposes is a log of app usage events, read through Android's UsageStatsManager: which package came to the foreground, which went to the background, and the timestamps. Aggregated over a day, that becomes the per app totals you see in Digital Wellbeing, which uses the same underlying data.

Usage Access in numbers

Usage Access has existed since Android 5.0 (API level 21), released in 2014, when Google added the UsageStatsManager class. According to Android's developer documentation, the system groups usage data into four time intervals: days, weeks, months and years. An app with the permission can ask for totals at any of those levels, which is how a screen time app can show today's minutes and a monthly trend without keeping a history of its own.

The detailed record is short lived. The individual events, each app opening or closing with an exact timestamp, are kept by the system for only a few days, according to the same documentation. After that, only the daily, weekly, monthly and yearly totals remain. Since Android 11, the system also returns no events after a restart until you unlock the phone for the first time, so an app cannot read your usage while the device is still locked.

Granting it takes one switch per app, in Settings, and there is no popup that can grant it by accident. Android's documentation is explicit that an app declaring the permission is not enough: "the user of the device still needs to grant permission through the Settings application". Turning the switch off takes effect immediately and changes nothing else about the app.

What it cannot do

This is the part worth being precise about, because the name invites the worst assumption.

• It cannot read your screen. There is no screen content in this data at all. Capturing the screen is a completely separate permission that shows a system warning and a persistent indicator.
• It cannot see inside apps. No posts, no messages, no usernames, no search terms.
• It cannot log keystrokes. That would require an input method or Accessibility.
• It cannot see web pages. It knows Chrome was open. It does not know which site.
• It is not location, contacts, photos or files. Those are all separate permissions that this one does not imply.

Usage Access versus Accessibility

These get confused constantly, and the difference is large. Accessibility Services exist so that screen readers and switch controls can work, which means they are extremely powerful by design.

If you are auditing a screen time app, this is the question to ask. An app that requests Accessibility for screen time is asking for the ability to read everything on your screen in order to do a job that Usage Access already covers. Google reviews that category closely for exactly this reason, and screen time apps have a long history of trouble there. The full comparison, including which popular apps use which, is in Accessibility vs Usage Access.

How to check and revoke it

1. Open Settings.
2. Search for Usage access, or go to Apps, then Special app access, then Usage access. The exact path varies by manufacturer.
3. You get a list of every app that has asked, with its current state.
4. Tap any app to turn it off. Nothing else about the app is affected.

It is worth reading that list once even if you never install a screen time app. Most people have granted it to something they have forgotten about. For which apps should be on that list, and the paths on Samsung, Pixel and Xiaomi, see is Usage Access safe.

Why a persistent notification usually comes with it

Android does not push an event when the foreground app changes for this kind of use, so an app that wants a live timer has to check repeatedly. Doing that reliably while you are inside another app requires a foreground service, and Android requires every foreground service to show an ongoing notification.

So the permanent notification is not the app being intrusive. It is Android insisting that anything running continuously in the background has to declare itself. An app that keeps a live timer with no notification at all is doing something you should look at more closely.

Common questions

What is Usage Access on Android?

Usage Access is a special Android permission, granted in Settings rather than through a popup, that lets an app read the system's app usage statistics: which app is in the foreground, when it opened and closed, and how long each app has been used. It does not give access to anything inside those apps or to the contents of the screen.

Is it safe to grant Usage Access?

The permission itself is narrow, exposing only which apps are open and for how long. The risk is not the data but the app you give it to, since usage patterns are still personal. Grant it to apps that keep that data on the device and explain what they do with it.

Can an app with Usage Access read my messages?

No. Usage Access carries no screen content and no text of any kind. Reading what is on screen requires an Accessibility Service or screen capture, both of which are separate and much more visible to you.

Why can I not find Doom Saver in the Usage Access list?

On Android 13 and up, apps installed from outside the Play Store have sensitive settings hidden behind a safeguard. Go to Settings, Apps, the app in question, open the menu in the corner and choose Allow restricted settings, then check the list again.

Does Usage Access drain my battery?

The permission itself costs nothing. Any battery cost comes from what the app does with it, specifically running a foreground service to check the current app. The work involved is small, and a well built app of this type is not a meaningful share of daily battery use.