Cookie policy
Last updated 27 August 2026
[FILL IN] need real values before publication.GitSearch sets three cookies. All three are strictly necessary for the service to work, none of them tracks you, and no third party sets a cookie through this site. That is why the banner tells you about them rather than asking your permission: under Article 5(3) of the ePrivacy Directive, as implemented in Germany by § 25(2) TTDSG, and under the equivalent rule in Serbian law, consent is not required for cookies that are strictly necessary to provide a service the user has expressly requested.
1. The cookies we set
| Name | Purpose | Lifetime |
|---|---|---|
authjs.session-token | Keeps you signed in. Contains a signed token identifying your user; your role and permissions are read from the database on every request, not from the cookie. | 12 hours |
authjs.csrf-token | Protects forms against cross-site request forgery. | Session |
gs_cookie_consent | Records that you have seen the cookie notice, so it is not shown on every page. | 12 months |
2. What we do not do
We do not use analytics, advertising, remarketing, session recording, heat mapping, social plugins, embedded fonts served from third parties, or any other technology that would place a cookie or read one on behalf of someone else. No pixel, tag or script from a third party runs on this site.
Avatar images are loaded directly from GitHub's content delivery network, which means GitHub can see your IP address when a results page renders. That is an image request, not a cookie, and GitHub's own privacy statement governs it. [FILL IN — decide whether to proxy avatars through our own servers to avoid this; note the bandwidth cost.]
3. If that changes
If we ever introduce analytics or any other non-essential cookie, the banner will change from a notice into a genuine choice with a working reject option, no non-essential cookie will be set before you choose, and this page will list what was added and why. We will not quietly repurpose the existing cookies.
5. Questions
Write to [FILL IN — privacy@bluegrid.io]. See also our privacy policy.