KADO

documents

Personal data processing policy

Version dated 20 September 2026

Website: kadonext.com

01 General provisions

This Policy sets out how the operator processes and protects personal data when visitors use kadonext.com, its features, or contact the operator.

The Policy has been prepared under Federal Law No. 152-FZ “On Personal Data” dated 27 July 2006. The operator processes only the data needed for specified purposes and does not process it in a manner incompatible with those purposes.

The website can be viewed without providing a name, telephone number or email address. A visitor who does not accept optional processing may choose not to submit an enquiry and may decline analytics cookies.

02 Data processed

Enquiry data

A name or chosen identifier, email address, telephone number, messenger username, information about the project, its stage, timing and budget, links to materials, and any other information a visitor voluntarily includes in an enquiry.

The operator also records the fact that consent was given, the version and text of that consent, and the date and time the enquiry was submitted.

A visitor may optionally attach voice messages. Recordings contain the visitor’s voice and any sounds captured by the microphone. They are used to understand and answer the enquiry, not to identify the person by their voice.

Technical data

IP address, date and time of access, pages viewed, referral source, browser, operating system and device type, technical identifiers and cookie data. When web analytics is enabled, anonymised or pseudonymised information about activity on the website may also be processed.

The operator does not seek to process special categories of personal data or biometric personal data. Visitors should not include such information in free-text fields or emails unless it is necessary for the enquiry.

03 Purposes and legal grounds

Responding to an enquiry

Discussing a project, preparing a proposal, contacting the visitor and taking steps at the visitor’s request before entering into a contract. The legal basis is the visitor’s consent and, where applicable, the need to take pre-contractual steps at the visitor’s request.

Operation and security

Displaying pages correctly, remembering visitor choices, preventing abuse and diagnosing errors. Only the minimum technical data needed to operate the website and protect the legitimate interests of the operator and visitors is processed.

Web analytics

Measuring traffic and improving the website’s structure, content and performance. Optional analytics is enabled with the visitor’s consent if an analytics service is connected.

04 How data is processed

Processing may be automated and, when handling enquiries, non-automated. It may include collection, recording, organisation, accumulation, storage, correction, retrieval, use, granting necessary access to processors, restriction, deletion and destruction.

Before the form is submitted, text and voice messages remain in browser memory. The microphone is activated only after a visitor action and browser permission. Sound-level analysis occurs on the visitor’s device. Unsent recordings are deleted when the page reloads and are not written to local storage.

When the form is submitted, the entered information and selected voice messages are sent to the enquiry processor. Audio files are stored temporarily for validation and conversion to MP3, then the temporary files are deleted. The enquiry, recordings and a consent snapshot are delivered to the operator through a private Telegram bot chat and remain in the cloud chat until the operator deletes them. When a visitor uses the direct email link, the visitor sends the message from their own email application.

The operator does not publish or sell personal data and does not make solely automated decisions based on it that produce legal effects for the visitor.

05 Cookies and local storage

The website uses essential browser storage. The kado_motion_intro cookie, retained for up to 7 days, records whether motion-control guidance has been shown. The kado_cookie_notice cookie, retained for 30 days, records that the cookie notice has been seen. The kadonext-preload-seen local-storage entry remembers that the intro has been shown and remains until the visitor clears website data. These entries contain no name or contact details and are required for requested interface behaviour.

If Yandex Metrica is connected, it may set its own cookies and process technical visit data. The analytics counter will run only after separate consent. A way to change or withdraw that choice will be provided at the same time. Declining analytics does not restrict core website functions, and stored files can be deleted through browser settings.

Blocking all cookies may affect remembered interface settings but does not prevent access to website content.

06 Yandex Metrica, Telegram and other parties

The operator may use Yandex Metrica, supplied by YANDEX LLC (16 Leo Tolstoy Street, Moscow 119021, Russia), for web analytics. When enabled, Yandex processes visit and device data on the operator’s instructions. The operator must not send form content, contact details, CRM data or other information that directly identifies a visitor to Metrica.

Yandex processing is governed by the Yandex Metrica terms and the Yandex privacy policy.

The operator may use the Telegram Bot API, supplied by Telegram Messenger Inc., to deliver enquiries. Telegram receives information voluntarily included in the enquiry, selected voice messages, the submission date and confirmation of consent. Telegram is a cloud service; ordinary cloud chats, including bot messages and files, are stored on Telegram servers.

Telegram processing is governed by the Telegram Privacy Policy. This delivery channel is enabled only after applicable requirements concerning commissioned processing and cross-border transfer have been met.

Hosting, information-security, email and message-delivery providers may also access data to the extent necessary to provide their services, perform their contract with the operator and comply with law. The operator requires confidentiality and appropriate protection. Data is disclosed to other parties only with the data subject’s consent or on another legal basis.

07 Retention, storage and destruction

Enquiry data is processed until correspondence ends and then for no more than three years after the last substantive contact, unless a contract or law requires longer retention. When the purpose has been fulfilled, data is deleted or anonymised unless another lawful basis for storage applies.

Technical and analytics data is retained within the periods set by the relevant service and required for the purposes stated in this Policy, or until consent is withdrawn, whichever applicable end condition occurs first.

When personal data of Russian citizens is collected, its recording, organisation, accumulation, storage, correction and retrieval use databases located in the Russian Federation, except where the law expressly provides otherwise. Delivery through Telegram may involve a cross-border transfer of the information and files supplied by the visitor. Such transfer occurs under separate informed consent and only after statutory requirements have been met.

08 Visitor rights

A visitor may obtain information about processing; request correction, restriction or deletion; withdraw consent; object where lawful grounds exist; and lodge a complaint with Roskomnadzor or a court.

A request or withdrawal may be sent to hello@kadonext.com with the subject “Personal data”. The operator may request information needed to verify the applicant’s identity and connection to the data. Withdrawal does not affect processing lawfully carried out before it was received and does not prevent processing under another legal basis.

09 Data protection

The operator takes the necessary legal, organisational and technical measures to protect personal data against unlawful or accidental access, destruction, alteration, restriction, copying, disclosure, distribution and other unlawful acts. Access is granted only to people who need it for a specific task.

10 Changes to this Policy

The operator updates this Policy when the scope of processing, services used or legal requirements change. A new version takes effect when published on this page. The date of the current version appears at the beginning of the document.