Effective date: February 23, 2026 | Last updated: July 17, 2026

This Cookie Policy forms part of the GitHits Legal Framework, which includes the GitHits Terms of Service, Privacy Policy, Data Processing Agreement, and Subprocessor List. If a conflict exists between this Cookie Policy and the Terms of Service, the Terms of Service will prevail.

This Cookie Policy explains how GitHits uses cookies and similar technologies (such as SDKs, pixels, and local storage) on our websites and Service.

For more information about how we process personal data, see our Privacy Policy.

1. What are cookies?

Cookies are small text files that websites place on your device. Similar technologies include local storage, pixels, and SDK identifiers. We use these technologies to operate the Service, remember preferences, understand how users use the Service, and measure the performance of our marketing campaigns.

2. Types of cookies we use

2.1 Strictly necessary cookies

We require these cookies for core functionality, and you cannot switch them off in our systems. They include authentication and session cookies, security cookies, cookie preference records, and load balancing or performance cookies that we need to deliver the Service.

For example, we may store githits-auth-token at the .githits.com domain so your authenticated session can work across GitHits apps. We also store gh_cookie_consent to remember your cookie preferences.

2.2 Functional and support cookies

Functional cookies help remember your settings and preferences (such as theme or language). Support cookies help provide customer support, including keeping support conversations available across GitHits apps.

Intercom is our main support channel in the GitHits web app. Intercom may set cookies so the support messenger can work consistently across githits.com and app.githits.com. These support cookies are separate from analytics cookies and are not disabled when you decline analytics cookies.

2.3 Analytics cookies

We use analytics and observability technologies to understand how users interact with the Service, diagnose issues, monitor performance, and improve features. These tools may include product analytics, real user monitoring, application performance monitoring, and error diagnostics.

Analytics cookies and similar trackers may collect information such as page views, clicks, device and browser details, and event timing. Depending on the configuration, they may also receive identifiers that we associate with your account.

We set analytics cookies only after you provide consent, where applicable law requires consent (such as under the ePrivacy Directive, as each EEA member state has transposed it into national law). If you do not consent, we will not place analytics cookies on your device.

Before you answer the cookie banner, or if you decline analytics cookies, we may still use analytics and observability tools in modes that do not store analytics cookies or persistent analytics storage in your browser, such as cookieless or memory-backed session modes. In those modes, we do not attach account identifiers or account-level properties to analytics or observability events. If you accept analytics cookies, we may use cookie-backed analytics and observability features, including interaction measurement, performance telemetry, error diagnostics, and masked session replay where configured.

2.4 Advertising measurement cookies

With your consent, we use the Google Ads tag to measure conversions and understand the performance of campaigns that direct visitors to GitHits. Google may receive information such as the page URL, referrer, ad-click identifiers, device and browser details, and conversion events. Google Ads may set first-party cookies with names beginning _gcl_ to retain campaign attribution. For more information about Google’s processing, see the Google Privacy Policy.

The Google Ads tag is blocked until you accept the advertising measurement category. We disable advertising personalization and remarketing signals, and we do not enable Google Analytics storage through this tag. If you decline, we do not load the tag. If you later withdraw consent, we update the tag to deny advertising data use and remove accessible first-party Google Ads cookies.

3. Advertising and targeting cookies we do not use

GitHits does not use cookies for personalized advertising, cross-context behavioral advertising, audience targeting, or retargeting. We do not serve ads on the Service. GitHits does not embed third-party social media tracking cookies on our Service.

4. Your choices and controls

Where law requires it, we will ask for your consent before setting non-essential cookies and will provide a way to manage your preferences. You can reopen cookie preferences from the Cookie Settings control in the website footer. Most browsers also allow you to control cookies through their settings, although blocking some cookies may affect the Service.

Because we do not sell or share your data for behavioral advertising (as Section 3 describes), privacy signals such as Global Privacy Control (GPC) function as an opt-out request for our optional analytics and advertising measurement cookies. When GPC is active, we keep those categories rejected and use cookieless analytics measurement only, where applicable. We do not load the Google Ads tag in response to GPC-enabled visits.

5. How long cookies last

Some cookies last only for the duration of your browser session and are deleted when you close the browser. Others persist for longer periods. We retain persistent cookies for no longer than is necessary to fulfill their purpose, and in no event longer than 13 months, unless applicable law requires otherwise.

We may update this Cookie Policy from time to time and will update the effective date above.

7. Contact

1604 Philadelphia Pike, Suite 150, Wilmington, DE, 19809, US

Email: support@githits.com

GitHits Cookie Policy