1. Operator and scope
The operator is ООО «ТД „МЕЙДИНПРОФ“», Tax ID 7743477597, KPP 774301001, registration number 1257700412310. Address in current records: 125130, г. Москва, вн. тер. г. муниципальный округ Войковский, пер. 6-й Новоподмосковный, д. 3 [confirm against the current Russian company register extract]. Personal data contact: info@madeinprof.ru.
This policy covers madeinprof.ru and its current local version: equipment, licence, technical presales and partnership enquiries. The website does not provide a customer account, online payment or contract signing.
2. Data and purposes
Forms collect a reply contact (email or telephone), an optional company name and requirements. Any name, role or representative details included in the message become part of the enquiry. Do not submit passport or banking details, health information or third-party data without a lawful basis.
Purposes: respond, select suitable products, prepare an equipment and licence proposal, discuss the requested cooperation and manage this enquiry in CRM. Advertising mailings and publication of applicant data are outside these purposes.
Technical records include enquiry ID and date, form language, consent version and a hashed request identifier for rate limiting. A review cookie stores a signed access token. The website does not request geolocation, camera or microphone access.
3. Legal basis and processing operations
An enquiry uses separate consent confirmed by an unchecked checkbox. Contract formation and performance rely on separate lawful grounds where applicable. Declining consent does not prevent browsing the catalogue.
Operations: collection, recording, organisation, accumulation, storage, correction, retrieval, use, transfer to authorised processors for the stated purpose, restriction, deletion and destruction. Processing is automated and, for staff responses, non-automated.
4. CRM and recipients
Current enquiries are stored in the website database and sent through a server connection to Bitrix24 as leads assigned to Alexey Varlamov. Lead assignment does not establish appointment as the statutory personal data officer. Access is limited to authorised staff.
Telegram notifications are disabled in the current local version. Contact with a supplier or installation contractor does not automatically transfer all applicant data; scope and grounds must be agreed separately.
[Before launch, complete: legal names and addresses of hosting, CRM and email processors, processing agreements, actual recipients and storage countries. The Bitrix24 brand alone does not prove Russian database location.]
5. Storage location and cross-border transfers
The verified version runs locally on a Mac. Future public hosting and CRM, email and backup storage countries are unconfirmed. Collection of Russian citizens’ personal data must meet the current Article 18(5) of Federal Law 152-FZ. Website consent does not replace localisation requirements.
If an agreed route involves cross-border transfer, the operator must first verify its legal grounds and follow the statutory procedure. This version does not authorise arbitrary transfers to foreign services.
6. Retention and destruction
The current setting is 180 days for reviewing an unresolved enquiry. This planned period requires operator approval and does not mean automatic deletion from the website, CRM or backups. Statutory deadlines and exceptions apply on purpose completion, withdrawal or processing termination.
Archiving a lead is not data destruction. [Approve purpose-specific periods, the responsible person and a verified deletion process for website, CRM and backups.] Executed contract records may be retained on independent lawful grounds.
7. Rights and withdrawal
You may request processing information, correction, restriction or deletion, withdraw consent and challenge the operator’s actions. Email info@madeinprof.ru with your contact and, if available, enquiry ID. Identity checks must be proportionate; do not send passport details in advance. Responses and processing cessation follow statutory deadlines.
8. Safeguards and changes
Current technical measures include separate owner access, restricted enquiry access, server-side integration secrets and replay protection. Before public launch, verify HTTPS, staff authorisation, database and backup security and organisational records. New purposes, services or processors require policy updates and, where necessary, new consent.