Privacy policy

1. Who runs this site

ksim.pro is a personal site for an independent technology consulting practice. The operator is a private individual. The only contact channel is the form on the home page or email m@ksim.pro.

2. What I collect

There are two situations in which your data reaches me or my service providers.

When you send the contact form

• Name and reply channel (email or messenger handle) that you type in.
• Message text, its length and the time of submission.
• On landing pages: your role and company, if you fill them in.
• Technical metadata: sender IP address and browser fingerprint (used for anti-spam and incident review).
• Yandex.Metrika ClientID - a random browser identifier used for conversion attribution (see section 5).

When you simply browse the site

• Standard web server logs: IP, request time, path, User-Agent header, referrer.
• Analytics data from Yandex.Metrika and Google Analytics 4 (see section 5).
• Technical cookies of the Cloudflare Turnstile anti-bot service - only if you interact with the contact form.
• A lang cookie - set when you manually switch between RU and EN.

3. Why I collect it

• To answer your message and follow up on whatever you wrote about.
• To understand which pages and notes are useful and which are not.
• To defend the form against spam and automated bots.
• To comply with applicable law and keep proper records of contact.

Your data is not used for automated scoring, advertising, or any commercial transfer to third parties.

4. Legal basis

Personal data is processed under Russian Federal Law 152-FZ "On Personal Data". If you reach out from a jurisdiction with stricter rules (for example the EU under the GDPR or the UK under the UK GDPR), I treat your request under those rules as well. The bases I rely on:

• Your consent, expressed by action - submitting the form or messaging me.
• Pre-contract communication and contract performance - the conversation that follows.
• Legitimate interest of the operator - fraud prevention, security logging, audience analytics.

5. Analytics and third parties

The site embeds third-party tools. They receive data under their own privacy policies, which I do not control directly.

• Yandex.Metrika (Yandex LLC, Russia) - counter, WebVisor session replay, click heatmaps. May record user actions in an anonymised form. Yandex policy.
• Google Analytics 4 (Google LLC) - aggregated visit stats. Google policy.
• Cloudflare Turnstile (Cloudflare Inc., USA) - form anti-bot protection. Cloudflare policy.
• Telegram (Telegram FZ-LLC) - the text of your message is delivered to me via Telegram so I can reply. Telegram policy.

If you do not want your visit recorded by analytics, disable third-party cookies in your browser settings, use private browsing with a tracker blocker, or write directly to the email address instead of using the form.

6. How long I keep the data

• Contact-form payloads - up to 3 years from the last interaction with you (so I can pick up the conversation later, and for reporting).
• Web server logs - up to 90 days.
• Analytics provider data - according to each provider's own retention policy.

On a reasoned request, data is deleted earlier.

7. Who the data may be shared with

• The infrastructure providers listed in section 5, only to the extent their services require.
• The site's hosting provider, in the form of technical logs.
• State authorities, only when a binding legal request requires it.

No sale or commercial exchange of personal data takes place.

8. Your rights

• Ask what data about you is being processed.
• Request correction or deletion.
• Withdraw consent for processing.
• File a complaint with the competent supervisory authority in your country (and in Russia, with Roskomnadzor).

For any of these, write to me through the form on the home page or via the email address - I respond personally.

9. International transfers

Embedded third-party services may process data outside Russia (Google, Cloudflare, Telegram). If that is a deal-breaker for you, do not submit the form and do not use messengers - just send an email.

10. Changes to this policy

If the toolset or processing approach changes, this text is updated and the date at the top changes with it. For substantive changes that affect data already submitted, I let the affected people know directly through the existing conversation.