Skip to content

Legal

Cookie Policy

Last updated Version 1.0

In short

  • FireFunc sets cookies only to keep you signed in and to finish connecting a tool. It sets no analytics or advertising cookies, and no one else sets cookies through firefunc.com.
  • Your theme and a few display preferences are kept in your browser’s local storage. They stay in your browser.
  • Every cookie here is needed for something you asked for, so we do not ask for consent to them. If we ever want one that is not, we will ask first.
Contents
  1. 1. What cookies and browser storage are
  2. 2. The cookies FireFunc sets
  3. 3. Cookies set by other services
  4. 4. What the app keeps in your browser
  5. 5. No analytics or advertising
  6. 6. Your choices
  7. 7. What would change this
  8. 8. Contact

1. What cookies and browser storage are

A cookie is a short piece of text a website asks your browser to keep and send back on later visits. Local storage and session storage are places in your browser where a page can keep small values for itself; unlike cookies, the browser does not send them anywhere. Session storage is cleared when you close the tab.

2. The cookies FireFunc sets

All of them are set by firefunc.com itself. Each is marked HttpOnly, so scripts on the page cannot read it; Secure, so it only travels over an encrypted connection; and SameSite=Lax, so other sites cannot make your browser send it with their requests.

Signing in and connecting tools
CookieWhat it is forHow long it lasts
ff_sessionKeeps you signed in. It holds the access token Amazon Cognito issued when you signed in, which FireFunc checks on each request.1 hour. Renewed from ff_refresh while you use FireFunc; removed when you sign out.
ff_refreshRenews ff_session, so you are not asked to sign in again every hour.30 days from when you signed in; removed when you sign out.
ff_pkce, ff_oauth_stateSet only if sign-in goes through Amazon Cognito’s own sign-in page. They tie that page’s answer to the sign-in you started, so it cannot be forged or replayed.10 minutes; removed as soon as sign-in completes.
ff_connectSet while you connect a tool such as GitHub or Jira. It remembers which workspace, project and tool you were connecting, and a one-time value the tool must send back.10 minutes; removed when you return from the tool.
ff_connect_mcpThe same, while an organization signs in to an MCP server.10 minutes; removed when you return.

FireFunc’s staff console sets its own versions of the sign-in cookies. Only people who sign in to that console receive them.

The staff console
CookieWhat it is forHow long it lasts
ffa_sessionKeeps a member of FireFunc staff signed in to the staff console.30 minutes. Renewed from ffa_refresh; removed on sign-out.
ffa_refreshRenews ffa_session.30 days, though the sign-in it holds stops working after 7 days; removed on sign-out.
ffa_pkce, ffa_oauth_stateThe same protection as ff_pkce and ff_oauth_state, for the staff console.10 minutes; removed when sign-in completes.

3. Cookies set by other services

None are set through firefunc.com. The scripts, fonts, images and film the site loads all come from firefunc.com itself, so no other service learns of your visit from them.

When you leave FireFunc to connect a tool — GitHub, Atlassian, Linear, Sentry, Slack or Figma, for example — or when signing in or out passes through Amazon Cognito’s own pages, you are on that service’s site, which sets its own cookies under its own policy.

4. What the app keeps in your browser

These values stay in your browser: nothing copies them to FireFunc. Local storage keeps them until you clear it; session storage, until you close the tab.

Local storage
KeyWhat it remembers
themeYour theme: Light, Dark or System, chosen with the theme switch on the site or in Settings → Preferences.
firefunc:workspace, firefunc:project:…The workspace you last had open, and the project you last chose in each workspace.
firefunc:v2:landing, firefunc:v2:timestampsSettings → Preferences: the screen a new tab opens on, and whether times are shown as “3h ago” or as a date.
firefunc:v2:railWhether you collapsed the side rail.
firefunc:getting-started:…That you dismissed Getting started on Home, for that workspace.
firefunc:v2:tasks-explainerThat you closed the explainer on a project’s Tasks tab.
ff.review.sortHow you sort the Review list.
Session storage
KeyWhat it remembers
firefunc:v2:entry, firefunc:v2:landedWhich page this tab opened on, so Home sends you to your chosen screen only once.
ff:stale-deploy-reloadWhen the page last reloaded itself because a new version of FireFunc was released, so it never reloads in a loop.

5. No analytics or advertising

FireFunc uses no analytics, advertising, social media or tracking cookies, pixels or scripts. We do not follow you across other websites, and we do not build a profile of your visits.

6. Your choices

  • Signing out removes ff_session and ff_refresh. The others expire on their own within 10 minutes.
  • You can block or delete cookies in your browser’s settings. If you block the ones above, you cannot sign in to FireFunc or connect a tool.
  • Clearing this site’s data in your browser removes what the app keeps in local storage; your theme and preferences return to their defaults.

7. What would change this

If we ever add a cookie, or anything kept in your browser, that is not needed for something you asked for — analytics, for example — it will be listed here before it is used. Where the law requires consent, we will ask for it first, and saying no will be as easy as saying yes.

The date and version at the top of this page change whenever this policy does. How we handle personal data more broadly is in the Privacy Policy.

8. Contact

Questions about cookies or anything else on this page: admin@firefunc.com.