Last updated: 7 November 2026
Usage access (Android): used solely to detect which app is currently in the foreground, so Prayer Unlock can notice when an app you chose to lock is opened. This check happens entirely on your device. We do not read screen content, log your app usage, or transmit any of this information anywhere.
Display over other apps (Android): used solely to show the prayer-reminder screen over an app you chose to lock. Nothing is recorded or transmitted.
Notifications: used for the blocking service's required status notification and, if you start a free trial, a single reminder before the trial ends. Notifications are scheduled on your device.
The app's network requests are the prayer generation below, and the Firebase Analytics and TikTok measurement described under Analytics and advertising.
Generated prayers are saved to your journal on your device. We do not keep copies.
Purchases are processed by Google Play (or the Apple App Store) and managed through RevenueCat, our subscription-management provider. RevenueCat receives an anonymous app-user ID and purchase receipt data — which plan was bought, when it started, whether it is still active — to confirm your subscription. It never receives your name or your payment details. On Android, RevenueCat also receives your advertising ID and IP address, so that when a free trial turns into a paid subscription we can report it to TikTok (see Analytics and advertising). See the RevenueCat privacy policy.
This record is kept, and that is deliberate. Because Prayer Unlock has no accounts, a subscription record held against an anonymous ID is the only way your access can come back if you reinstall the app or move to a new device. It is retained for as long as we need it for that purpose and to meet billing, tax, and fraud-prevention obligations, including after a subscription is cancelled. It is not linked to your identity and is not used to build a profile of you.
Prayer Unlock does not show ads. We use Google Analytics for Firebase to measure installs and subscriptions that come from our Google Ads campaigns.
That SDK collects an advertising ID, an app instance ID, and campaign events. first_open is recorded automatically the first time the app is opened. After a successful subscription purchase we record start_trial (a free trial) or purchase (a paid start), including the plan's currency and price. Those events are shared with Google Ads so we can tell which ads led to an install or a subscription. Google describes its handling of this data in the Google privacy policy.
We also record which setup screens are reached, so we can see where people stop: onboarding_step (the name of each setup screen, and when setup is complete), paywall_step (each subscription screen shown, whether prices had loaded, and whether a free trial was on offer), subscribe_tap (the plan chosen when the subscribe button is tapped), and purchase_failed (the reason a purchase did not complete, such as cancelled or a store error code). These events never include your name, your answers to the setup questions, or any prayer text. Like the events above, they are sent with the app instance ID and the advertising ID.
TikTok (Android). We use TikTok's App Events SDK to measure installs and subscriptions that come from our TikTok ads. It records when the app is installed, when it is opened, and whether it is opened again on the following days. After a successful subscription purchase we record StartTrial (a free trial) or Subscribe (a paid start), including the plan's currency and price. A free trial that turns into a paid subscription happens on Google Play's servers rather than in the app, so our server reports that Subscribe to TikTok when RevenueCat tells us about it, with the same advertising ID and IP address. These events are sent to TikTok with the advertising ID, the Google Play install referrer, an anonymous SDK ID, your IP address, and device details (model, operating system version, screen size, language, and app version), so TikTok can tell which ads led to an install or a subscription. We have switched off the SDK's optional collection of screen views, taps, and on-screen text. TikTok describes its handling of this data in the TikTok privacy policy.
On Android, you can reset or delete your advertising ID in your device's Google settings, which stops it being linked to these events. On iPhone, Prayer Unlock does not ask for permission to track you, so iOS does not share Apple's advertising identifier (IDFA), and these events are sent without it.
Your prayer journal, prayers, and locked-app list stay on your device. They are not sent to Firebase, Google Ads, or TikTok.
We also see aggregate subscription figures — how many people subscribed, renewed, or cancelled — through the RevenueCat dashboard, calculated from the purchase records described above. These are counts, not a record of how you use the app.
Uninstalling Prayer Unlock permanently deletes everything held on your device: your prayer journal, streak, prayer times, locked-app list, Bible reading position, and onboarding answers. That deletion is immediate and irreversible — we hold no backup, so there is nothing for us to restore.
The exception is the subscription record described above, which is held by Google Play (or Apple) and RevenueCat rather than on your device. It survives an uninstall by design, so that reinstalling returns the access you paid for. To stop a subscription, cancel it in your Google Play or App Store account settings; cancelling ends future billing but does not erase the purchase record, which those providers retain for their own billing and tax purposes.
Prayer Unlock is a general-audience app and is not directed at children under 13. We do not knowingly collect personal information from anyone, including children.
If we change how the app handles data, we will update this page and the "last updated" date above before the change takes effect.
Questions? Contact us.