Reels & Shorts Blocker (“Nemu”, “the app”) helps you avoid short-form video by counting and blocking the Instagram Reels and YouTube Shorts screens on your device. This policy covers the app, the optional account, and the subscription.
What the app processes on your device
To recognise the Reels/Shorts screens, the app uses an Android accessibility service that reads the view IDs (internal layout identifiers) of exactly two apps: Instagram (com.instagram.android) and YouTube (com.google.android.youtube). The service is configured at the operating-system level so it does not receive events from any other app.
The accessibility service reads view IDs only. It does not read, store, or transmit the content of your screen, your messages, your passwords, or anything you type.
What we collect
The app requires an account. You sign in with Google on first launch, and your counts and settings are synchronised so they survive a reinstall or a new device. Counting and blocking themselves run entirely on-device and keep working with no network — but there is no way to use the app without signing in first.
| Data | When | Why | Where it goes |
|---|---|---|---|
| Email address, name, profile photo | On sign-in with Google | To identify your account and restore your subscription on a new device | Supabase (our backend) |
| Daily counts of Reels/Shorts viewed, per app | While you use the app | So your history follows you to a new device | Supabase |
| Your settings (mode, daily limit) | When you change them | Same | Supabase |
| Purchase token, order ID, subscription status, billing country | If you subscribe | To verify the purchase with Google and keep your subscription working | Supabase; the token is checked against Google Play |
| Promo code you enter | If you enter one | To apply the discount and credit the influencer who referred you | Supabase |
| Play Store install referrer | On first launch | To credit the influencer whose link you used | Supabase |
| Hashed IP address, request counts | On backend requests | To stop abuse of promo codes and the purchase endpoint | Supabase; IP addresses are stored only as a one-way hash, never in the clear |
| App usage events — which screens you open, which buttons you tap, sign-in outcomes | While you use the app | To understand which parts of the app people actually use and where they get stuck | Google (Firebase Analytics) |
| Crash and error reports — stack traces, and coarse state like whether the accessibility service was on when it happened | Only if the app crashes or hits an unexpected error | To find and fix bugs | Google (Firebase Crashlytics) |
| Device model, OS version, app version, a random installation identifier | Automatically, alongside the above | Firebase's baseline diagnostic data | Google (Firebase) |
We never collect the content of your screen, your browsing history, your contacts, your location, advertising identifiers, or anything from apps other than Instagram and YouTube — and analytics/crash reporting is no exception: neither ever receives what you watched, your counts, or anything read from Instagram or YouTube by the accessibility service.
What we do NOT do
- No advertising, and no advertising SDK in the app.
- No selling or sharing of personal data for anyone else's purposes.
- No profiling and no automated decisions that affect you.
- Analytics and crash reports are diagnostic only — they never decide anything the app does; blocking and counting behave identically whether or not either can reach Google's servers.
Payments
Subscriptions are sold through Google Play Billing, and Google processes the payment. We never see your card, UPI ID, or bank details. We receive a purchase token, an order ID, and the subscription's status, which we check against Google's servers to keep your subscription working.
Who processes data for us
| Processor | What for |
|---|---|
| Supabase | Database, authentication, backend functions |
| Google — Play Billing and Play Developer API | Payment processing and purchase verification |
| Google — Sign-In | Authentication, if you choose to sign in |
| Google — Firebase (Analytics, Crashlytics) | Usage analytics and crash/error reporting |
How long we keep it
- Account data and history: for as long as your account exists.
- Purchase and payment records: seven years after the transaction, because tax law requires it. These survive account deletion, with identifying fields removed where we are able to remove them.
- Rate-limiting counters: two hours.
- Analytics events and crash reports: governed by Google's own Firebase retention settings, not ours — typically a few months, after which Google deletes them automatically.
Your choices and rights
- Delete your account — in-app, from Profile → Delete my account, or from our account deletion page, which works without installing the app. Deletion happens 30 days after the request: signing back in during that window automatically cancels it and keeps your account exactly as it was. Once the 30 days pass, we remove your profile, settings, and history. Deletion does not cancel a Google Play subscription — cancel that separately in the Play Store, or it will keep renewing.
- Export your data — email us and we will send you everything we hold about you.
- Withdraw consent by signing out and deleting your account.
Children
The app is not directed at children under 13, and we do not knowingly collect data from them.
Changes
Material changes to this policy will be announced in the app before they take effect.
Contact
Questions about this policy, or a data request: team@nemuapp.in