Documents
Version of [date]
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.
| Category | Contents | Source |
|---|---|---|
| Contact details | Telegram ID, Telegram name and username, interface language | Telegram, when you contact the bot |
| Request data | Date, city, venue, event type and format, budget, capacity, contact’s role, organiser | Client messages |
| Voice messages | Audio recording and its transcript | Client (optional) |
| Company details | Company name or full name, tax ID, registration number, address, bank details, signatory, email | Web form or uploaded file |
| Documents | Contract, invoice, certificate of completion, agreed rider, signature and payment marks | Created during the process |
| Technical data | Date and time of messages, request status, action log | Created by the system |
Special categories (health, beliefs, etc.) and biometric data are not processed.
| Purpose | Legal ground |
|---|---|
| Receive and review a booking request | Consent 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 completion | Performance of a contract (Art. 6(1)(5) of 152-FZ); GDPR: Art. 6(1)(b) |
| Accounting and tax records | Legal obligation (Art. 6(1)(2) of 152-FZ); GDPR: Art. 6(1)(c) |
| Remind you of an unfinished request or a payment deadline | Consent / performance of a contract |
| Internal assessment of organisers’ reliability after events | Legitimate interest of the operator — [to be confirmed with a lawyer] |
We do not use the data for advertising mailings and do not sell it.
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:]
| Data | Period |
|---|---|
| Unfinished or declined request | [12 months] from the last message, then deletion or anonymisation |
| Contract, invoice, certificate of completion, company details | 5 years after the end of the year of performance (accounting) |
| Voice recordings | [30 days] after transcription |
| Action log | [3 years] |
A contract or processing instruction is concluded with every processor (Art. 6(3) of 152-FZ; GDPR Art. 28).
[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.
You can:
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.
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).
The current version is always available at [domain/en/privacy] and via the /privacy command in the bot.