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.
• ·The iOS and Android apps show third-party advertising, which collects and tracks as set out in the next section. You can turn the tracking part of it off, and the section says how.
• ·This website shows no advertising and contains no advertising or analytics SDK.
• ·Cloud sync, where offered, runs on your own platform account — iCloud on Apple devices, Google on Android — and the publisher cannot see it.
• ·Where audio is offered, it 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.

This is the full declaration made to the App Store, in Apple’s own categories. Tracking has the meaning Apple gives it: linking this data with data from other companies for targeted advertising or advertising measurement, or sharing it with a data broker.

• ·“Not linked to you” means none of it is joined to your name, your email or an account: the publisher has no account to join it to. It is still tied to your device, which is what makes the tracking possible.
• ·Coarse location is approximate — a general area, derived from the network you are on rather than from GPS. The apps never request precise location and cannot read it.
• ·Crash data is the one row that is not used for advertising. It is how a crash gets fixed.

This website is not covered by any of the above. It serves no advertising, embeds no advertising or analytics SDK, and sets no advertising cookie. The only third-party frame it can load is a YouTube player, and only once you ask a recitation to play.

• ·iOS / iPadOS — the App must ask before it may track you, and it does. If you decline, it cannot read your device’s advertising identifier and cannot track you. To change your answer later: Settings → Privacy & Security → Tracking.
• ·Android — Settings → Privacy → Ads lets you delete your advertising ID outright, or opt out of ads personalisation. Deleting it removes it for every app on the device, not just this one.
• ·Either platform — Google’s own controls for the advertising it shows you live at myadcenter.google.com.

Some laws, California’s in particular, treat sharing data for cross-context behavioural advertising as a sale of personal information. On that definition the advertising in these apps is a sale, and the controls above are how you opt out of it. The publisher does not sell data in any other sense: it has none to sell.

• ·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.

• ·Reserving a copy sends us your name, email address, shipping country, how many sets you want, and anything you type into the note. That is a deliberate, one-off submission — nothing on this site collects it in the background, and reading never asks for any of it.
• ·A reservation is used to size the print run, to decide which countries to hold stock in, and to tell you when the edition is ready. It is not added to a mailing list and is not shared with anyone.
• ·Where a reservation goes depends on how this deployment is configured: either to a form endpoint the publisher operates, or — when none is set — into your own mail client as a message you send yourself. In the second case nothing reaches us until you press send.
• ·When actual orders open, a payment processor will handle the payment and receive what it needs to take it. Card, UPI and bank details go to that processor and are never seen or stored by this site.
• ·Ask to be removed at any time and you will be. A reservation holds no money and nothing is lost by dropping it.

The apps are unaffected. Nothing about the printed edition changes what iOS or Android store, sync or collect, and the declarations elsewhere in this policy still describe them exactly.

• ·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: where offered, and 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, where offered: 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. They do call Google’s advertising servers to fetch ads, as described above.
• ·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.

• ·Your name, email address, contacts, photos or files.
• ·Precise location. Only the coarse location described above, and only in the apps.
• ·The content of your reading — the pasurams you open or bookmark, your place in the text, and what you type into search. These stay on your device and are sent to no one, including the publisher.
• ·Audio listening history, or your credentials with any music service.

The distinction is worth stating exactly, because the section above complicates it. The advertising SDK records product interaction — that the app was opened, that a screen was shown, that an ad was seen or tapped. It does not receive the text you are reading or the terms you searched for, and neither does the publisher.

• ·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 — App Privacy: the table in the Advertising section above is that declaration, verbatim, including the rows under “Data Used to Track You”.
• ·Google Play — Data Safety: the same collection, sharing and purposes are declared there, in Google’s equivalent categories.

An earlier version of this policy declared “Data Not Collected” on both stores. That was true of the App at the time and is no longer true of the advertising it now carries. It is corrected here rather than quietly dropped.

• ·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.
• ·Advertising data: it is held by Google, not the publisher, so it is Google that deletes it — reset or delete the advertising identifier in your device settings, and use myadcenter.google.com for the rest.