Prayer in Hand

Privacy

The app and this website have separate, deliberately limited data practices.

In the app

Prayer in Hand does not require an account and never transmits prayer text, intentions, practice history or private notes. Those records stay on your device, without app-operated cloud sync. If iCloud Backup is enabled, iOS may include local app data in your encrypted device backup.

StoreKit connects to Apple to load products, complete purchases, check entitlements and restore purchases. We do not receive your payment-card details. RevenueCat receives purchase and subscription data under its anonymous app user ID for subscription reporting and entitlement checks; automatic device-identifier collection is disabled. The RevenueCat SDK collects the Apple AdServices attribution token for Apple Ads campaign attribution. The token is sent to RevenueCat, not Umami, and does not include prayer content. The app does not use IDFA or IDFV or request permission for cross-app tracking. Local reminders use Apple’s notification system on your device.

Apple Ads measurement

The app measures our own Apple Ads with Apple's AdServices framework, without asking for permission and without using your advertising identifier (IDFA). Apple tells the app and RevenueCat, our purchase service, whether an install came from one of our ads and which campaign, ad group, keyword and ad it was. These identify our ad, not you. RevenueCat keeps this with its anonymous customer record. When a purchase, renewal, cancellation or refund happens, our server records the event type, product, price, these ad identifiers and, while analytics are on, the source category and campaign label. It does not record a customer ID, email or IP address.

App analytics

Anonymous usage analytics are on by default; turn them off any time in the app's Settings, under "Share anonymous usage analytics". They are anonymous: they are not linked to your name, email or Apple ID, there are no cookies, and the app never asks for tracking permission. For installs from our Apple Ads, they also carry the campaign, ad group and keyword IDs. Every request the app sends, including these anonymous counts, has a User-Agent with the iOS version (major and minor only, such as 18.5) and whether the device is an iPhone or iPad. Screen views, including anonymous ones, carry the name of the previous app screen as the referrer.

While analytics are on, the app creates a random install ID (a random UUID, not your name, email, Apple ID or advertising ID) the first time it runs and keeps it in the iOS Keychain on your device, so it survives a reinstall; it is not synced to iCloud. The same ID is used as the identifier for PostHog and Umami and is stored with RevenueCat as the attribute analytics_install_id, so a purchase can be matched to the same install. The app sends selected events with that ID to our self-hosted Umami server: app opens, generic screen names and the previous screen name, paywall and purchase activity, trials, offer codes, settings, error codes and usage-allowance events (the feature, how many uses were used, the limit and whether it is exhausted). These events also carry the app version and build version, runtime environment, consent state, language, App Store storefront country, and paywall and experiment variants. Purchase events send only a product label (annual, welcome_annual, trial_annual, lifetime or other) and the offer type, never App Store product or offer IDs. Exit and win-back offer events also send the RevenueCat offering ID, price and currency. It also records how you found the app: an Apple Ads install, a website, campaign or social bio link, a creator or offer code, or your answer to "How did you find Prayer in Hand?", including the short note you may add if you choose Other. That answer and note are removed when you turn analytics off. This attribution is sent as a source channel and detail, plus the Apple Ads campaign, ad group and keyword IDs for Apple Ads installs. Apart from iPhone or iPad, the app sends no hardware details. RevenueCat always receives a consent flag and the app environment (pih_env); while analytics are on it also receives the install ID and the source channel, source detail, media source and campaign, stored with RevenueCat's anonymous customer record. Our server does not pass your IP address to Umami, and Umami does not store IP addresses. We never send what you pray, your intentions, your practice history or your notes. There is no tracking across other apps or websites, no advertising and no data sale, and the app never asks for tracking permission. Turning analytics off stops those events, deletes the ID and source from your device and clears them at RevenueCat; nothing further is sent to Umami or PostHog. Turning them back on creates a new install ID. To delete data already collected, email hello@prayerinhand.com.

