Documents

Personal data processing policy

Version of [date]

1. Who processes the data

Operator: [full name of the agency / sole trader], Tax ID (INN) [ ], OGRN/OGRNIP [ ], address: [ ].

Person responsible for organising personal data processing: [full name, position], email: [privacy@domain].

This policy applies to the Telegram bot [@bot_name], web forms on the domain [domain] (Telegram Mini App) and the related artist booking processes.

2. What data we process

CategoryContentsSource
Contact detailsTelegram ID, Telegram name and username, interface languageTelegram, when you contact the bot
Request dataDate, city, venue, event type and format, budget, capacity, contact’s role, organiserClient messages
Voice messagesAudio recording and its transcriptClient (optional)
Company detailsCompany name or full name, tax ID, registration number, address, bank details, signatory, emailWeb form or uploaded file
DocumentsContract, invoice, certificate of completion, agreed rider, signature and payment marksCreated during the process
Technical dataDate and time of messages, request status, action logCreated by the system

Special categories (health, beliefs, etc.) and biometric data are not processed.

3. Purposes and legal grounds

PurposeLegal ground
Receive and review a booking requestConsent of the data subject (Art. 6(1)(1) of Federal Law 152-FZ); GDPR: Art. 6(1)(b) — pre-contractual steps
Prepare, conclude and perform the contract, issue the invoice and certificate of completionPerformance of a contract (Art. 6(1)(5) of 152-FZ); GDPR: Art. 6(1)(b)
Accounting and tax recordsLegal obligation (Art. 6(1)(2) of 152-FZ); GDPR: Art. 6(1)(c)
Remind you of an unfinished request or a payment deadlineConsent / performance of a contract
Internal assessment of organisers’ reliability after eventsLegitimate interest of the operator — [to be confirmed with a lawyer]

We do not use the data for advertising mailings and do not sell it.

4. Use of AI

The bot uses a language model to understand messages and carry on the conversation. Before anything is sent to the model, the system removes from the text names, phone numbers, emails, tax IDs, account numbers and links, replacing them with placeholders. Company details, files and documents are not passed to the model. Decisions on booking, price and terms are made by a person (the manager), not by AI.

[Choose a voice recognition option:]

  • Option A (recommended). Voice messages are transcribed on the operator’s servers in Russia and are not transferred abroad.
  • Option B. Voice messages are sent for transcription to [service name, country]. This is a cross-border transfer (section 7).

5. Where and how long the data is stored

  • Initial recording, systematisation, accumulation, storage, updating and retrieval of the data of Russian citizens are carried out in databases on servers in the Russian Federation: [hosting, city].
  • Retention periods:
DataPeriod
Unfinished or declined request[12 months] from the last message, then deletion or anonymisation
Contract, invoice, certificate of completion, company details5 years after the end of the year of performance (accounting)
Voice recordings[30 days] after transcription
Action log[3 years]

6. Who receives the data

  • The artist the client’s request is about: only the request and contract data.
  • Services the process cannot work without: cloud hosting [ ], e-signature service [ ], e-document exchange [ ], bank [ ].
  • Government authorities — where required by law.

A contract or processing instruction is concluded with every processor (Art. 6(3) of 152-FZ; GDPR Art. 28).

7. Cross-border transfer

[To be completed once the services are chosen: country, recipient, purpose, data. Notify Roskomnadzor before the transfer begins (Art. 12 of 152-FZ).]

Open question for the lawyer. Conversations with the bot technically pass through Telegram’s infrastructure (Telegram Messenger Inc., UAE / United Kingdom). It needs to be assessed whether this counts as primary collection of personal data using a foreign service, and how to document it.

8. Your rights

You can:

  • find out what data of yours we process;
  • ask us to correct, block or delete the data;
  • withdraw your consent;
  • complain about the operator’s actions to Roskomnadzor (EU residents — to the supervisory authority of their country).

How: the /privacy command in the bot or an email to [privacy@domain]. We reply within 10 working days (Art. 14 of 152-FZ; the period may be extended by 5 working days with notice).

When consent is withdrawn, processing stops. Data needed to perform a concluded contract and to meet legal requirements is kept for the required periods.

9. Data protection

Only authorised staff have access to the data: managers see the requests of their own artists. Actions are logged. Connections are encrypted. Secrets (tokens, keys) are stored separately from the code. In the event of a leak, the operator notifies Roskomnadzor within 24 hours and reports the results of the investigation within 72 hours (Art. 21(3.1) of 152-FZ).

10. Changes to the policy

The current version is always available at [domain/en/privacy] and via the /privacy command in the bot.