Your reading life is personal

Privacy Policy

This policy explains what Leruna collects, why it is used, and the choices you have when you read and speak with the assistant.

Effective August 16, 2026

Who operates Leruna

Leruna is operated by Tuan Lima, an individual developer in Brazil. Questions or privacy requests can be sent to tuanclima@gmail.com.

Information we process

Account information

When you create an account, we receive account identifiers and the profile information you provide, such as your name and email address. Sign-in is provided by Clerk and may use Apple, Google, or email authentication.

Your library and reading activity

We store books you upload, imported public-domain books in your library, processed text and metadata, reading position, generated references, and other features needed to restore your reading experience. You are responsible for having the right to upload and process your books.

Assistant conversations and audio

When you use Ask Aloud, microphone audio and relevant book context are sent to the selected AI provider to understand and answer your request. Leruna does not intentionally store raw microphone recordings. Transcripts, questions, answers, selected text, and nearby passage context may be processed and may appear in diagnostic logs when logging is enabled.

Images and other AI features

Selected passages, prompts, and nearby text may be sent to an AI provider to generate images, definitions, cultural references, clean imported text, or answer questions.

Purchases and usage

Apple processes payments. Leruna receives product, transaction, entitlement, expiration, and app-account identifiers, but not your full payment-card details. We also record usage totals and reservations needed to enforce plan allowances and prevent duplicate charges. Subscription transactions and a stable account identifier are mirrored to RevenueCat for aggregate subscription reporting. TrustMRR may receive aggregate revenue, recurring revenue, and subscription-count metrics from RevenueCat to verify Leruna's business revenue; it does not receive your book or assistant content from Leruna.

Diagnostics

We may collect technical event logs such as provider, model, voice, timestamps, errors, and session diagnostics. Because diagnostics can include conversation or passage excerpts, do not submit material you do not want processed for troubleshooting.

Product analytics and crash reports

We use PostHog to understand how Leruna is used and where it fails. Analytics may include a stable account identifier, sign-in method, app screens and features used, book source and word count, subscription plan and billing period, purchase-flow outcomes, allowance totals, device and app information, and sanitized error categories. Native crashes may be reported on the next launch. We do not intentionally send book titles or text, search terms, selected passages, assistant transcripts, email addresses, raw provider responses, or payment-card details to product analytics. Session replay is disabled.

How we use information

• Provide authentication, book import, reading progress, search, references, assistant answers, audio, and image generation.
• Operate subscriptions, the Reader trial, allowances, abuse prevention, reliability, and customer support.
• Diagnose failures and improve Leruna’s safety and performance.
• Comply with legal obligations and protect users, Leruna, and others.

We do not sell personal information, use it for third-party advertising, or track you across other companies’ apps and websites for advertising.

Service providers

Information is shared only as needed to operate Leruna. Current providers include Clerk for authentication, Convex for application hosting and data storage, PostHog for product analytics and crash reporting, RevenueCat for subscription reporting, TrustMRR for aggregate revenue verification, Google (including Gemini) for live voice and fallback AI features, DeepSeek for text cleanup, definitions, references, and question answering when enabled, BytePlus and ByteDance (including ModelArk and Seedream) for image generation when enabled, Microsoft Azure and Microsoft Foundry for fallback image generation when enabled, fal.ai and Reve for fallback image generation when enabled, Apple for StoreKit purchases, device services, and sign-in, and Project Gutenberg for public-domain catalog data. If an OpenAI-powered option is enabled and selected, relevant requests are sent to OpenAI. These providers process information under their own terms and privacy commitments.

Storage, transfers, and retention

Leruna and its providers may process information outside your country, including in the United States and, when the first-party DeepSeek API is enabled, China. Account data, library content, reading progress, and entitlement records are generally kept while your account is active or as needed to provide the service. Diagnostic and support records are kept only as reasonably necessary for security, troubleshooting, legal, and operational needs. When you delete your account, Leruna deletes account-linked data from its active application database. To prevent repeated claims of the one-time Reader trial, Leruna retains a one-way pseudonymous eligibility marker derived from a verified email plus the trial dates and aggregate usage totals; this marker does not contain the email and cannot restore your account, library, or content. Other limited records may remain where required for financial or legal compliance, dispute resolution, or in provider backups until their normal rotation completes.

Your choices and rights

• You can deny or later revoke microphone, speech-recognition, and photo-library permissions in iOS Settings.
• You can delete individual books inside Leruna.
• You can delete your Leruna account and account-linked application data in Settings. Deleting Leruna does not automatically cancel an Apple subscription; subscriptions are managed through your Apple Account.
• You may email us to request access, correction, deletion, portability, or information about processing, subject to applicable law.

Security and children

We use reasonable technical and organizational safeguards, but no online service can guarantee absolute security. Leruna is not directed to children under 13, and we do not knowingly collect their personal information. If you believe a child has provided information, contact us.

Changes

We may update this policy as Leruna changes. The effective date will be revised, and material changes will be communicated in the app or by another appropriate method.