Privacy Policy

• ·The publisher collects and stores no personal data on any server of its own.
• ·The text of the corpus is bundled with each client and readable without a connection.
• ·Your reading data and preferences are stored on your own device.
• ·Cloud sync, where offered, runs on your own platform account — iCloud on Apple devices, Google on Android — and the publisher cannot see it.
• ·Audio is never hosted by the App. It plays through Apple Music, Amazon Music or YouTube Music, under your own account with them.
• ·Notifications, where offered, are scheduled locally on your device.

• ·Reading data — your current reading position, bookmarks, and recently viewed sections.
• ·Preferences — chosen script and language, reading font, accent colour, appearance, and text size.
• ·Reminder settings — whether daily reminders are enabled, and the times you chose.

On the web, this is smaller and is held in the browser’s own local storage under three keys: dp.reading (script, text size, line spacing, theme), dp.auth.provider (which provider you signed in with, so recitations open in the right service) and dp.auth.prompted (that you have already been asked about signing in). A service worker also keeps a copy of the pages, fonts and corpus you have visited so the reader works offline. The web client has no bookmarks and no reminders. All of it is readable only by this site, in that browser.

• ·iOS / iPadOS — iCloud: if enabled, your bookmarks, reading position and preferences synchronise across your Apple devices through iCloud Key-Value storage, tied to your own Apple Account, under Apple’s privacy policy.
• ·Android — Google Drive / Play Services: if enabled, preferences and reading history sync through your own Google Account, including the account email or profile identifier needed to associate the data with it, under Google’s privacy policy.

The web client offers no cloud sync. Nothing it stores leaves your browser.

• ·iOS / iPadOS — Sign in with Apple: the user identifier and name Apple provides are stored locally on your device, under Apple’s privacy policy.
• ·Android — Google Sign-In: your basic profile identifier and email are stored locally on your device to enable bookmark and preference sync, under Google’s privacy policy.

The web client differs and the difference is worth stating plainly. Sign-in there is handled by Firebase Authentication, a Google service, using either your Google or your Apple account. Google processes the sign-in and holds the resulting account record on the publisher’s behalf, under Google’s privacy policy, and Apple’s if you sign in with Apple. The publisher never receives your password. On the web, signing in exists for one purpose only: to decide which music service recitations open in. No reading activity is attached to it.

• ·iOS / iPadOS — Apple Music: full tracks stream through MusicKit under your own Apple Music subscription. The App asks permission to interact with your Apple Music account. Under Apple’s privacy policy.
• ·Android — Amazon Music or YouTube Music: you may choose either. A subscription is not required for standard streaming, though Amazon Music Unlimited or YouTube Music / Premium may be required by those services for background playback when the app is minimised or the screen is off. Under Amazon’s or Google’s privacy policy.
• ·Web — Apple Music or YouTube Music: Apple Music plays in the page through MusicKit under your own subscription. YouTube Music plays in an embedded YouTube player, which receives the playback request and may set its own cookies in that frame. Under Apple’s or Google’s privacy policy.

The web client has no notifications and requests no notification permission.

• ·iOS / iPadOS and Android: the apps operate without a publisher backend and make no network requests to the publisher.
• ·Web: the site is served by Vercel, which — like any web host — records ordinary request logs, including IP addresses, for delivery and security. This is inherent to being a website rather than an installed app.

The website also calls a small endpoint of its own to obtain the short-lived developer token that allows Apple Music to play in the page, and to look up a recitation’s title and artwork. Those requests carry no identifier for you, and nothing about them is retained.

• ·Personal identifiers, contact lists, or location of any precision.
• ·Analytics, usage profiling, or behavioural tracking.
• ·Advertising identifiers (IDFA or GAID). No client contains any advertising or tracking SDK.
• ·Search queries, bookmarked pasurams, or reading habits.

• ·Apple or Google may process device metadata, download metrics and diagnostic crash logs, under their own privacy policies.
• ·If you opt in to share diagnostics, the publisher receives only aggregated, anonymised crash reports and basic usage statistics through App Store Connect and Google Play Console. That data is decoupled from your identity.

• ·Apple App Store: declared as “Data Not Collected”.
• ·Google Play Data Safety: declared as “No data collected” and “No data shared with third parties”.

• ·Local data (apps): uninstalling removes all local data from your device immediately.
• ·Local data (web): clearing this site’s data in your browser removes every stored preference and the offline cache.
• ·Synced cloud data: disable sync in Settings, or delete the stored app data through iOS Settings (iCloud) or Android Settings (Google Drive / app management).
• ·Sign-out: signing out in Settings removes the sign-in from that device or browser. To remove the account record itself, use the Apple or Google account controls it was made with.