Skip to content

Legal

Privacy Policy

How PrayLock handles private prayer data, Community posts, purchases and diagnostics, and how to request deletion.

Last Updated: October 12, 2026

Who we are

PrayLock is provided by Ruvix Ltd. Contact praylock@ruvixlabs.com about privacy, access or deletion. This policy covers our iPhone and Android apps; features and providers can differ by version.

Private prayer and app protection

Your personal prayer lists, notes, Bible bookmarks and Rule progress are stored on your device. They are separate from Community. Android uses Usage access to detect the foreground app and Display over other apps to show the prayer gate; selected apps and gate settings are stored locally. On iPhone, Apple Screen Time permissions support shielding. PrayLock does not create or read your Screen Time passcode. You can revoke permissions in your device settings. Explicit sharing sends the content you select to the destination you choose.

Community data

When live Community is enabled, Firebase Authentication assigns an account identifier. Firebase Firestore and Cloud Functions process your Community profile/display name, posts, comments, likes, reports, blocked-user preferences and optional progress-board entry. Posts and comments may reveal religious beliefs or other personal information. Publish only what you intend other Community users to see; private prayer notes are not automatically posted.

Public Community content is visible to other users. Content moderation and abuse prevention process submitted text and reports. We do not sell your prayer content.

Purchases and providers

Apple or Google processes payments. RevenueCat processes a separate randomly generated app user identifier, purchase/receipt and entitlement information to provide subscriptions and restore purchases. PrayLock does not receive your payment-card details. Firebase provides Community, Remote Config, App Check and Crashlytics services. These services process identifiers, device/app information and diagnostics as needed for their functions. Crashlytics handles crash reports; Remote Config delivers configuration; App Check helps verify genuine app requests. We use these providers to operate, secure and troubleshoot the app, not to claim that all app data stays on your device.

Purchase measurement

Our configured purchase-measurement integrations process RevenueCat purchase events, transaction amounts and pseudonymous app user IDs through AppRefer and advertising partners such as Meta to measure advertising results. Private prayer notes and Community post or comment text are not included in this purchase-event pipeline. Firebase configuration and security services also process country and locale information, IP addresses and installation identifiers. The Android app does not request GPS location permissions.

Storage and retention

Remote service requests use encrypted HTTPS connections. We retain Community data while needed to provide Community until you remove it or request deletion. Moderation/security records may be retained to investigate abuse and protect users. Purchase records may be retained by stores and subscription providers for transaction, fraud, legal and restore purposes. We do not promise deletion of records that a provider must retain under its obligations.

Access and deletion

You can remove posts/comments and delete your Community account in supported app versions. Older versions may offer content deletion only, which retains the account/profile. See Delete your PrayLock Community account to request deletion from outside the app. Local private data can be removed through the relevant app controls or by clearing app storage/deleting the app, subject to your device backup settings.

Deleting Community data or the app does not cancel a subscription. Manage renewal in Apple or Google Play subscriptions. Contact us for access/correction/deletion requests; never send passwords or passcodes.

Changes

We update this policy when our practices change and show the revision date above.