Accessibility Service Disclosure — CompareMyKart

Last updated: 6 May 2026

This page is referenced by Google Play to verify the legitimate use of the Android Accessibility Service inside CompareMyKart. It is also linked from inside the App during the consent flow.

1. What is an Accessibility Service?

Android offers an Accessibility Service API to help users with disabilities — for example, screen readers for visually impaired users, switch-control apps for motor-impaired users, and similar assistive tools.

Beyond strict assistive cases, Google also permits Accessibility Services for purposes that directly benefit the user when no alternative API exists, provided the use is fully disclosed and the user has explicitly consented.

CompareMyKart uses an Accessibility Service for one specific purpose: to read the items currently displayed in your cart on supported food-delivery apps, so that the App can compare prices for those exact items on competing platforms.

2. Why we need it (and not some other API)

Major Indian food-delivery apps (such as Zomato) do not provide a public API that lets a third-party app read the user's current cart. Without such an API, the only feasible way to know what is in your cart is to read what the cart screen is displaying. Android's Accessibility Service is the only sanctioned mechanism on Android for reading on-screen content from another app.

We have evaluated and rejected the alternatives:

Public APIs of delivery apps — do not exist for cart introspection by third parties.
Screen-recording / screenshot APIs — invasive, capture far more than necessary, and are not designed for structured data extraction.
Asking the user to manually retype every item — defeats the purpose of a one-tap price comparison.

Accessibility Service, restricted to the cart screen of one specific app at the moment of the user's tap, is by far the least-intrusive technical solution available.

3. Exactly what we read, and only when

When the Accessibility Service is enabled by you and you are looking at the cart screen of a supported delivery app:

You tap the small floating CompareMyKart button (a foreground overlay).
At that moment — and only at that moment — the Accessibility Service reads the text content of the visible cart screen.
The structured data extracted is: restaurant name, restaurant address, item names, item quantities, item prices, applied coupons (if shown), subtotal, delivery charges, and total.
This structured data is sent to our backend server over HTTPS, which uses it to query the equivalent items on other delivery platforms.
Comparison results are displayed to you. The captured cart data is retained only as long as needed to debug failures (≤ 30 days), then automatically purged.

That is the complete scope. The Accessibility Service is never used for any other purpose.

4. What we DO NOT do

We do not read screens of any app you have not explicitly chosen to compare.
We do not read keystrokes, passwords, OTPs, or any credential.
We do not capture screenshots, photos, or video.
We do not run silently in the background — the service activates only on your tap.
We do not sell, share, or repurpose the captured cart data for advertising, profiling, or any non-comparison use.
We do not monitor banking apps, messaging apps, or any app outside the small list of food-delivery apps the user has explicitly opted into.

5. Your control

The Accessibility Service is opt-in. You must:

Open Android Settings → Accessibility
Find "CompareMyKart"
Toggle it on
Confirm in the system dialog

You can disable it at any time by reversing those steps. CompareMyKart's other features (saved addresses, account profile) continue to work without the Accessibility Service — only the price-compare feature requires it.

6. Supported food-delivery apps

Currently supported (this list grows over time, with corresponding App updates):

Zomato (com.application.zomato)
Swiggy (in.swiggy.android) — limited to cart-bar capture
Magicpin (com.magicpin)
EatClub (com.box8.android.app)

The Accessibility Service is configured to filter events from these package names only. Events from any other package are dropped immediately at the OS level.

7. Data flow diagram

[Your phone]
   ├─ You're on Zomato cart page
   ├─ You tap the CompareMyKart floating bubble
   │
[CompareMyKart Accessibility Service]
   ├─ Reads the visible cart screen text
   ├─ Extracts: restaurant, items, quantities, prices, total
   │
[CompareMyKart App]
   ├─ Sends structured cart JSON over HTTPS to our backend
   │
[CompareMyKart backend (api.comparemykart.com)]
   ├─ For each supported alternative platform:
   │     ├─ Looks up the matching restaurant on that platform
   │     ├─ Reads the menu, applies your saved address
   │     ├─ Computes equivalent total with platform's coupons
   │
   ├─ Returns price comparison to your phone
   │
[CompareMyKart App]
   └─ Displays "Cheapest: Magicpin ₹236.63 (vs Zomato ₹316.53)"

No data leaves the diagram boundary. No third-party advertising network, analytics broker, or unrelated service receives any cart content.

8. Independent verification

The full source code of the Accessibility Service component (the on-device parser) can be made available to Google's Play Integrity review team on request. The on-device parser is a small, deterministic component whose only output is structured cart JSON of the form { restaurantInfo, foodCart, checkoutTotal, couponInfo } — no free-form text, no images, no other data.

9. Contact

If you have any concerns about how the Accessibility Service is used, write to support@comparemykart.com with subject "Accessibility Concern". We respond within 7 days.