Privacy policy

Revision dated 18 November 2026. This revision applies from its publication on the website.

2026-11-18-1

1. Controller and contact details

The controller of personal data on the CaseNova website is ООО «Case Nova» (Case Nova LLC), tax identification number (INN) 309263133. The English designation describes the legal form; the registered name is retained above.

Address: Republic of Uzbekistan, Tashkent, Mirzo Ulugbek district, 235 Buyuk Ipak Yuli Street. Phone: +998 71 266 88 77. Email for personal data enquiries: casenova.tashkent@gmail.com.

2. Form data and purposes

The form collects a name and phone number. The purpose is to receive a request, contact a prospective patient and arrange a consultation or appointment. It does not request diagnoses, passport details or medical documents; do not enter these in the name field.

The page path, language, request identifier, consent confirmation and version, and receipt time are also used to process a request. The server receives technical connection information, including an IP address; its hash is used for rate limiting. Form values are not placed in URLs.

3. Consent and withdrawal

You must select the consent checkbox yourself before submitting a request. It is initially unchecked; the server rejects requests without consent. The policy version and server time of receipt are recorded with the request.

Consent covers the request, not marketing messages or optional analytics. You can withdraw it by emailing the controller. Processing based on consent then stops; if another lawful basis applies, the controller must explain the relevant limits. You may call the clinic instead of using the form.

4. Cookies and analytics

The public website integrates Google Analytics 4 and Yandex Metrica, including session replay, click and scroll maps and link tracking. These services may use cookies and similar technologies to measure visits, traffic sources and interactions. Technical information may include IP addresses, cookie identifiers, browser and device details.

There is no separate cookie panel; analytics code starts on approved public website addresses without an additional interface action. This describes the technical implementation and does not assert that its legal basis has been approved. The basis for starting optional analytics without additional consent requires assessment before publication.

You can restrict cookies in browser settings; blockers may prevent analytics loading. These measures do not guarantee that all technical requests stop. Requests and directions links do not depend on analytics consent.

5. Events and field protection

Analytics measures page views, consultation opening, form starts, successful requests and contact-link clicks. A successful request is recorded only after server confirmation. Names, phone numbers, request text and technical consent records are not added to website analytics events.

Permitted utm_source, utm_medium, utm_campaign, utm_content and utm_term values are retained for attribution. Arbitrary query parameters and recognisably sensitive values are removed before tags load. Never place personal data in campaign tags: filtering cannot recognise every name by meaning.

Form inputs use ym-disable-keys and the form area uses ym-hide-content to exclude its content from session replay. Recordings must be checked in the service dashboard after publication.

6. Recipients and request flow

Request flow: visitor → Netlify Function → Telegram Bot API → CaseNova’s private staff group. Messages are accessible to staff authorised by the clinic to handle requests. Telegram stores messages; copies may remain in notifications and participants’ devices.

Netlify provides hosting, CDN and the server function. Website code has no separate request database and does not write request bodies to public logs. Hashed rate-limit and duplicate keys are held in a function instance’s memory with a 15-minute TTL. Provider infrastructure logs and backups require separate review.

Google provides GA4; Yandex provides Metrica and the interactive map. The map loads near the contacts section and sends technical data to Yandex. The address and directions link work independently of the map. Telegram, Instagram and Yandex Maps can also be opened through external links and have their own terms.

7. Cross-border processing

Netlify, Telegram, Google and Yandex may process data outside the Republic of Uzbekistan. Storage exclusively in Uzbekistan has not been confirmed and is not claimed.

The controller must assess processing countries and contracts, grounds for cross-border transfers, and applicable database storage and registration requirements. Consent to a request does not by itself establish that all these requirements are met.

8. Retention and deletion

The controller’s retention period for a request is one year from receipt. This period must cover Telegram messages and consent records, accessible copies, logs and backups containing request data. Data should be deleted when the period ends unless a different period is legally required; any applicable exception must be justified.

Automatic deletion of Telegram messages after one year is not implemented in the website code. Assigning responsibility, tracking deadlines, deleting messages and copies, checking provider logs and backups and documenting completion are organisational implementation tasks. Technical enforcement of the one-year period is not yet confirmed.

One year applies to requests, not automatically to all third-party statistics. GA4 and Metrica retention settings, provider rules and statistical deletion options need separate review.

9. Rights and enquiries

You may request information about processing, correction, restriction or deletion of your data, withdraw consent and challenge unlawful processing in accordance with applicable law. Proportionate identity verification may be required to fulfil an enquiry.

Send enquiries to casenova.tashkent@gmail.com or the controller’s address. You can clarify the process at +998 71 266 88 77. Do not send excessive medical documents or passport details unnecessarily. Enquiries are handled under the procedures and deadlines of applicable law.

10. Security and policy revisions

The public form uses HTTPS POST, server validation, request-origin checks, size and rate limits, duplicate-submission protection and a honeypot. The bot secret is used only on the server. These measures do not guarantee absolute security; staff access, devices, logs and deletion need organisational oversight.

The current revision is published on this page. Material changes update the policy version recorded with new requests. This revision does not imply that legal review of actual processing conditions has been completed.

casenova.tashkent@gmail.com · +998 71 266 88 77

LexUZ · Law on personal data