Cookie Policy
Gitfile uses a minimal, essential-only set of cookies (three in total). No advertising, tracking, or third-party analytics cookies.
Last updated October 3, 2026
Cookies we use
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
| gitfile_session | Keeps you signed in to your dashboard. | Essential, httpOnly | 30 days |
| gitfile_oauth_state | CSRF protection during the GitHub sign-in redirect (also carries whether the flow is a login or a private-access upgrade, and, for sign-ins, the version of the legal documents you accepted). | Essential, httpOnly | 10 minutes at most — deleted right after sign-in completes |
| gitfile_gitlab_oauth_state | CSRF protection during the GitLab sign-in redirect (also carries the version of the legal documents you accepted). | Essential, httpOnly | 10 minutes at most — deleted right after sign-in completes |
Theme preference (not a cookie)
Your light/dark mode choice is stored in your browser's localStorage, not a cookie. It never leaves your device and we never read it server-side.
Third parties
GitHub's and GitLab's own sign-in pages (github.com, gitlab.com) may set their own cookies when you authenticate there — that's governed by their respective privacy policies, not this policy. Gitfile itself doesn't embed any third-party analytics, advertising, or tracking scripts.
Managing cookies
gitfile_session and gitfile_oauth_state and gitfile_gitlab_oauth_state are strictly necessary to sign in and stay authenticated, so there's no separate opt-out while staying signed in — you can always clear cookies in your browser, or sign out or disconnect your provider from the dashboard to end your session outright. Blocking these cookies will simply prevent Gitfile from keeping you signed in.
Changes
We'll update the date above if the cookies we use ever change — for instance, if we add optional analytics in the future, we'll disclose it here first and give you a way to opt out. See also our Privacy Policy.
Contact
contact@gitfile.dev — Starhub SPA, Chile.