Cookie Notice
Version 1.3, effective June 9, 2026
This Cookie Notice explains how NobGit uses cookies and browser storage.
Short version: NobGit currently uses only necessary cookies and browser storage for login, account security, form protection, signup/verification, Google Sign-In session protection, and user-requested interface preferences. NobGit does not currently use analytics cookies, advertising cookies, marketing pixels, cross-site tracking cookies, or third-party tracking scripts. If a user chooses Google Sign-In, the user is redirected to Google-controlled pages where Google may use its own cookies or account security technologies under Google's own policies.
1. What Cookies and Browser Storage Are
Cookies are small pieces of data stored by your browser. Browser storage, such as local storage, can also store small pieces of data in your browser. NobGit uses these technologies only where they are needed to provide the service, protect accounts, protect forms, or remember a setting requested by the user.
2. What NobGit Uses
| Type | Purpose | Duration | Third-party advertising/tracking access |
|---|---|---|---|
| Session cookies | Keep users signed in and support login, signup, email verification, OTP, passkeys, and account sessions. | Session-based or until logout, expiry, replacement, or browser cleanup. | No. |
| Security cookies or tokens | Protect forms, requests, sessions, sign-in attempts, account actions, and anti-abuse checks. | Short-lived, session-based, or until the related security action expires. | No. |
| Local browser storage |
Remember user interface preferences, such as
nobgit-theme
for dark mode or light mode.
|
Until the user changes the setting, clears browser storage, or resets the browser profile. | No. |
| Cloudflare security data | Route traffic, protect NobGit and abuse forms, reduce spam, and defend against automated or harmful traffic. This may include Cloudflare Turnstile or other Cloudflare security services where enabled. | Handled by Cloudflare according to its security service behavior and NobGit configuration. | No advertising use by NobGit. Cloudflare may process technical data for security and traffic delivery. |
| Google Sign-In redirect and OAuth state data | Support optional Google signup, login, and account linking. NobGit uses temporary session state, nonce values, and redirect metadata to protect the Google OAuth/OpenID Connect flow. | Temporary, session-based, or until the sign-in attempt expires, is completed, is cancelled, or browser/session cleanup occurs. | No advertising use by NobGit. Google-controlled pages may use Google cookies or account security technologies under Google's own policies when the user leaves NobGit to sign in with Google. |
If NobGit later adds analytics, advertising, tracking, embedded marketing tools, or any non-essential third-party cookies or scripts, NobGit will update this notice and add a cookie consent mechanism before those tools run.
NobGit only uses cookies and browser storage that are necessary for login, security, sessions, account actions, Google Sign-In session protection, and user-requested interface preferences.
NobGit does not currently use analytics cookies, advertising cookies, marketing pixels, cross-site tracking cookies, behavioral advertising tools, or third-party tracking scripts.
No Analytics or Tracking Cookies
3. Google Sign-In and Google-Controlled Pages
When a user chooses Google Sign-In, NobGit redirects the user to Google-controlled authentication pages. NobGit does not set Google cookies on NobGit-controlled pages for advertising or analytics. Google may use its own cookies, account session tools, fraud prevention tools, and security checks on Google-controlled pages or within the user's Google account environment.
Blocking cookies or browser storage may prevent Google Sign-In from completing because both NobGit and Google need temporary state, session, or security information to protect the sign-in attempt and return the user to NobGit safely.
4. Why NobGit Does Not Show a Cookie Banner Right Now
NobGit currently uses cookies and browser storage only where they are necessary to provide the service, protect the service, keep users signed in, complete user-requested actions, or remember a user-requested display preference.
Because NobGit does not currently use non-essential analytics, advertising, tracking, or marketing cookies, NobGit does not currently show a cookie consent banner.
5. If NobGit Adds Non-Essential Cookies Later
If NobGit later adds analytics, advertising, marketing pixels, embedded marketing tools, heatmaps, cross-site tracking, or other non-essential third-party cookies or scripts, NobGit will update this Cookie Notice and add a real cookie consent mechanism before those tools run.
6. How Users Can Control Cookies and Storage
Users can control cookies and browser storage through their browser settings. Blocking or deleting necessary cookies may break login, signup, verification, passkeys, OTP, Google Sign-In, sessions, account actions, or security protections.
Users can clear local browser storage to remove stored interface preferences, such as the saved theme.
7. Related Privacy Information
For broader information about what data NobGit collects, why it is used, providers such as Hetzner, Cloudflare, and Google for optional Google Sign-In, data retention, backups, and user rights, see: Privacy & Data Handling .
8. Contact
For support or privacy questions, contact: [email protected] .
To report abuse, copyright issues, illegal content, phishing, malware, exposed credentials, or security concerns, use https://abuse.nobgit.com or email [email protected] .
9. Changes to This Notice
NobGit may update this Cookie Notice from time to time. Updates will be posted on this page with a new version or last updated date.