Sign-in cookies
The gitflare_session cookie maintains a signed-in session. It ends after seven days without use and no later than 30 days after sign-in; while you use Gitflare it is renewed at most once an hour. It is HttpOnly, Secure and SameSite=Lax, and changes made with it must come from Gitflare itself. Sign-out clears the browser cookie.
When the website and the app use separate addresses on the same domain, a gf_signed_in cookie tells the website to show a link to your workspace instead of sign-in. It holds no account information and grants no access. It is Secure and SameSite=Lax, lasts no longer than the 30-day session limit, and is cleared on sign-out or when the app finds the session has ended.
Cloudflare sign-in and account-linking use short-lived browser-binding cookies, including __Host-gitflare-signin-state and __Host-gitflare-cloudflare-link, with a ten-minute maximum age. Cloudflare resource connections also use short-lived authorization state. OAuth client consent uses browser-bound authorization state managed by the OAuth provider.
Interface and navigation storage
Local storage saves your gitflare-theme preference and diff-view preferences. Session storage can hold the route to return to after sign-in and whether an owner-token notice has been acknowledged. These settings support the interface; they are not evidence of an active server session.
Cloudflare and connected services
Cloudflare may set additional cookies when a deployment enables services that require them. Cookies set by Cloudflare sign-in or other external services are governed by those services' notices. Their presence depends on the deployed configuration.
Managing storage
You can inspect and clear cookies and site storage in your browser. Blocking sign-in or authorization cookies can prevent those features from working. Clearing local storage resets saved interface preferences; sign out or revoke a session to end its server authorization. Questions can be sent to privacy@gitflare.io.