Cookie Policy

Baxtlilar · Edition in force from the date of official publication · Version 1.3 · English

BAXTLILAR · LEGAL DOCUMENTS

English

Version 1.3 · Enters into force on the date of its official publication on the Baxtlilar Platform.

Operator: “Bahtli bo‘laman” LLC. Current edition: baxtlilar.app and Telegram Mini App.

1.1. This Policy explains the use of cookies and similar technologies on the informational website https://baxtlilar.app and, to the extent applicable, in the related web components of Baxtlilar.

1.2. The main user service of the MVP operates through Telegram Mini App. Telegram Mini App may use the technical mechanisms of Telegram, browser storage, SDK, server logs and other technologies that are not always cookies in the classical sense.

1.3. This Policy applies together with the Baxtlilar Privacy Policy. If a cookie or a similar identifier is linked to personal data, its processing is also governed by the Privacy Policy and the applicable consents.

1.4. Baxtlilar does not use cookies for the covert reading of the profile, correspondence, documents, verification selfie or other sensitive data.

2.1. Cookies are small files or records that a website may store in the user’s browser for the operation of functions, security, the saving of settings and, where the relevant tools are in place, analytics.

2.2. Similar technologies may include local storage, session storage, SDK, pixels, tags, server logs, UTM tags, technical session identifiers and analytics events.

2.3. Session cookies usually remain valid until the browser is closed. Persistent cookies may be stored for longer — within the period set for the specific purpose.

2.4. First-party cookies are set by Baxtlilar itself. Third-party cookies or similar identifiers may be set by an external provider only where the relevant service is actually connected.

4.1. Until external web analytics or advertising tools are actually connected, Baxtlilar proceeds from a minimal model: mandatory technical cookies/storage necessary for the correct operation of the website and the saving of cookie settings.

4.2. If functional storage is required for language or other user settings, it is used only for the relevant purpose.

4.3. Analytical and advertising cookies must not be declared as actually in use if the specific tools have not yet been connected.

4.4. Before the production launch, the team must compile an actual Cookie Inventory: the name of the cookie/identifier, the provider, the purpose, the category, the retention period, the first-party/third-party status and the country/region of processing, if applicable.

4.5. Before the edition in force is published, the responsible specialist checks the Cookie Inventory against the actual cookies, localStorage/sessionStorage, embedded scripts and SDK in the production build. The need for a banner and a refusal mechanism is determined on the basis of the optional categories actually connected and the applicable rules.

5.1. A technical session identifier or cookie preference.

5.2. The IP address and the approximate technical location at country/region level, if it is generated by the technical infrastructure.

5.3. The device type, browser, operating system, language and version of the software environment.

5.4. The date and time of the visit, the URL/page, the referral source, UTM tags and the fact of a transition to Telegram Mini App.

5.5. Technical errors, page response time and other diagnostic events.

5.6. The user’s choice regarding the optional categories of cookies.

5.7. If analytics is connected later, the list of events actually collected must correspond to the published policy and must not include hidden sensitive profile data, documents or private correspondence.

6.1. Ensuring the correct and secure operation of https://baxtlilar.app.

6.2. Saving the selected language, region and available user settings.

6.3. Remembering the user’s decision on the cookie-banner and the optional categories.

6.4. Prevention of abuse, technical diagnostics and the elimination of errors.

6.5. Measuring website traffic and improving the structure of the website — only if an analytical tool is actually connected.

6.6. Evaluating advertising click-throughs and campaigns — only if an advertising tool is actually connected and the consent requirements have been met.

6.7. Understanding the user’s transition from the informational website to the official Telegram Mini App without building a hidden profile of sensitive characteristics.

7.1. If optional analytical or advertising cookies are used on the website, the cookie-banner must allow the user to make a real choice before they are activated, where this is required by the legislation.

7.2. At a minimum, clear actions must be available to the user: to accept the optional categories, to reject them or to customise the choice, if several categories are used.

7.3. Refusal of optional cookies must not block access to the informational content of the website, except for functions that objectively depend on a specific permission.

7.4. Mandatory cookies may be used to the extent necessary for the operation and security of the website, even if the user has rejected the optional categories.

7.5. The user’s choice must be retained for a reasonable period and may be changed through the available “Cookie settings” mechanism, if such a mechanism is used.

8.1. In this version, Baxtlilar does not list third-party analytics/advertising services that have not actually been approved and connected.

8.2. If a third-party service is connected, its purpose, the list of data, the retention period, the transfer conditions, the contractual role, the country of processing and the applicable safeguards must be determined before production use.

8.3. If a third-party provider acts as an independent operator/controller of particular data, the user must be informed of this in a clear form and, where necessary, receive a link to its applicable terms.

8.4. The connection of a new provider that materially changes the processing of cookies or the cross-border transfer is a ground for updating this Policy and, where required, for a new consent.

9.1. If a cookie, SDK, pixel or other identifier is linked to personal data, its use is also governed by the Baxtlilar Privacy Policy.

9.2. The storage and cross-border transfer of such data must comply with the applicable legislation of the Republic of Uzbekistan and the actual architecture of the provider.

9.3. Before connecting a service that processes data outside Uzbekistan, Baxtlilar must assess the legal basis, the appropriate cross-border transfer mechanism and the information/consent requirements.

9.4. The Cookie Policy does not replace the registration of a personal data database or other obligations of the Operator, if they arise by law.

10.1. The final specific periods for third-party cookies must not be published “by eye”: they are filled in after the actual provider has been selected and its settings have been checked.

11.1. If a cookie-banner or a settings centre is in operation on the website, the user may use it to manage the optional categories.

11.2. The user may also delete or restrict cookies through the settings of their browser.

11.3. Blocking mandatory technical cookies at browser level may result in the incorrect operation of particular functions of the website.

11.4. Changing the cookie settings does not necessarily delete data that was previously lawfully processed and must be retained on another basis.

12.1. Baxtlilar must not use cookies or similar technologies for the covert analysis of religious beliefs, family history, private correspondence, documents, verification selfie or other sensitive data for advertising targeting.

12.2. Cookies must not be used to covertly change Matching, Compatibility Score or the availability of candidates depending on the user’s advertising profile.

12.3. The cookie-banner must not use misleading wording or an interface that artificially makes it difficult to refuse the optional categories.

12.4. Refusal of advertising or analytical cookies does not affect the basic security of the account, Block/Report and the user’s rights within Telegram Mini App.

13.1. https://baxtlilar.app performs an informational, reference and legal function and may direct the user to Telegram Mini App.

13.2. Telegram and the built-in webview may use their own technical mechanisms, cookies or local storage, which are partly outside the control of Baxtlilar and are also governed by the rules of the relevant platform.

13.3. Baxtlilar is responsible for its own scripts, SDK, trackers and configuration that the team deliberately connects to its website or Mini App.

13.3a. In order to control the actual mechanisms on the Airnet infrastructure and in Telegram Mini App, a single Cookie/SDK/Storage Inventory is compiled. Data transferred to external analytics or advertising tools is not declared to be hosted in Airnet solely on the basis of own hosting.

13.4. Before connecting a new SDK or tracking tool, the team must assess what data it collects, whether it is really needed and whether it requires an update of the Privacy Policy, Consent Registry or Cookie-banner.

14.1. Baxtlilar updates this Policy when the cookies, SDK, analytics/advertising providers actually used, the purposes of processing or the applicable legislation change.

14.2. A material connection of a new optional tracking tool must be accompanied by an update of the Cookie Inventory and of the user consent interface.

14.3. The current edition is published at https://baxtlilar.app and, if necessary, is accessible from Telegram Mini App.