# What an Android accessibility service can and cannot see

An Android accessibility service is a permission that can let an app observe events on your screen, read on-screen content and act on your behalf. What a given service actually reads depends on how the app is built, so check its disclosure and grant the permission only to apps you trust.

URL: https://nyutonlabs.in/guides/what-android-accessibility-services-can-see  
Last updated: 8 November 2026

Many apps that count or limit what you do inside other apps ask for the accessibility permission. Before you grant it, understand what it allows. This guide explains the permission in general, how to check which apps have it, how to turn it off, and what a trustworthy disclosure should say. It ends with exactly what Ippo's service reads.

## What is an Android accessibility service?

An accessibility service is a background component that an app registers with Android so it can be told what is happening on screen and act on it. It exists to help people with disabilities use their phones, for example by reading the screen aloud or controlling the phone with switches.

The same capability is useful for other purposes. An app that needs to know when something happens inside another app, such as a video starting, often has no other reliable way to find out. That is why tools that count or limit app use frequently rely on it.

## What can an accessibility service see?

Depending on how it is configured, an accessibility service can be notified of events such as which app or window is in front, when content on screen changes, and when you tap or scroll. If the app asks for it, the service can also read the text and structure of what is on screen.

An app declares what its service wants when it is built. The main settings are:

| Setting | What it controls |
| --- | --- |
| Event types | Which kinds of events the service is told about, such as window changes or scrolling |
| App filter | Whether the service listens to all apps or only named ones |
| Window content access | Whether the service can read the text and layout of what is on screen |
| Actions | Whether the service can act, such as pressing Back or Home, or tapping on your behalf |

A service that listens to every event in every app, with window content access, can see a great deal. A service that listens only to a few event types in a few apps, and reads nothing beyond that, sees very little. Both use the same permission. The permission itself does not tell you which kind you are dealing with.

## What can an accessibility service do?

It can act as well as observe. A service can perform system actions such as going Back or to the Home screen, and on recent Android versions it can perform taps and gestures. This is how assistive tools let someone control a phone without touching it.

It is also how a limiting tool can stop you at a set point: it notices the event and sends you somewhere else, such as the home screen.

## Why is the accessibility permission considered risky?

Because it is broad. A service with full access could read anything shown on screen in any app and act as if it were you. Android shows a warning when you turn a service on for this reason. The risk is not the permission itself. The risk is granting it to an app that does more with it than it says.

Treat it like a house key. Do not hand it out casually.

On recent Android versions, an app installed from outside an app store may need an extra step in Settings before its accessibility service can be turned on. This is a deliberate safety measure. Do not work around it for an app you do not trust.

## How do I check which apps have accessibility access?

Open the accessibility section of your phone's Settings and look for the list of installed or downloaded services. Every app listed there with its switch on has an active accessibility service.

The exact path varies by phone maker and Android version. A common route:

1. Open **Settings**.
2. Tap **Accessibility**.
3. Look for a section named something like **Installed apps**, **Downloaded apps** or **Installed services**.
4. Read the list. Each entry shows whether the service is on or off.

If you cannot find it, search Settings for "accessibility".

Do this now. Look for anything you do not recognise or no longer use.

## How do I turn off an accessibility service?

Open the service in the accessibility list and switch it off. The app keeps its other permissions, but it can no longer use the accessibility service until you turn it back on.

1. Go to **Settings**, then **Accessibility**.
2. Open the installed services list.
3. Tap the app.
4. Turn the switch off and confirm.

Uninstalling the app also removes its service. Some apps that depend on the service will stop working properly without it. That is expected.

## What should an app's disclosure tell me?

A trustworthy app tells you, before you turn the service on, exactly what it reads, what it never reads, why it needs the service, and whether anything leaves your phone. Vague wording is a warning sign.

[Google Play's policy](https://support.google.com/googleplay/android-developer/answer/10964491) requires apps that use the accessibility API for anything other than helping people with disabilities to show a prominent disclosure inside the app and get your consent with a deliberate action, such as a tap to accept. The disclosure must appear in the normal use of the app, not only in the store listing or on a website, and the use must also be documented in the app's Play listing. Read that disclosure. Then compare it with the privacy policy.

### Questions to ask before you grant it

- **What exactly does the service read?** Look for a specific list, not "screen content".
- **What does it never read?** Messages, passwords and the content you view should be named.
- **Does it read window content, or only events?** Events are much narrower.
- **Which apps does it listen to?** All apps, or only the ones it needs?
- **Does anything leave the phone?** Is there an account, a server or uploads?
- **Is the data sold or shared?**
- **Do the disclosure and the privacy policy say the same thing?** If they differ, trust neither.
- **How do you delete the data?**

If an app cannot answer these plainly, do not grant it the permission.

## Why do screen-time apps need this permission?

Because Android's general app usage data shows which app was open and for how long, not what happened inside it. To count individual reels, a tool has to know when a new reel starts. That event happens inside another app, and an accessibility service is the standard way to be told about it.

This is also why a tool that only measures app minutes cannot give you a reel count. See [how to measure your real reel time](/guides/measure-your-real-reel-time) for why the count matters more than minutes.

## What does Ippo's accessibility service read?

Ippo, a reel counter and limiter for Android, counts the reels you watch and stops the next one when you pass your daily limit. It uses an Android Accessibility Service for this, its core purpose.

Ippo's accessibility service reads only event metadata: that a reel was watched, and which app it was in. It does not read what you watch, messages, passwords or anything else on the screen.

Ippo's main service appears in Android's accessibility settings as **Ippo reel counter**. It is not limited to particular apps in its configuration, so Android sends it accessibility events from every app. For each event, Ippo looks at two things only: the name of the app and the type of event. It uses them to recognise a reel in Instagram and ignores everything else. It cannot read what is on your screen: the setting that would allow that (`canRetrieveWindowContent`) is turned off.

| Ippo reads | Ippo never reads |
| --- | --- |
| That a reel was watched | What you watch |
| Which app it was in | Your messages |
| | Your passwords |
| | Anything else on the screen |

When you pass your daily limit, Ippo blocks the next reel and sends you to the home screen.

### What about the web guard?

The web guard is an optional, paid feature. It is a second accessibility service, off by default. If you turn it on, Ippo also reads the web address in the browser's address bar to tell that a new reel started. The address is never saved, logged or sent anywhere. It reads nothing else on the page. See [Ippo's web guard](/ippo/web-guard) for the supported browsers.

### Where does the data go?

Nowhere. Everything stays on the phone. Nothing is uploaded or sold. You can delete all of Ippo's data by clearing the app's data or uninstalling it.

The full wording is in the [Ippo accessibility service disclosure](/ippo/accessibility) and the [Ippo privacy policy](/ippo/privacy). The two say the same thing, word for word. Ippo is coming soon to Google Play. Start at [Ippo: reel counter and limiter for Android](/ippo).

## The short version

- The accessibility permission can allow an app to observe and act on your screen.
- What an app actually reads depends on how it is built. The permission alone does not tell you.
- Check Settings, then Accessibility, for the list of active services. Turn off what you do not use.
- Before granting it, read the disclosure. Look for a specific list of what is read and never read.
- Grant it only to apps that answer plainly and keep data on the phone.

For why a limit needs a hard stop in the first place, read [why you scroll without deciding to](/guides/why-you-scroll-without-deciding).