International privacy annex
Russia: Federal Law No. 152-ФЗ, the Telegram bot and initial enquiry records
Privacy annex for Russian enquiries covering data minimisation, the Telegram bot, bookings, analytics and the service-provider map.
Status: Draft processing requirements and source references; legal, privacy and language approval pending
This annex outlines data-processing requirements and relevant sources; it is not a final legal opinion. Legal, privacy and language reviews remain pending, and existing launch restrictions still apply.
Who this covers
visitors in Russia, company representatives and clients providing contact details, document type and a deadline
Data that may be involved
- a name or business contact voluntarily provided by the user
- Telegram username, email or another contact channel
- company, role, country or route, and a brief account of the situation
- document type, receipt date, response deadline and amount at issue
- Website technical data and any analytics consent given
Launch safeguards
- the bot is not a mandatory file-transfer channel; documents are shared directly by arrangement
- no marketing tags before consent
- the main policy remains linked from the footer, calendar and contact section
- a CRM or new form requires an updated provider map and Roskomnadzor/localisation assessment
Service-provider approval
GA4 is restricted to a consent-aware configuration. The Telegram bot token stays server-side. LinkedIn tracking and retargeting remain disabled pending separate approval.
Language-version status
The Operator is Andrey Eduardovich Bernev, an individual resident in Georgia. Send data-rights requests to bernev_64@mail.com. The Russian text is available, but country-specific legal and implementation review remains pending.
Deployment verification required
Verification covers /, /contacts/ and /personal-data-policy/ before and after consent, with HAR network records and screenshots.