Licence Agreement Privacy Policy

Privacy Policy

Revision date: 10 August 2026
This is a translation of the Russian original provided for convenience. In case of any discrepancy, the Russian version prevails.

This Privacy Policy (the “Policy”) describes what data the BuzzAI application (the “Service”) collects, for what purposes, and with whom it is shared. The Policy applies to all Users of the Service.

1. General Provisions

1.1. The operator processing personal data is Egor Andreevich Severinov, self-employed, payer of professional income tax (the “Operator”).

1.2. The address of this Policy on the Internet is https://buzzai.ru/en/privacy.html (Russian original — https://buzzai.ru/privacy.html). The current revision is available at these addresses at any time.

1.3. Matters relating to the collection, storage and protection of Users’ personal data are governed by this Policy, the Licence Agreement and Federal Law No. 152-FZ of 27 July 2006 “On Personal Data”.

1.4. By registering and using the Service, the User confirms that they have read this Policy and accept its terms.

1.5. If the User does not agree with this Policy, use of the Service must cease immediately.

1.6. The Operator may amend the Policy. The current revision is always available at the address above.

2. Data Minimisation Principle

2.1. The Operator collects only the data necessary to provide the User with the functionality of the Service and to comply with legal requirements.

2.2. The content of voice recordings and of recognised dictation texts is not retained by the Operator after the result has been returned to the User. Audio is sent to a third-party artificial intelligence model for recognition and is not stored on the Operator’s servers. The recognised text is returned to the User and is stored only in the local history on the User’s device (on macOS — the directory ~/Library/Application Support/Buzz/; on iOS — inside the application’s container).

3. What Data is Processed

Category of data Purpose of processing Legal basis
Mobile phone number, Telegram identifiers (chat_id, user_id), one-time confirmation codes; identifiers of external sign-in providers (Apple ID sub, Yandex ID), email and (where available) phone number received from the provider Identifying the User at registration and sign-in; delivering the confirmation code via the Telegram bot @buzzai_bot; sign-in via Apple / Yandex. Performance of the contract between the Operator and the User (Licence Agreement).
User identifier in the Service, session token (access_token), registration date Authorising the User while using the Service. Performance of the contract.
Balance in ø, remaining gift Balance, top-up history (amount, date, status, payment identifier in YooKassa); purchase confirmation and subscription status received from Apple for purchases made in the App Store Accounting for the paid features of the Service; billing. Performance of the contract; compliance with legal requirements on settlements.
Subscription information: plan, status, expiry date, automatic renewal flag, identifier of the stored payment method in YooKassa Providing the Premium Plus Subscription and automatic renewal. Performance of the contract.
Service usage metadata: number of recognition requests, audio duration, cost in ø, identifier of the model used, timestamps, errors Billing, abuse prevention, monitoring the health of the Service, product analytics. The content of audio and of recognised texts is not part of this metadata. The Operator’s legitimate interest in improving the Service; performance of the contract.
Technical data: application version, operating system version, device identifier (an anonymous UUID generated in the application), connection IP address Diagnosing problems, usage statistics, protection against automated attacks. The Operator’s legitimate interest.
Information provided by the User when contacting support (including the User’s email address and the text of the enquiry) Handling enquiries and responding to them. Performance of the contract; legitimate interest.
Web analytics data for the website buzzai.ru (via Yandex.Metrica): anonymised visitor identifier (ClientID), pages viewed, referral source, actions on the site (including “Webvisor” session recordings), cookies Web analytics, measuring traffic, assessing advertising performance. Not connected with the content of dictations, texts or audio. The Operator’s legitimate interest; the User’s consent (an informational cookie notice on the first visit).

3.1. Messages and mailings. In order to perform the agreement with the User, to provide access to the Service and its features, and to develop and improve BuzzAI, the Operator may send the User service and informational messages (emails, SMS, push notifications), including to obtain feedback (surveys, quality ratings). To deliver email the Operator engages a third-party provider — VK WorkSpace (the “Mail.ru for Business” service). For these purposes the Operator processes the User’s contact details — email address and/or phone number — as well as a technical flag recording the User’s consent to, or opt-out from, advertising mailings. The User may opt out of advertising mailings at any time (the “Unsubscribe” link in the message); service messages necessary for the operation of the Service are sent regardless of such an opt-out.

4. What the Operator Does Not Collect or Store

5. Data Transfer to Third Parties

5.1. To operate the Service the Operator engages the following counterparties:

