Privacy Policy

Q: How do I request privacy help or deletion?

Email support with your request. Uninstalling the app removes locally stored app data from your device; provider-held subscription or cloned-voice records may require a separate request.

Effective 16 April 2026

This Privacy Policy explains what information Narratr collects, how it is used, and the choices you have. We aim to collect the minimum necessary to operate the app.

Short version: your imported EPUB and TXT books stay on your device as full files. On-device voices run locally. Cloud AI voices need the current text chunk to be sent for narration, and permission-first voice cloning uses the short recording you provide to create the cloned voice profile.

Privacy quick answers

Does Narratr upload my whole book?

No. Imported EPUB and TXT files are stored locally on your device as full files. Cloud voices only receive the current text chunk needed for narration. If you are checking format boundaries first, start with Supported files.

Can I use Narratr without cloud voice processing?

Yes. On-device voices run locally. Cloud AI voices need internet access and require sending the current narration chunk to the TTS provider. The practical voice trade-offs are explained in Plans and voice options.

How is voice cloning data handled?

Voice cloning is for your own voice or a voice you have explicit permission to use. The short voice recording is uploaded to the TTS provider to create a cloned voice profile tied to your subscriber ID, and you can delete the cloned voice in the app.

How do I request privacy help or deletion?

Email luke@deepmake.io with your request. Uninstalling the app removes locally stored app data from your device; provider-held subscription or cloned-voice records may require a separate request. The Support page has the practical checklist.

1. What We Collect

Subscription status — managed by the app stores and RevenueCat. We see your anonymous subscriber ID, purchase entitlements, and subscription state. We do not see your Apple ID, Google account, or payment card details.
Crash and diagnostic data — if enabled in your device settings, Apple or Google may share anonymised crash reports with us through their developer consoles. These can include stack traces and device model but no personal content from your books.
TTS requests — when you use a cloud voice, the text of the currently-playing chunk (typically 180–600 characters) is transmitted to our Cloudflare Worker and forwarded to the TTS provider (DeepInfra) to generate audio.
Voice recordings — if you use voice cloning with your own voice, or a voice you have explicit permission to use, the short recording you make is uploaded to the TTS provider to create a cloned voice profile tied to your subscriber ID.

2. What We Do NOT Collect

No tracking or advertising. Narratr contains no ad networks or behavioural advertising trackers. Platform privacy declarations are configured to avoid cross-app tracking.
Your books stay on device. The full text of books you import is stored locally on your device and never uploaded in bulk. Only the small chunks needed for active TTS playback are sent to the TTS provider.
Writing drafts follow the same rule. If you use Narratr to listen back to your own manuscript, the imported TXT or EPUB file stays local as a full file; cloud voices only receive the current chunks needed for narration.
Word-timing extraction runs on device. We use an on-device Whisper model to align audio with text — no audio is uploaded for timing purposes.
No account or personal profile is required. Narratr does not ask for name, email, phone number, or location.

3. Third Parties

Apple and Google — process purchases and deliver the app through their app stores.
RevenueCat — manages subscription entitlements and generates anonymous subscriber IDs. revenuecat.com/privacy
Cloudflare — hosts our auth proxy and stores temporary rate-limit counters. Proxy logs contain request metadata only (no book content is logged). cloudflare.com/privacypolicy
DeepInfra — runs the cloud TTS models that generate audio from text chunks. deepinfra.com/privacy

4. How Long We Keep Data

Subscription records: for as long as your subscription is active, plus whatever the app stores and RevenueCat require for tax and audit purposes.
Cloned voice profiles: until you delete the custom voice in-app, which removes it from the upstream provider.
Rate-limit counters: up to 90 days.
TTS request text: processed in-flight and not retained by our Worker. Upstream providers may retain inputs per their own policies.

5. Your Rights

You can:

Stop generating new cloud TTS by switching to an on-device voice in the Voices tab.
Delete any cloned voice you created in the app.
Cancel your subscription through iOS Settings or Google Play subscriptions at any time.
Delete all locally-stored data by uninstalling the app.
Contact us to request deletion of any account-linked data we hold. Under GDPR and UK-GDPR you also have the right to access, rectify, or export your data.

6. Children

Narratr is not directed at children under 13 and we do not knowingly collect data from them. If you believe a child has used the app, contact us and we will delete any related data.

7. International Data Transfers

Our providers operate globally. Data may be processed in the United States or other regions outside the UK/EEA under standard contractual clauses or equivalent safeguards.

8. Security

Traffic to our Worker and upstream providers is encrypted in transit (HTTPS/TLS). Subscription validation uses signed API keys. No system is perfectly secure, but we keep our attack surface minimal by avoiding data we don't need.

9. Changes

We may update this Policy. Material changes will be notified in-app or on this page. The effective date at the top reflects the most recent update.

Related privacy and trust routes

If you are deciding whether Narratr fits your workflow, these pages keep the privacy, file-format, and support boundaries together.

Supported filesConfirm Narratr’s EPUB and TXT boundary before importing books or drafts. EPUB to audiobookSee how readable EPUB files become listenable while full imported files stay on device. TXT to audiobookUse the plain-text workflow for drafts, notes, and public-domain text you have the right to use. AI audiobook makerCompare on-device playback with cloud AI voices that need the current narration chunk. Read-along listeningReview the practical reading-and-listening workflow before choosing voice settings. Manuscript listen-backUnderstand how your own TXT or EPUB drafts fit the same local-file rule. Public-domain EPUBsKeep rights-cleared source choices and privacy boundaries together before listening. Long text filesCheck the plain-text workflow for long notes or exports without broad file-format claims. Android TTS choicesCompare on-device and cloud voice trade-offs while Android store wording stays conservative. Plans and voice optionsCompare on-device and cloud voice boundaries without exact-price claims. Support and deletion requestsFind the checklist for subscriptions, cloned voices, refunds, and privacy help.

10. Contact

Privacy questions or data requests? Email luke@deepmake.io.