Privacy notice · Updated 16 November 2026
Your library is personal.
This notice explains Taleva Audiobooks, its purchase-verification services and this support website.
Who is responsible?
Taleva Audiobooks is the independent UK developer business responsible for the processing described here (the data controller). We use Taleva Audiobooks as our trading name. Contact taleva-support@neyaniaslo.resend.app for support or privacy requests.
Postal contact: Taleva Audiobooks, Lytchett House, 13 Freeland Park, Wareham Road, Poole, Dorset, BH16 6FA, United Kingdom.
What stays on your device
Imported audio, book names, authors, narrators, covers, chapter details, listening positions, history, goals, streaks, notes, badges and your optional local profile or photo are processed on your device. Taleva does not upload your audiobooks or send book details to an AI service. No Taleva listening account or public profile is required. There is no public leaderboard or advertising inside the app.
System pickers let you choose audio files or an image. Taleva makes managed local copies so listening can continue offline. Removing a book does not delete the original file you selected. Uninstalling the app may remove its local library.
Optional listening reminders
If you enable reminders, Taleva asks the operating system for notification permission and schedules messages locally on this device. Your reminder time, tone, quiet-hour choices and a local delivery budget stay on the device. Messages do not include book titles, authors, notes or listening content. Taleva does not register a push-notification token or send reminder preferences to a notification server. You can turn reminders off in Taleva or change notification permission in your device settings. Streaks keep counting when reminders are off.
Backups and sharing you choose
A metadata backup can include book details, positions, notes, listening history, streak metadata and achievement progress. It excludes audio, custom cover images, your profile/photo, preferences (including reminder settings and delivery budgets), notification permissions and purchase entitlements. Keep your original files separately. Reports and share cards contain only the information shown or selected for that export; review them before choosing a destination. Your chosen storage or sharing service then handles the exported file under its own terms.
Purchases and restores
Apple or Google handles payment information and store accounts. Taleva does not receive your card number. On Android, the product identifier and purchase token are sent over HTTPS to Taleva’s verification service, hosted by Cloudflare, and checked with Google. The service stores a SHA-256 token digest, verified purchase status, test indicator and verification time, rather than the raw purchase token or Google account details. The raw token is used in memory to verify and acknowledge the purchase. On iOS, StoreKit verifies purchase evidence through Apple; Taleva has no Apple purchase-validation server. A protected local entitlement cache supports restoring access. Purchases do not transfer automatically between the two stores.
Android verification cache entries are removed after 30 days without verification, by request cleanup and a daily task, normally within about 31 days. This cache is not the lifetime purchase record; the store remains authoritative. Cloudflare’s D1 recovery history can retain deleted entries for up to a further 30 days.
Authorised Android review access
An authorised store reviewer can enter a private review code to request temporary Pro access. The code and a random installation-scoped identifier are sent over HTTPS to Taleva’s Cloudflare service for validation. The service stores only a configured code digest, not submitted codes, individual grants, books or payment records. A seven-day grant is kept in protected local storage, separate from paid purchase evidence. The same code can renew access while authorised; removing it or letting it expire does not remove a real paid purchase. Network information is processed for delivery and rate limiting. This is not a payment or a listening account.
Optional feature counts
Usage reporting is off by default and is unavailable in builds where the reporting service is not configured. If you are 18 or older, you can choose to share usage counts in the Quick Tour or in Settings. Your age declaration stays on your device. If you explicitly switch sharing on, Taleva can send allowlisted feature-open and import-success/failure counts, app version, iOS or Android, and a random per-batch deduplication identifier to a separate Cloudflare service. In versions that support usage milestones, the report can also include one count per installation for first agreeing to share the expanded counts, first adding a book, and first playing a cumulative minute of audio. If you agree, the counts may include milestones reached earlier in that app session. The report does not send the book or the amount of time you listened. If you previously shared feature counts, Taleva asks you to agree to the updated choice before sharing resumes. It does not include book names, files, notes, listening content, your profile/photo, purchases, email or a continuing account/device identifier. Switching it off stops future reports and clears queued counts; previously sent reports cannot be attributed to you through a listening account.
Active reports use a 30-day cutoff and daily cleanup, normally within about 31 days. Deleted reports can remain in D1 recovery history for up to a further 30 days. Delivery and abuse prevention require processing connection information, including IP addresses; IP addresses are not stored in the app’s report or verification tables.
Optional iOS campaign measurement
Starting with iOS version 1.0.3, compatible builds can offer a separate choice to help Taleva measure which Google ads lead to a first app open. This starts off. If you are 18 or older, you can opt in during the Quick Tour or in Settings under Help measure Taleva’s ads. You can turn it off there at any time. Your choice does not affect listening, imports or purchases.
When you opt in, Google Analytics for Firebase can receive first opens, sessions and other app lifecycle events. It assigns an identifier to this installation of Taleva and can collect basic app and device information, general location derived from your IP address, and diagnostic data. Standard App Store purchase events can include the product, price and currency. Google Ads uses the first-open event for campaign measurement and optimisation. Taleva keeps your books, audio, listening history, notes and local profile out of these reports.
Taleva disables the Apple advertising identifier, vendor device identifier, ad storage and ad personalisation in this integration. The first-party feature counts described above are a separate choice. Switching off campaign measurement stops future Analytics collection and does not erase information already received by Google. Google Analytics is configured to retain event-level records for two months and user-level records for 14 months. New activity restarts the user-level retention period. Aggregate reports can be kept longer. See Google’s Analytics data retention information.
Support and service providers
If you contact our support address, Resend and your chosen email provider process your email address, sender name if provided, message and attachments. We use this information to answer your request, follow up and handle privacy requests, not to add you to marketing lists. Taleva’s earlier Gmail address remains a contact route for existing conversations; Google processes messages sent there.
Resend retains email and log data for 30 days under its standard service policy and states that recovery backups are kept for seven days. We keep a minimal support case record and essential correspondence while a request is open, then review it for deletion within 30 days after resolution, unless a dispute or legal obligation requires longer. This case review is manual. We do not promise that Resend keeps an open conversation indefinitely. Do not send private audio, passwords, identity papers, card details, purchase tokens or full device backups.
Resend stores data in the United States. It provides a Data Processing Addendum with EU standard contractual clauses and UK transfer provisions, and publishes its subprocessors and security and retention information. Routine support handling uses human review; incoming email does not trigger app or account actions. We do not enable message open tracking, click tracking, an AI editor or an automatic email agent for Taleva support.
Cloudflare provides website delivery, hosting, rate limiting and database services; Apple and Google provide their store, payment and operating-system services. These providers can process connection, security and transaction information under their own applicable policies. A database’s Western Europe placement is not a promise that all processing stays in the UK or EU. These services can process information in the United States and other countries. Cloudflare describes its transfer safeguards in its Data Processing Addendum, including European standard contractual clauses and the UK transfer addendum for applicable restricted transfers, and its privacy policy. For optional iOS measurement, Google provides Firebase, Analytics and Ads. Google explains its international processing and transfer safeguards in its data transfer frameworks; Apple explains its processing in its privacy information. Contact us for information about the safeguards relevant to your request.
Purposes and your choices
We process information to provide the local player and requested purchase features, answer support requests, protect services against abuse and meet applicable legal obligations. Where UK or EEA data law applies, the relevant bases are providing requested services, legitimate interests in security and support, legal obligations where applicable, and your consent for optional usage counts and optional iOS campaign measurement. You can withdraw either consent in Settings without affecting listening.
You can change or remove local profile information, remove imported books and delete the app’s local data. Removed books may retain a local listening record for reimport; uninstalling or clearing app data removes the app’s local database. Store purchase records and files you exported are controlled separately. Contact us to request applicable access, correction, deletion, restriction, objection or portability rights for information we actually hold; we may need enough information to verify your request. Because we do not hold your local audio library, we cannot retrieve or erase it remotely. To request deletion, email taleva-support@neyaniaslo.resend.app with the subject “Privacy request” and describe the information you want removed. Do not send a password, identity document, card number or purchase token. We will explain if a record cannot safely be identified or must be retained by law. Requests normally receive a response within one month, subject to applicable extensions. Deleting a support message does not cancel your store purchase. You can complain to the UK Information Commissioner (0303 123 1113) or your relevant supervisory authority.
Your right to object
You can object to processing based on our legitimate interests, including security and support, for reasons relating to your situation. Email taleva-support@neyaniaslo.resend.app. We will stop the relevant processing unless we have compelling lawful grounds to continue or need it for legal claims. We do not use your information for direct marketing.
Young listeners
Taleva’s first release is designed for independent teen and adult listeners, not directed at children under 13. Local laws may protect older children too. Do not send us a child’s personal information through support. Contact us if you believe personal information has been provided improperly. Store content ratings are separate from intended audience and can vary by country.
Security and updates
Service requests use HTTPS. Purchase credentials remain on the server; local purchase cache uses protected device storage. No system can guarantee absolute security. We update this notice when features or processing change, and show the revision date here. Material changes requiring consent will be presented before the relevant optional processing.