Privacy Policy
Your data, kept small.
In short: Namaz First has no accounts. Your location and the apps you block stay on your phone. We never read your screen, messages, photos or keystrokes. We send app-usage analytics, crash reports and subscription records, linked to device IDs (not your name), to run and improve the app, and we measure which of our ads brought you here. No ads inside the app. We never sell your data.
Who we are
Namaz First (the “app”) is published by EpowerX Labs Private Limited, Bangalore, Karnataka, India (“EpowerX”, “we”, “us”). We are the Data Fiduciary for the personal data described here under India’s Digital Personal Data Protection Act, 2023 (“DPDP Act”).
Contact: support@namazfirst.com
What stays on your phone
This information is processed on your device only. It is never sent to us or to anyone else.
Approximate location
We ask for approximate (not precise) location to calculate the five daily prayer times for where you are. The calculation happens on your phone. We may save your city name on the phone so the app can show it and work offline. You can instead set your city by hand, and you can turn location off at any time in Android Settings.
Apps you choose to block
You pick which apps should wait at prayer time. That list is saved on your phone only.
Usage access and “Display over other apps”
Why we use them: the app lock needs two Android permissions. Usage access tells the app which app is in front, so it knows when you open one of the apps you chose to block. Display over other apps lets it show the prayer screen at prayer time, or the short Quran verse screen between prayers, on top of that app.
What the app sees: with Usage access, Android lets the app read which apps were opened and when (app package names and times). Namaz First only uses this to check whether the app in front is one you chose, while the lock is on. It is checked on your phone, is not stored, and never leaves it. “Display over other apps” only lets the app draw its own screen; it does not let the app see what other apps show.
What we never do: we never read the content of your screen, your messages, photos, passwords or keystrokes. We do not collect, store or share your app usage, and we don’t use it for ads or analytics.
While the lock is on: Android requires a small, silent notification while the app watches for your chosen apps. It shows the next prayer and a countdown. If you turn off the verse gate between prayers, it only runs during prayer times.
Your choice: the app explains this before you turn them on. Without them, app blocking can’t work, but you can still get prayer reminders. You can switch them off any time in Android Settings (Apps → Special app access → Usage access, and Display over other apps).
Settings and prayer marks
Your app settings and your “I’ve prayed” marks are stored on your phone.
Notifications
We ask for notification permission to play the adhan reminder at each prayer time, a short “lock in 10 min” note before a prayer lock, and a silent card with the next prayer and a countdown (you can turn the card off in the app under Me). Home-screen widgets show the same prayer times. All of this is worked out on your phone. You can turn notifications off in the app or in Android Settings.
What leaves your phone
We collect only the following, through our own analytics servers and trusted service providers. None of it includes your name, email address or phone number, your location, or the apps you block. It is linked to device IDs: the Android ID that Android gives this app on your phone (or a random ID the app creates if that is missing), an anonymous app user ID, and, for ad measurement, your phone’s advertising ID.
| Data | Why | Provider |
|---|---|---|
| Product analytics | Which screens you open and what you tap, your onboarding answers (for example which prayers you tend to miss and your estimate of hours per day on your phone), paywall events such as viewing plans or starting a purchase, widget and notification taps, plus app language, install date and country. Used to understand and improve the app. | OpenPanel, run on our own servers; the same events also go to Google Analytics for Firebase |
| Install and ad attribution | When the app first opens: the Google Play install referrer (which link or campaign the install came from) and, if you came from a Facebook or Instagram ad, the referrer those apps hold. The Meta SDK reports the install and app open with your advertising ID and basic device details so Meta can tell which ad led to it. We don’t send Meta your in-app activity. | Google Play, Meta (Facebook) SDK, Google Analytics for Firebase |
| Subscription status and purchases | Whether you have an active plan, which plan, its price and renewal dates, linked to an anonymous app user ID and to the device and attribution IDs above (advertising ID, Android ID, IP address, the Meta and Firebase IDs, our analytics ID, install referrer and basic device details). Used to unlock the app and restore your purchase. When you buy, our server tells Meta and Google that a purchase happened (plan, price and these IDs) so we can measure which ads work. | Google Play Billing, RevenueCat, our servers, Meta, Google |
| Crash reports | What went wrong when the app crashes, with an installation ID. Used to find and fix bugs. | Firebase Crashlytics (Google) |
| Offer timer | When your 70% first-year offer was first shown, stored against a one-way scrambled (hashed) code derived from your device’s Android ID, so the 3-hour timer is honest and doesn’t restart. It can’t be turned back into your device ID and isn’t used for anything else. | Firebase Cloud Firestore (Google) |
These services also receive basic technical information needed to work, such as device model, Android version, app version, language, time zone, mobile network and country, and your IP address when your phone connects to them. We do not use your IP address to identify you.
Payments are made through Google Play. We never see or store your card, UPI or bank details. Google’s handling of your payment is covered by the Google Privacy Policy. Meta’s use is covered by the Meta Privacy Policy.
What we never do
- Show ads inside the app.
- Sell or rent your personal data.
- Read your screen content, messages, photos or keystrokes.
- Send your location or the list of apps you block off your phone.
- Ask for your name, email or phone number to use the app.
Why we use your data, and how to say no
We don’t ask a separate yes/no question for analytics. From the first time you open the app, it sends the product analytics, crash reports and install measurement described above (OpenPanel, Google Analytics for Firebase, Firebase Crashlytics, the Google Play install referrer and the Meta SDK’s install and app-open report). We rely on:
- Providing the app you chose (contract): unlocking and restoring your subscription, the offer timer, and keeping the adhan and the prayer lock working.
- Our legitimate interest: finding and fixing crashes, seeing which screens help or confuse people, and knowing which ads bring installs and purchases, so the app can stay free of in-app ads. We keep this to the data in the table above, which never includes your name, contact details, location or the apps you block.
- Your permission, for phone features: location, notifications, Usage access and “Display over other apps” are each explained in the app before Android asks you, stay off until you allow them, and are used on your phone.
To object or stop, at any time:
- Uninstall the app. Nothing more is sent from your phone after that. (Google Play and RevenueCat still tell us about an active subscription’s renewals until you cancel it.)
- Ask us to delete what we hold, with your Support ID. See Delete your data.
- Reset or delete your advertising ID in Android Settings → Privacy → Ads (Settings → Google → Ads on some phones), or turn on “Opt out of Ads Personalization” on older phones. After a delete the app and Meta get no advertising ID; after a reset the new ID isn’t linked to the old one.
- Turn off a permission in Android Settings. Some features then stop working (blocking needs Usage access and “Display over other apps”).
- Email us to object to a particular use. We’ll stop it unless we need it to provide the app or the law requires it.
Stopping doesn’t undo processing done before.
Who we share data with
With the service providers named above (RevenueCat, and Google for Play Billing, Firebase Analytics, Crashlytics and Firestore), who act as our Data Processors under contract and may use it only to provide their service to us. Our analytics (OpenPanel) runs on our own servers. For ad measurement we share the install and purchase events and IDs described above with Meta and Google, who also use them under their own privacy policies. We may also disclose data if Indian law or a lawful order requires it. These providers may store data on servers outside India, including in the United States. Where we do so, we follow the DPDP Act and any transfer restrictions notified under it.
How long we keep it
- On your phone: until you clear the app’s storage or uninstall it.
- Analytics (OpenPanel, Firebase): up to 24 months, then deleted.
- Crash reports: about 90 days, then deleted automatically.
- Subscription records: while your subscription is active and afterwards only as long as needed for refunds, disputes, and tax and accounting law.
When data is no longer needed for its purpose, or you object or withdraw a permission, we delete it unless the law requires us to keep it.
Your rights
Under the DPDP Act you have the right to:
- Access a summary of the personal data we hold about you and how we process it, and know who we’ve shared it with.
- Correct, complete or update it.
- Erase it. See Delete your data.
- Object, or withdraw a permission you gave, at any time (see above).
- Nominate someone to use these rights for you if you die or become unable to.
- Raise a grievance with us, and then with the Data Protection Board of India.
To use any of these, email support@namazfirst.com. Because we don’t know who you are, please include your Support ID (in the app: Me → About → Support ID, tap to copy) or your Google Play order number (it starts with GPA.) so we can find your records. We may ask you to confirm the request comes from you.
Contact
EpowerX Labs Private Limited, Plot No. 77, JBR Tech Park, 6th Rd, Whitefield, EPIP Zone, Bangalore, Karnataka 560066, India
Email: support@namazfirst.com
We acknowledge complaints within 48 hours and resolve them within 30 days. If you’re not satisfied, you may complain to the Data Protection Board of India.
Security
Data on your phone stays in the app’s private storage. Everything sent to our providers is encrypted in transit (HTTPS/TLS). We limit access to the data to what’s needed to run the app. If a breach affects your personal data, we will inform you and the Data Protection Board as the law requires.
Children
Namaz First is meant for adults aged 18 and over. We don’t knowingly process data of children. If you believe a child is using the app, email us and we’ll delete the related data.
Changes
If we change this policy, we’ll update the date above and, for important changes, tell you in the app before they apply. If we ever want to use your data for a new purpose, we’ll ask for your consent first.