In PostHog, events are filed under RevenueCat’s anonymous app user ID (a random ID created by RevenueCat, not your name, email or Apple ID); the install ID above stays on each event as a property, and the two are joined after a purchase or restore. PostHog events also carry a random session ID, how long each screen was open, which rough part of the screen was tapped (one of 24 blocks, never coordinates and never what was tapped), the app version and build, iOS version, iPhone or iPad, language, App Store country and the names of any test variants. Screen recording is off today. If we switch it on for some installs of the App Store version, it saves small pictures of the screens you see with every piece of text, every text field and every image covered, so no prayer, note, name or email can be read in them. They are filed under the same anonymous ID, are used only to see where people get stuck, and stop with the analytics switch. Turning analytics off stops these events too.

Version 1.9 also sends SKAdNetwork conversion values to Apple. These are aggregate and are not linked to you.

Analytics providers

Anonymous usage analytics are on by default; turn them off any time in the app's Settings. While they are on, the usage events described above are sent to two analytics services that we operate or contract: PostHog (PostHog Inc., which stores the data on servers in the United States), which acts as our processor, and our self-hosted Umami server in the EU. They receive the screens you view, which features you use, the app version, your device type (iPhone or iPad), the approximate country of your App Store region, how you found the app (for example an Apple search ad) and the random install ID the app creates on your device. The country comes from your App Store region, never from your IP address or location. This data is anonymous: it is not linked to your name, email or Apple ID, it is not used for tracking or advertising, and it is not sold or shared with advertisers. The app does not use the advertising identifier, does not show a tracking prompt and, unless screen recording is switched on as described above, does not record your screen. Turning analytics off opts the app out of PostHog and deletes its install ID. Purchases are handled by Apple and RevenueCat as described above, not by these analytics services.

The Android app

On Android, your prayer history, private notes and rule of prayer are stored only on your phone. Reminders are local notifications from the phone itself. Anonymous usage analytics work as described above and are on by default: PostHog and Umami receive the screens you view, which features you use, the app version, the session length and a random install ID the app creates. Your prayers, notes and intentions are never sent. How you found the app comes from the Google Play install referrer campaign, or from your answer to "Where did you hear about us?" if you choose to give one. Turning analytics off in Settings opts the app out of PostHog and deletes the install ID. The Android app does not use the advertising ID and does not record your screen. Purchases are handled by Google Play and RevenueCat, which receives an anonymous ID and the install ID so that a purchase can be matched to the same install. You can manage or cancel a subscription in your Google Play subscriptions.

Optional email updates

If you choose to subscribe, we collect your email address, canonical consent wording and version, app version, a separate random email-only ID, confirmation and activity timestamps, and (only when analytics consent is granted) an acquisition source category and short campaign detail. We use these details to send daily prayer, saint or reading updates and occasional win-back reminders timed by app opens. Our lawful basis is your consent under GDPR Article 6(1)(a). We send a confirmation link before starting updates; opening it does not change your subscription, and you must press the confirmation button. You can unsubscribe using the button on the email page or its one-click email control. Email records are kept while you are subscribed; unsubscribed records are purged at the first hourly cleanup after 30 days. Unconfirmed requests are deleted at the first hourly cleanup after 3 days. If email delivery is enabled, Amazon SES in a US region processes delivery for us. To request an export or deletion, or withdraw consent, email hello@prayerinhand.com; we respond within 30 days.

On this website

This website uses a self-hosted, cookieless Umami service for page views and App Store button clicks. The website analytics do not receive app prayer activity. We do not use this site for cross-site advertising profiles.

We use Sentry for technical server-error reports from this website. Reports exclude submitted message bodies, request queries, cookies and authentication headers, and are not connected to prayer records.

Messages you send

If you email support, we receive your address and what you choose to include. We use it to respond. Do not send prayer notes or other sensitive information. You can request deletion of support correspondence at hello@prayerinhand.com.

Last updated: 8 November 2026