Last updated: July 27, 2026
This Privacy Policy describes how Quiet Lock (“Quiet Lock,” “we,” “us,” or “our”) collects, uses, discloses, and otherwise processes information when you use our mobile application (“App”) and related services we offer through the App (collectively, the “Service”). The operator of the Service is the developer entity identified on the App’s page in the Apple App Store (the “Developer”).
By using the Service, you agree to this Privacy Policy. If you do not agree, please do not use the Service. Please also read our Terms of Service, which govern use of the App.
This policy applies to the Service. It does not apply to third-party websites, apps, or services that may be linked from the Service or to Apple Inc.’s processing of information through iOS, Screen Time, the App Store, or system permissions (see Section 8).
Depending on how you use the Service, we may process the categories below. Unless stated otherwise, data described in Sections 2.1–2.2 and 2.5–2.7 is stored locally on your device using Apple’s on-device storage frameworks (for example, SwiftData and app storage). If you opt in to iCloud Backup (Section 2.8), selected user data syncs through Apple’s iCloud private database—we do not receive that content on our own servers. We do not transmit prayer text or similar User Content to servers we operate. Limited technical data is sent to our analytics and diagnostics providers as described in Sections 2.3–2.4 and 2.6. If you contact us by email, we receive that correspondence as described in Section 2.1.
Screen Time shielding. Although Quiet Lock uses Apple’s Screen Time–related APIs to shield apps or categories you select, the Developer does not have access to, and the App does not collect, any information regarding the specific content or user activity within the apps chosen for shielding. Enforcement relies on Apple’s system frameworks and tokens as designed by Apple.
We use TelemetryDeck (TelemetryDeck privacy information) to understand aggregate product usage—for example, app launches, onboarding steps completed, screen views, tab selections, and high-level events such as subscription paywall interactions. TelemetryDeck acts as our processor under its terms and documented data-processing arrangements.
What we send. Event names and coarse parameters (for example, which screen was viewed, which tab was selected, coarse age band, coarse subscription state, and locale or region derived from device settings). TelemetryDeck’s SDK also attaches standard technical metadata (for example, app version, device model, OS version, language, and broad region) as described in TelemetryDeck’s documentation.
What we do not send. We design our integration so that analytics payloads do not include prayer text or prayer point text, display names, email addresses, advertising identifiers, or precise GPS location.
Identifiers. TelemetryDeck uses privacy-oriented techniques (such as hashing on the device) rather than collecting your name or Apple ID. Session identifiers are generated by the SDK to understand usage within a visit.
Storage location. TelemetryDeck processes data on infrastructure located in the European Union (Germany).
In the European Economic Area, United Kingdom, and Switzerland, we rely on TelemetryDeck’s privacy-by-design approach and applicable legal bases (including legitimate interests in understanding aggregate product usage, and consent where required). You can contact us with questions or objections as described in Section 11.
We use Sentry (Sentry privacy policy) to receive crash reports, app-hang signals, and certain non-fatal errors so we can fix bugs and improve stability. Sentry acts as our processor under its terms and documented data-processing arrangements.
What we send. When the App or a related extension crashes or records a handled error, Sentry may receive technical diagnostics such as stack traces, error codes or messages, app and OS version, device model, environment tags (for example, whether the event came from the main App or a Screen Time extension), and limited diagnostic breadcrumbs (for example, that a block schedule save failed—without prayer content).
What we do not send. We configure Sentry not to attach screenshots or view hierarchies, and we do not intentionally include prayer text, display names, or similar User Content in diagnostic reports. Do not include sensitive spiritual reflections in free-text fields you know may be echoed in system error messages.
Storage location. Our Sentry organization is configured for EU data storage; diagnostic data is stored at rest in Frankfurt, Germany.
We rely on legitimate interests (and, where applicable, legal obligation) in maintaining a secure, reliable Service. This processing is separate from advertising and we do not use Sentry for cross-app tracking.
If you purchase a subscription or other paid feature through the App Store, Apple processes payment and provides us limited information (such as subscription status indicators) as described in Apple’s terms and documentation. We do not receive your full payment card number. Subscription performance analytics are described in Section 2.6; Apple remains the merchant of record for App Store charges, cancellations, and refunds.
We use Superwall (Superwall privacy information) to help us understand subscription and purchase performance—for example, purchases, free trials, renewals, cancellations, and refunds. Superwall acts as our processor under its terms and documented data-processing arrangements. Superwall does not process your payment card or charge your Apple ID; Apple remains the App Store merchant of record.
What we send / may be processed. Technical purchase-related signals observed from Apple’s StoreKit on the device; subscription lifecycle events Apple may forward to Superwall through App Store Server Notifications (for example, renewals, billing issues, cancellations, and refunds); an opaque identifier (a randomly generated UUID stored on your device—not your name, email, or Apple ID); and coarse attributes such as age band, locale or region derived from device settings, and subscription state. Superwall’s SDK may also attach standard technical metadata (for example, app version, SDK version, and device or OS attributes) as described in Superwall’s documentation.
What we do not send. We design our integration so that Superwall does not receive prayer text or prayer point text, display names, email addresses, advertising identifiers, precise GPS location, or payment card numbers.
Storage and transfers. Superwall may process data on infrastructure outside the European Union (including the United States). Where personal data is transferred across borders, we rely on appropriate safeguards under applicable law (such as standard contractual clauses) and our arrangements with Superwall.
We rely on legitimate interests (and consent where required) in understanding subscription performance and maintaining the Service. This processing is separate from advertising and we do not use Superwall for cross-app tracking.
The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. See Section 9.
If you enable iCloud Backup in the App’s Settings, selected user-owned data stored in SwiftData (for example, profile and onboarding preferences, prayer points, Soul statistics such as prayer days and stillness time, Bible verse highlights, last-read Bible chapter, and related in-app settings) syncs through Apple’s iCloud private database associated with your Apple ID. We do not operate our own cloud servers for this feature. Apple processes and stores this data under Apple’s privacy policy and iCloud terms.
What syncs. Profile, prayer points, Soul progress metrics, Bible highlights (book/chapter/verse references and colors you choose—not the bundled scripture text), last-read Bible location, and related user settings in our sync-enabled database.
What does not sync. Block schedules and Screen Time shield selections remain on each device because Apple’s Family Controls tokens are not portable across devices. Bundled prayer, verse-of-day seed catalog content, and offline Bible translation files stay in local-only stores and are not uploaded to iCloud.
Your control. iCloud Backup is off by default. Turning it on or off requires restarting the App. Resetting local data from the recovery screen, resetting Soul progress from Profile, or deleting the App clears data on this device; with iCloud Backup enabled, deletions may sync through CloudKit on a subsequent sync. Copies in iCloud may remain until you disable iCloud Backup and manage iCloud data through Apple’s settings where available.
If you open Feature Request & Feedback in Settings, the App loads a web view pointed at our Featurebase portal (quietlock.featurebase.app). Featurebase Inc. acts as our processor for that feature under its terms and documented data-processing arrangements. See Featurebase’s privacy policy.
What may be processed. When you use the portal, Featurebase may process information you choose to submit there (for example, feature requests, feedback text, and optional contact details if you provide them), along with technical metadata typical of a web session (for example, browser or web-view user agent, IP address, and session cookies as described in Featurebase’s policy).
What we do not send automatically. Opening the feedback portal does not transmit your prayer text, prayer points, display name, or other on-device spiritual content from the App to Featurebase. Only information you voluntarily enter in the portal is shared with Featurebase.
We use information to:
We do not use your spiritual reflections or prayer points to train generalized public artificial intelligence models. If that ever changes, we will obtain any legally required consent and update this policy materially in advance.
Where the GDPR or similar laws apply, we rely on one or more of the following:
We share information only as described below:
We do not sell personal information as defined under U.S. state privacy laws, and we do not share personal information for cross-context behavioral advertising as a “sale” or “sharing” absent a future feature that would require updated notice and, where applicable, opt-out or consent. We do not handle your prayer or similar on-device content for commercial sale or advertising profiling.
On-device data remains until you delete it within the App or delete the App from your device. If you use iCloud Backup, synced copies follow Apple’s iCloud retention and deletion behavior until you disable sync or remove the data through Apple’s tools. Email support communications are retained only as long as needed to resolve your request and for legitimate business or legal record-keeping. TelemetryDeck analytics events, Sentry diagnostic events, and Superwall subscription analytics events are retained according to our vendor account settings (typically on the order of months unless a shorter period is configured) in pseudonymous or technical form. You may contact us to ask about retention or exercise rights as described in Section 11.
We use reasonable administrative, technical, and organizational measures appropriate to the nature of the Service. Because the Service stores meaningful content on your device, you should protect device access with a passcode or biometric and keep your operating system updated. No method of storage or transmission is completely secure.
Certain features rely on Apple frameworks and system permissions. Blocking uses Apple’s Family Controls / Screen Time APIs based on apps and categories you select—we do not read the content of other apps. Optional local notifications may remind you at Personal Time moments you schedule and help hand off from a Screen Time shield to prayer; we do not use notifications to collect content from other apps.
Your use of Apple frameworks is also subject to Apple’s terms and privacy policy. Apple’s systems may impose technical or policy limitations that affect how or whether blocking features operate. Quiet Lock is not endorsed by or affiliated with Apple.
The Service is not intended for children under 13. If you believe we have inadvertently collected personal information from a child under 13, contact us at privacy@quietlock.app and we will take appropriate steps to delete it.
Users between 13 and the age of majority must have parental or guardian permission where required by local law.
Most personal data described in Sections 2.1–2.2 and 2.5–2.7 stays on your device; we do not receive the content of your local prayer flow unless you send it to us (for example by email). If you email support or privacy addresses, we receive that correspondence where our mail systems operate (which may include India or other countries depending on our mail provider).
TelemetryDeck and Sentry process limited technical and usage data in the European Union as described in Sections 2.3–2.4. Superwall may process subscription analytics outside the EU as described in Section 2.6. If you use the Service from the United States or elsewhere, information may be transmitted to and stored in the countries where our processors operate on our behalf. Where personal data is transferred across borders, we comply with applicable law, including notice, consent, or approved transfer mechanisms (such as standard contractual clauses) where required.
Depending on where you live, you may have rights to access, correct, delete, port, or restrict certain processing, and to object to certain processing or profiling. You may also have the right to withdraw consent where processing was consent-based.
To exercise rights, contact privacy@quietlock.app. We may need to verify your request consistent with applicable law. You may designate an authorized agent where permitted.
Deleting your data. The Service does not require a remote account. You can delete most on-device data by uninstalling the App, using in-app reset options (including the database recovery screen or Profile → reset Soul progress), or turning off iCloud Backup and managing iCloud data through Apple where available. Contact us if you need help exercising deletion or portability rights for data we process directly (such as support email).
Apple App Store purchases: Many billing and receipt questions are best directed to Apple Support in addition to contacting us.
On-device Bible text. The App bundles complete Bible translations for offline reading in the Bible tab. That text is stored on your device as part of the App installation. We do not upload Bible text or your Bible reading content to our servers. On-device state related to the Bible tab may include your last book and chapter and, when your app language is English, your preference among KJV, WEB, or BBE.
Attribution. The following public-domain translations may appear in the App, depending on your language settings:
For licensing disclaimers and additional terms about scripture text, see Section 12 of our Terms of Service.
California residents may request information about disclosure of personal information to third parties for their direct marketing purposes. We do not disclose personal information to third parties for their direct marketing purposes as defined by that law.
We may update this Privacy Policy from time to time. We will post the updated version here and revise the “Last updated” date. If changes are material, we will provide additional notice as required by law (for example, an in-app notice or email where appropriate).
Questions or requests: