1. Who is responsible
In short: Individual Entrepreneur Artyom Isrofilov is responsible for your data. Use support@litgolos.ru for privacy requests.
The data controller and owner of LitVoice is Individual Entrepreneur Artyom Erkinovich Isrofilov, Russian TIN 773180521506, OGRNIP 326774600058292 ("we").
This Policy covers the website litgolos.ru including the account dashboard, the LitVoice web app at app.litgolos.ru, the LitVoice iOS and Android apps, and the related Telegram and MAX bots used for sign-in, payments, notifications, and support.
We process personal data in accordance with Russian Federal Law No. 152-FZ of 27 July 2006 "On Personal Data" and other applicable law.
For privacy questions, email support@litgolos.ru. We handle requests within the time required by applicable law.
2. Data we process
In short: we need account, device, usage, payment, and temporary synthesis data; books only if you turn on the cloud library. Payment card details stay with the payment provider.
Account and sign-in
Depending on your sign-in method, we receive a Telegram, MAX, VK ID, Apple, or Yandex ID identifier. The provider may also share your email address — only within the permissions you granted to that provider. We keep only the identifier and email; we do not retain the provider's name, surname, or username.
You can also provide an email address yourself: in the account dashboard at litgolos.ru or in a bot before paying for a package or subscription. We send receipts, subscription notices, and the sign-in link to that address. It also becomes a sign-in method: the link in the email opens the dashboard without a bot or the app. When you request such a link, we process the address you entered and the IP address of the request — to send the email and to limit how often requests can be made.
Use of the Service
We keep an internal account ID, balance, subscription, credit and usage history, tasks, notifications, and support information. Product analytics may include book added, preloaded, and completed events, title and author, language, platform, and size in text fragments.
Cloud library
If you have a subscription and have turned on library sync yourself, we store the books you add so they are available on all your devices: the parsed book text with images and table of contents, the original book file, title, author, language, size, and file checksums, as well as your reading position and the name of the device that saved it. We also record your choice — sync on or off — and when you made it. Audio is not synced: it stays only on the device where you listened.
Technical data
The app sends an installation identifier, platform, app version, device model and manufacturer, operating system and version, language, IP address, and activity timestamps. We use this to run and diagnose the API, produce statistics, and protect bonuses and payments from abuse. The website additionally receives technical request details from your browser as needed to operate and protect it.
Cookies
The website uses strictly necessary cookies only: we have no advertising or third-party tracking cookies. One of them appears after you sign in to the account dashboard, remembers that you are signed in, and is removed when you sign out. You can block such cookies in your browser settings, but the dashboard sign-in will then not work.
Payments and messages
We receive the amount, currency, status, time and transaction identifier, purchased plan or package, and technical purchase-verification data. We do not receive your full card number, CVC, or online banking password.
When we send email, our delivery log stores the address, message content, delivery status, and opening information. A small invisible image records the time and count of opens, but we do not retain the recipient's IP address or user agent from this request.
Speech synthesis text and support
We temporarily process text submitted for speech synthesis. When you contact support through the website form or another channel, we process your message, the reply contact you provided, and any information you choose to attach.
Important: we do not ask for passport details, biometrics, health, political, or religious information. Please do not include sensitive information in book text or support requests unless necessary.
3. Why we process data
In short: we process data to deliver the Service, handle payments, keep it secure, and improve reliability.
| Purpose | Legal reason |
|---|---|
| Create an account, sign you in, and provide speech synthesis | Perform our contract with you |
| Store books and sync them across your devices if you turned on the cloud library | Perform our contract with you; sync is turned on only by your action |
| Manage balance, subscriptions, payments, and receipts | Perform the contract and comply with law |
| Send service notices and provide support | Perform the contract and our legitimate interest in supporting the Service |
| Protect accounts, payments, and bonuses from abuse | Our legitimate interest and security |
| Understand performance and improve the app | Our legitimate interest; consent where required by law or platform settings |
| Send our own news and offers | Your consent |
| Comply with a binding court or government request | Legal obligation |
These grounds correspond to Article 6 of Russian Federal Law No. 152-FZ: performance of a contract, compliance with legal obligations, our legitimate interests provided your rights and freedoms are respected, and consent where required.
When you submit an email address in the dashboard sign-in form, you tick a consent to the processing of personal data: until the email is sent we do not know whose address it is, so the link request itself relies on your consent. Everything that happens after you sign in is performance of our contract with you.
Where processing relies on consent, you may withdraw it. This does not affect prior lawful processing or information we must keep under another legal basis.
We send our own news and special offers only with your separate consent. You can opt out at any time in notification settings or as described in the message itself. Service messages (payments, receipts, security, support replies) are not marketing and continue while the account exists.
We do not use your data for third-party advertising and do not profile you for advertising purposes.
Automated checks
Some abuse checks run automatically, without human involvement. This is how the rule "one welcome bonus per device and per email address" works: if the device or address has already received the bonus, a new account does not get it, or a bonus already credited is reversed. Request rate limits are also applied automatically when usage exceeds the permitted level.
These checks affect only the welcome bonus and technical limits inside the Service. They do not cancel a paid balance, a subscription, or access to your account, and we do not make automated decisions that produce legal or similarly significant effects on you.
We notify you when a bonus is reversed. You can contest the result of an automated check: write to support@litgolos.ru — a person will review it, and if the check was wrong we restore the bonus.
4. What happens to text, books, and audio
In short: synthesis text is processed automatically and deleted after the task; the cached result may remain for seven days after its last use. Books are stored on our servers only if you turned on the cloud library.
Synthesis text
- The app sends selected text to our server over an encrypted connection.
- The server automatically prepares the text and creates audio using our TTS components.
- The source text is deleted when processing finishes or is stopped.
- We keep a cryptographic hash and the resulting audio for caching. The hash cannot be used to recover the source text.
- Cached audio and its record are deleted seven days after the last use.
Books in the cloud library
- A book is parsed on your device. Without a subscription, or with sync off, it stays only on the device and is not sent to our server.
- With sync on, the device uploads the parsed book and its original file to the cloud over an encrypted connection. Books are kept in private storage under your account; they can be downloaded only through a temporary link the server issues to your account.
- The server automatically, without human involvement, checks uploaded books and re-parses them from the original file when we fix the parsing software. This way parsing errors are corrected in books already uploaded.
- Books are not matched across users: there is no shared catalogue, and duplicates are looked up only within your own library.
- You can turn sync off in the app settings at any time. When you do, you choose whether to keep the books in the cloud or delete them from it; books on your devices remain.
General rules
We do not routinely read submitted text or books, sell them, use them for advertising, or give them to third parties to train models. Limited access may be necessary for technical diagnosis at your request or to comply with a binding legal requirement.
You are responsible for having the right to submit the text and to upload the book to the cloud. Do not submit another person's confidential information without permission.
5. Who may receive data
In short: data goes only to services needed for sign-in, payment, analytics, messaging, infrastructure, or legal compliance.
We share only the data needed for the recipient's role:
- Sign-in providers: Telegram, MAX, VK ID, Apple, and Yandex ID.
- Payment providers and stores: Apple App Store, RuStore, Huawei AppGallery, YooKassa, Tochka Bank, banks, and payment infrastructure. In a payment dispute (including a chargeback) or a review by a bank or store, we disclose proof of the transaction and of your consent to it: the date and time of consent, the version of the Terms in force at that moment, the IP address, browser or device data, the amount, plan, and billing period, and the history of charges and reminders. The basis is performance of the contract and our legitimate interest in defending a claim; we disclose only what the review requires.
- Russian Federal Tax Service: transaction information required for receipts. Payer personal data is not included unless required by law or the payment method.
- AppMetrica: technical data and usage events for app analytics and diagnostics.
- Telegram, MAX, and email providers: recipient identifier and message content when used for sign-in links, notices, or support.
- Infrastructure providers: hosting, file storage, and technical contractors under appropriate data-protection obligations.
- Public authorities: only when disclosure is legally required by a valid request.
Independent services apply their own privacy rules. You can also manage their permissions in your account with the relevant provider.
Our primary server processing takes place in Russia. Foreign sign-in providers, app stores, or messengers may process data in other countries. Where required, we use the legal grounds and safeguards applicable to international transfers.
6. How long we keep data
In short: not every record disappears immediately: financial documents and limited anti-abuse records may need to remain longer.
| Category | Usual period |
|---|---|
| Account, sign-in methods, email, balance, and subscription | While the account exists; data is deleted within 30 days after account deletion, access ends immediately |
| Dashboard sign-in link and session | The link — until first use or expiry; the session — until you sign out |
| Source TTS text | Until the task finishes or stops |
| Hash and cached audio | Seven days after last use |
| Books in the cloud library, their original files, and reading positions | While the subscription is active and sync is on; 14 days after the subscription ends, then deleted. A book you delete, and a library you delete from the cloud when turning sync off, are deleted immediately. After re-parsing, the previous parsed version is kept for 30 days |
| Book usage events | Up to 540 days; a de-identified title and author directory may be kept longer |
| Technical and security events | Usually 7 to 365 days, depending on purpose and severity |
| Device data used to prevent repeat bonuses | While the account exists; after deletion, only de-identified statistics may remain if they can no longer be linked to a person |
| Payments, refunds, and receipts | For mandatory tax and accounting periods and potential claim periods |
| Email and support records | As needed for delivery, retry, support, audit, and dispute resolution |
A period may be extended to comply with law, investigate abuse, handle a refund or legal claim, or protect rights. After the purpose ends, data is deleted, de-identified, or isolated until the mandatory period expires.
Account deletion
We delete the entire account and its associated personal data — sign-in methods, email, profile, task history, and in-app notifications — within 30 days of confirmed deletion. The cloud library — books, their original files, and reading positions — is deleted immediately; books on your devices are not affected. We retain only records we are legally required to keep, such as certain payment and tax documents. They are isolated from the deleted account and are not used for other purposes. De-identified statistics may remain only if they can no longer be linked to you.
Important: deleting your account does not cancel a subscription renewed by an app store or another payment service. Cancel it separately and before deleting the account — in Apple App Store, RuStore, or the store where you subscribed — otherwise charges continue.
7. Your rights and choices
In short: you can access or correct data and delete your account. Start by contacting support.
Subject to applicable law, you may:
- ask whether we process your data and receive information about it;
- correct inaccurate data;
- delete your account or request erasure;
- turn off library sync and delete books from the cloud in the app settings, or delete a single book from the book list;
- restrict or object to processing;
- receive data you provided in a portable format where this right applies;
- withdraw consent where processing relies on consent;
- object to the result of an automated check and ask that a person review it;
- complain to a competent data-protection authority (in Russia, Roskomnadzor) or a court.
Email support@litgolos.ru to make a request. We may verify account ownership before disclosing data.
Some information cannot be erased immediately if retention is legally required or necessary to establish, exercise, or defend legal claims. We will explain any applicable limitation.
8. Security, children, and changes
In short: we use reasonable safeguards but do not promise the impossible. Material changes should not come as a surprise.
Security
We use access controls, encrypted connections, payment-webhook signature checks, request rate limits, and other reasonable organisational and technical safeguards. No internet service can guarantee absolute security.
Younger users
If the law where you live does not allow you to accept this Policy or enter into the Service contract on your own, use LitVoice only with a parent or legal guardian. Tell us if you believe a child's data is processed without a proper legal basis.
Changes
We may update this Policy when the Service or law changes. The new version will show its update date. We will give advance notice of material changes through the Service or an available contact channel where required by law or reasonable given the change.
9. Contact
In short: for a formal request, email support@litgolos.ru.
For privacy questions, account deletion, or rights requests:
Individual Entrepreneur Artyom Erkinovich Isrofilov Russian TIN 773180521506 · OGRNIP 326774600058292 Registered by Interdistrict Inspectorate No. 46 of the Russian Federal Tax Service for Moscow
- Email: support@litgolos.ru
- Telegram: @LitGolosBot
- MAX: id773180521506_bot
The rules for using the Service are in our Terms of Use.