Privacy Policy

This policy describes how LexTap's account, reading, translation, file import, and subscription services process information, and how to contact us about your data.

Information We Collect

• Account information: your email address, a password hash, account identifier, language preferences, locale, account status, Premium entitlement information, and account timestamps. Authentication tokens are stored as digests with expiration and revocation information.
• Reading activity: the book or personal document you are reading, chapter and paragraph position, progress percentage, and update times.
• Translations and usage: text submitted for translation, optional surrounding context, source and target languages, and translation results. Account-linked usage records contain character counts, request type, provider, cache status, processing status, and dates. We also record translation quota thresholds and import limit events.
• Personal EPUB uploads: the original file, extracted cover and text, title, author and other embedded metadata, filename, size, file checksum, import status and errors, import history, and a terms acceptance timestamp if supplied.
• Subscriptions: store and product identifiers, transaction or purchase references, verification results, purchase and expiration dates, subscription status, Premium entitlements, and store notification records. New notification records retain the event identifier, type, provider, and processing timestamps, without the full notification payload.
• Installation identifier: the app generates a random installation-level identifier, stores it in secure device storage, and sends it with API requests. The server stores a SHA-256 digest of it together with platform, first/last-seen, quota-cycle, and account-link timestamps. We use it to enforce Free translation limits and prevent repeated quota creation across accounts on one installation. It is not an advertising identifier and LexTap does not provide it to the advertising SDK.
• Operational information: requests to the service, IP addresses processed by hosting and network infrastructure, request identifiers, timestamps, response status, performance information, and errors. Logs may include request parameters such as translation text, context, filenames, and transaction identifiers. Password, email, token, and purchase-reference parameters covered by the application's filters are redacted from application logs.
• Support correspondence: if you email us, we receive your email address and the information you include.

How We Use Information

We use information to authenticate accounts, save reading positions and preferences, process personal EPUBs, provide translations, enforce usage limits, verify purchases, enable Premium access, serve advertising to eligible Free users, diagnose problems, prevent abuse, and respond to support requests. Internal staff tools display account activity, reading and import usage, quota events, and subscription summaries to help us understand and operate the service.

Translation Processing

When a translation requires our translation provider, the service sends the selected text, any supplied context, and language codes to DeepL. This includes passages from personal EPUBs when you request their translation. The translation request does not include your LexTap email or account identifier.

Translations may be reused from a shared cache. Cache entries contain translated text and provider information; their keys include language and request type with a hash of the source text and context, without an account identifier. Default cache lifetimes are 90 days for words and 180 days for text, and can vary with service configuration. An older database cache may still contain source text, context, and translations from earlier operation.

EPUB/File Processing

Personal EPUBs are uploaded to the server and parsed there. We retain the original EPUB and extracted cover in file storage, and extracted chapters, paragraphs, metadata, and progress in our database. Personal uploads are separate from the public catalog and their reading APIs require the owner's authenticated account. Failed imports may retain the uploaded file and a failed document record until deleted.

We store personal EPUB import and access timestamps. Free access is limited to the three earliest successfully imported existing ready documents; access timestamps may support reading activity but do not change that selection. Expiration of Premium locks additional documents without deleting uploads, extracted content, or progress. Translation usage and a UTC exhaustion timestamp enforce a reset 24 hours after exhaustion.

Personal EPUB import does not send the full file to an AI service. Translation of selected passages is processed as described above. Deleting a personal document removes its extracted content and progress and attempts to remove its source file and cover from storage. Import quota history remains after document deletion. A storage failure can leave files requiring additional cleanup.

Subscriptions

On iOS, Apple processes payments. We send transaction identifiers to Apple's verification service and receive transaction details and subscription notifications to associate your purchase with your LexTap account and maintain Premium access. We do not receive your payment card number. Where purchases through Google Play are available, their purchase references and subscription details are similarly used for verification.

Advertising

Eligible Free users may receive banner ads supplied through the Yandex Mobile Ads SDK in the Library, Book Details, and My Books areas. Before the first ad request, a Free user must choose either personalized or non-personalized ads. Non-personalized ads are still displayed. The choice is stored on the device and can be changed later in Profile. Until a choice is saved, the ad SDK is not initialized and no ad request is created.

The SDK is initialized only after the backend has successfully identified an account as Free and the app creates an eligible banner. Premium accounts, accounts whose entitlement is still loading, and accounts whose entitlement could not be checked do not create or load ad requests. Activating or restoring Premium removes existing banners and stops future ad requests. LexTap does not include account identifiers, email addresses, reading history, uploaded content, selected words, or translations in its ad requests, and does not configure custom ad targeting.

When an ad is requested, Yandex and SDK components included with it may process information such as IP address, device or app-instance identifiers available to the SDK, device and operating-system information, network and mobile-country/network codes, approximate location derived from technical information, ad interactions, advertising data, and diagnostic or performance information. Yandex processes this information under its own privacy documentation. Before initializing the SDK or requesting an ad, LexTap disables the SDK's location-tracking setting and passes the user's saved personalized or non-personalized choice to the SDK. LexTap does not request App Tracking Transparency permission and does not directly request access to the iOS advertising identifier (IDFA).

The LexTap backend does not itself send advertising requests or store advertising identifiers. These public Support, Privacy Policy, and Terms of Use pages do not use analytics, trackers, or set cookies.

Push Notifications

The app may ask for notification permission and schedule local, on-device reminders for translation or EPUB import quota resets. LexTap does not register device push tokens with its backend or send device push notifications through Firebase, FCM, or APNs. Store subscription notifications received by the backend are used to update purchase status; they are not device push messages.

Third-Party Services

• Render: hosting for the production backend, processing service requests and operational logs. Account and reading data are held in the configured PostgreSQL database; translation caching uses Redis when configured.
• Cloudflare R2: the production file storage integration for uploaded EPUBs and covers.
• DeepL: translation processing as described above.
• Yandex Mobile Ads and included AppMetrica components: banner advertising for eligible Free users and the advertising, device, interaction, and diagnostic processing described above.
• Apple and Google Play: purchase verification for the relevant store when available and configured.
• Google Gemini: staff tools send catalog book metadata (such as title, author, year, language, source, and existing descriptions) to generate catalog descriptions and reading difficulty suggestions. This workflow does not send personal EPUB files, reading progress, or account details.
• Standard Ebooks: staff tools can download catalog books from this source; those requests do not include reader account details.
• Email services: messages sent to our support address are processed by the email providers involved in delivery.

The backend has no OpenAI integration. Third-party services process information under their own terms and privacy policies. Processing locations depend on the hosting and service providers and may be outside your country.

Data Storage and Retention

Account, reading, usage, import history, and subscription records persist in our database until account deletion. Standalone installation records used for anti-abuse and Free quota enforcement may remain after account deletion without the deleted account link. There is currently no automatic age-based deletion schedule for these records or for the older database translation cache. Translation cache expiration is described above. Hosting logs and backups, where maintained, follow the relevant hosting configuration; we do not promise a fixed deletion period for those copies. Removing a document does not erase prior logs or shared translations.

Account and Data Deletion

You can also request deletion without installing or signing in to the app. Visit Delete your LexTap account for email instructions, ownership confirmation, and information about retained data.

To permanently delete your account, sign in to the LexTap app, open Profile → Delete account, review the warning, and choose Delete permanently. You do not need to email support. This cannot be undone.

Once confirmed by the service, deletion removes your account and authentication sessions, saved reading progress, personal EPUB document records and extracted text, import history, account-linked translation usage and quota events, account-to-installation links, and LexTap purchase and entitlement records. Your authentication tokens no longer work on any device. The app that initiated deletion signs out and clears its stored authentication tokens, account quota markers, pending purchase references, and scheduled quota reminders. It retains device preferences such as language and appearance and retains the random installation identifier. The server may retain the corresponding digested installation record and quota state without the deleted account link to continue Free quota and anti-abuse enforcement.

Source EPUBs and covers are queued for automatic removal from file storage. Their application file records are removed immediately. Cleanup normally starts within a minute while the service is running; storage failures are retried automatically and pending cleanup survives server restarts. Until cleanup completes, we keep the storage service name, object key, and retry information needed to remove those files, without your account identifier or the file contents.

We remove identifiable payloads from older store notifications that can be matched to your purchases. Event identifiers, types, providers, and processing timestamps remain for notification deduplication. Shared translation caches have no account index and are not selectively erased by account deletion; they may still contain translated passages until expiration, and the older database cache has no automatic expiration. Previous operational logs, hosting backups, and support correspondence are not automatically erased by this action. Contact lextap@atomicmail.io for help with these retained copies or other privacy requests.

Deleting your LexTap account does not cancel an App Store subscription. Apple may continue billing until you cancel in your Apple subscription settings. Please cancel any active subscription before deleting your account; the confirmation includes a subscription management link where available. Account deletion remains available even with an active subscription. Store payment records remain with the relevant store under its own policies.

User Rights

Depending on the laws that apply to you, you may have rights to access, correct, receive a copy of, or request deletion of your personal information, or to object to or restrict certain processing. Contact us to exercise these rights. You may also have the right to complain to your local data protection authority.

Security

We use password hashing, digests for authentication tokens, authenticated access checks for personal reading data, and HTTPS connections to translation, storage, and purchase verification services. No method of storage or transmission can guarantee absolute security.

Changes to This Policy

We may update this policy as the service changes. The current version and its update date will be available on this page.

Contact Us

For privacy questions, contact lextap@atomicmail.io or visit Support.

Last updated: October 2026