Cookie and tracking technology policy

E
ffective Date: April 20, 2026

1. General Provisions and Principle of Transparency

1.1. This document (the "Policy") defines the principles of using cookies and similar tracking technologies on git2log.com (the "Website"), operated by GIT2LOG LLC / JSC Git2Log Kazakhstan (the "Controller"). This Policy is an integral part of our overarching Privacy Policy.
1.2. Principle of Data Minimalism: The Controller categorically rejects the deployment of aggressive marketing trackers, profiling systems (retargeting mechanisms designed to share data with third parties for sales conversion), and global ad networks.
1.3. We provide Users with granular, explicit control over tracking technologies through an interactive cookie widget, in strict compliance with the General Data Protection Regulation (GDPR) and the ePrivacy Directive.

2. Classification and Purpose of Technologies

The Website’s architecture integrates three strictly isolated categories of cookies. Users have the absolute right to manage the status of Analytical and Third-Party files at any time. By default, all non-essential cookies are strictly blocked (Opt-In approach).

2.1. Strictly Necessary (Essential) Cookies This category is an integral part of the Website's technological core and cannot be disabled by the User.

• Purpose: To ensure the fundamental functionality of the web interface, including maintaining session state, applying user interface preferences (Light/Dark themes), and storing cryptographic tokens to mitigate Cross-Site Request Forgery (CSRF) and other network attacks.
• Consent State & Retention: Session cookies expire immediately upon closing the browser. The cookie responsible for memorizing your choices in the cookie widget is retained for exactly 6 months (180 days), after which your consent will be requested again to ensure your preferences remain current.
• Lawful Basis: Article 5(3) of the ePrivacy Directive and the Controller’s Legitimate Interest (Art. 6(1)(f) GDPR) in maintaining Website integrity. Disabling these files via browser settings will result in fatal UI failures.

2.2. Analytical Cookies (Internal Infrastructure) Unlike standard market practices, the Controller does not deploy external analytics platforms (e.g., Google Analytics).

• Purpose: To collect aggregated traffic statistics, analyze web server performance, and monitor User interaction with the Website's content.
• Mechanism & Retention: Analysis is executed exclusively via the native analytics of the site backend and the parsing of web server event logs (including anonymized processing of IP addresses). Data never leaves the Controller’s secured infrastructure perimeter. Analytical cookies (if consented to) are retained for a maximum of 6 months (180 days).
• Lawful Basis: Explicit, voluntary Consent (Art. 6(1)(a) GDPR). If consent is withheld, this category remains permanently inactive.

2.3. Third-Party Partner Cookies (External Integrations) The Website utilizes integration modules (widgets) provided by our authorized partner, GitHub Inc. (USA).

• Purpose: Dynamic rendering of source code, repository states, and organizational data (GitHub Organizations) directly within the Website's interface.
• Mechanism & Retention: By default, the initialization of this integration is strictly blocked. Upon receiving User consent, the browser establishes a direct connection with GitHub API servers. The lifespan of the cookies set by GitHub is determined by their internal policies; however, your local consent to activate this integration is valid for a maximum of 6 months (180 days). Withdrawing your consent via our cookie widget will immediately block further execution of the GitHub API on our Website.
• Lawful Basis: Explicit, informed Consent (Art. 6(1)(a) GDPR) and explicit consent to the proposed transfer (Art. 49(1)(a) GDPR). Refusal of this category disables the external integration entirely, while keeping all core text content fully accessible.

3. Mechanisms for Consent Management and Withdrawal

In compliance with Article 7(3) of the GDPR, the Controller guarantees that withdrawing consent is as easy as giving it.

3.1. Real-Time Interactive Management (Recommended Method): Users may initiate a review of their preferences or fully withdraw consent for third-party integrations at any time. To do so, invoke the interactive control panel by clicking the "Manage Cookies" link, permanently available in the footer of every webpage.
3.2. Browser-Level Management: Users may utilize native browser settings to force-delete or block cookies, which will result in a hard reset of all previously granted permissions. Please note that deleting Strictly Necessary cookies may reset your UI preferences. Instructions are available in the official documentation of your browser provider.

4. Absolute Priority of Automated "Do Not Track" Signals (DNT/GPC)

4.1. In adherence to the highest standards of digital ethics, the Website’s infrastructure is programmed to unconditionally subordinate to global privacy signals.
4.2. If the system detects a "Do Not Track" (DNT) or "Global Privacy Control" (GPC) signal in the User's HTTP headers, the infrastructure forcibly blocks the initialization of Analytical and Third-Party cookies, seamlessly overriding and ignoring any prior consents granted via the graphical interface.

5. Data Subject Rights & Overarching Privacy Policy

This Cookie Policy functions as a specific technological addendum and must be read in conjunction with our main Privacy Policy. For comprehensive information regarding your fundamental rights under the GDPR (including the Right of Access, Right to Erasure, and the Right to lodge a complaint with a supervisory authority), please refer to the primary Privacy Policy available on the Website.

6. Contact Information

For legally significant notices and inquiries regarding tracking technologies, please contact our Compliance Team at: privacy-en@git2log.com.