5.2. The Operator does not transfer Users’ personal data to third parties for purposes other than those stated above without the User’s prior consent, except in cases expressly provided for by the law of the Russian Federation (including requests from competent state authorities).

5.3. Cookies and web analytics. The website buzzai.ru uses cookies — small text files stored in the User’s browser. Cookies are used for the correct operation of the site and for web analytics (Yandex.Metrica, including the “Webvisor” tool, which records anonymised visitor actions on pages), including to assess advertising campaign performance. On the first visit to the site the User is shown an informational notice about the use of cookies. The User may restrict or disable cookies in their browser settings, although this may affect the correct operation of certain site features. Site analytics do not touch the content of the User’s dictations, texts or audio recordings.

6. Storage and Processing Period

6.1. The User’s personal data is stored on the Operator’s servers located within the territory of the Russian Federation.

6.2. Data is stored for the entire period during which the User uses the Service. After 6 (six) months from the last use of the Service, or upon the User’s request to delete their account, personal data is deleted, except for information the Operator is required by law to retain (including payment transactions — for the periods established by tax legislation).

7. Account Deletion

7.1. The User may at any time request deletion of their account and the associated personal data by sending a request to severinovea@ya.ru with the subject “BuzzAI account deletion”.

7.2. Once the request is received, the account is deleted within 30 calendar days. Financial transactions relating to Balance top-ups and Subscription purchases are retained in anonymised form as part of tax and accounting records for the periods established by law.

7.3. Local data on the User’s device (dictation history, settings) is deleted automatically when the application is removed from the device.

8. Data Protection Measures

8.1. The Operator takes technical and organisational measures to protect Users’ personal data against unlawful or accidental access, destruction, alteration, blocking, copying and dissemination.

8.2. Data is transmitted between the User’s application and the Operator’s server over the secure HTTPS protocol using modern encryption algorithms.

8.3. Access to the server infrastructure is limited to a restricted group of people who maintain it.

9. Rights of the User

9.1. Under the Federal Law “On Personal Data” the User has the right:

10. The iOS Application and the Voice Keyboard

10.1. The iOS application consists of two parts: the main application and a keyboard extension, which is available in any application on the device through the system keyboard switcher.

10.2. iOS does not allow a keyboard extension to access the microphone. Recording and recognition are therefore performed by the main application, while the keyboard only starts dictation and inserts the finished text into the input field.

10.3. The keyboard requires the system “Full Access” permission. It is needed for exactly two purposes: network access (to send audio for recognition) and access to the storage shared by the application and the keyboard (to receive the recognised text and account data). The Operator uses no other capability of this permission.

10.4. The Operator does not collect or transmit what the User types by hand. No keystroke log is kept; the content of the input field in another application is neither read nor transmitted. The only things that leave the device are the audio the User recorded themselves by pressing the dictation button, and the text produced from it.

10.5. Typo correction and word suggestions work locally on the device using iOS facilities (UITextChecker); the words typed are not transmitted anywhere for this purpose.

10.6. Dictation audio is handled under the general rules of section 3: it is sent for recognition and is not stored on the Operator’s servers. A local copy remains only on the User’s device and only where recognition failed — for the “Recognise again” function; it is deleted automatically no later than 7 (seven) calendar days.

10.7. The dictation history (texts and metadata — time, duration, status) is stored locally on the device. The User may delete any entry or the entire history within the application.

10.8. Subscriptions in the iOS application are paid for through the App Store. The User’s payment details are not passed to the Operator: the Operator receives from Apple only the purchase confirmation (transaction data signed by Apple) required to activate access, and information about its status (renewal, cancellation, refund).

10.9. The device advertising identifier (IDFA) is neither requested nor used by the Operator; there are no third-party advertising networks or trackers in the application. The User is not tracked across other companies’ apps and websites.

10.10. The application asks the operating system for permission to access the microphone. The permission can be revoked in the device settings; if it is revoked, dictation becomes unavailable while the other features continue to work.

11. Limitation of the Policy

11.1. This Policy does not apply to the acts or the online resources of third parties, including resources linked to from the Service.

11.2. The Operator is not liable for the acts of third parties who obtained access to the Service on the User’s behalf as a result of the User compromising their credentials.

12. Requests and Contacts

12.1. Users may send the Operator requests concerning the processing of personal data, and any other enquiries, to the email address severinovea@ya.ru.

12.2. The Operator undertakes to consider an enquiry and send a reasoned response within 30 calendar days from its receipt.

12.3. The request must contain information that unambiguously identifies the User (for example, the phone number used at registration) and the substance of the enquiry.