Cookie policy.

TrackForge LLC (“TrackForge,” “we,” “us”) uses the cookies and browser-storage values listed below.

This policy sits alongside the Privacy Policy, which covers everything else we do with personal information.

1. What these technologies are

A cookie is a small text file a site stores in your browser and sends back on later requests. Local storage is a related browser feature that keeps values on your device until the site reads them for the related feature. TrackForge uses both, only for the purposes below.

2. Cookies we set

These are sent back to a server on requests, which is what makes them cookies rather than device-only storage.

• Clerk session cookies

  Keeps you signed in and protects your account against session theft.

  Set by Clerk, our authentication provider Per Clerk's session lifetime

• sidebar_state

  Remembers whether the app sidebar is expanded or collapsed, so the layout does not reset on every page load.

  Set by TrackForge Expires after 7 days

• tf_post_auth_redirect

  Set only when you follow a link that requires signing in first, such as a team invitation. Holds the page you were trying to reach so we can return you there.

  Set by TrackForge Expires after 30 minutes, and cleared the moment it is used

3. Values stored on your device

These stay in your browser’s local storage and are not attached automatically to every request. TrackForge reads or submits the two values identified below when their related features run; the remaining preferences stay on the device.

• trackforge-active-org

  Which organization your view is scoped to, so switching context survives a reload. The app reads this value to scope later queries and writes to that organization.

  Until you clear site data

• trackforge-theme

  Whether you asked for the light theme, the dark theme, or for TrackForge to follow your device. Written only if you use the theme control; following your device is the default.

  Until you clear site data

• trackforge-welcome-tour-seen

  Whether you have finished the introductory tour, so it does not reappear.

  Until you clear site data

• trackforge.style-quiz.v1

  Your answers to the optional training-style quiz, the knowledge packs they matched, and when you completed it.

  Until you clear site data

• trackforge:referral-code

  A referral code from a shared sign-up link. After your account exists, the app submits the code once to claim the offer and then clears it. The code identifies the offer, not the person who shared it.

  Until it is used, or you clear site data

• trackforge:calendar-view: + your user id

  Whether you last viewed the calendar by month, week, or agenda.

  Until you clear site data

• trackforge:section-card: + the section id

  Whether you collapsed a section of a page, so it stays that way the next time you open it. One entry per section you have collapsed or reopened, holding only the word open or closed.

  Until you clear site data

• trackforge_live_strength_draft

  An in-progress weight-room session, written only in the demo version of TrackForge, which has no account and no server storage.

  Until the session is finished, or you clear site data

4. What we do not use

TrackForge sets no advertising cookies, no retargeting cookies, no cross-site tracking cookies, and no third-party analytics-profiling cookies. We embed no advertising pixels and no social-network tracking pixels. We do not sell or share the contents of any value listed above.

5. Why there is no cookie banner

Consent rules under the EU ePrivacy Directive, the UK PECR, and comparable US state law apply to storage that is not strictly necessary for a service the user asked for. Every item above is either:

• Strictly necessary. Required to sign you in and keep you signed in.
• A preference you set. Something you chose inside the application, stored so the application behaves the way you left it.

Neither category requires opt-in consent, so TrackForge does not interrupt you with a consent banner.

TrackForge does record how the product is used, and it is worth being exact about why that does not change the answer above. Those records are written on our servers, as a by-product of actions you take in the app. Nothing is stored on or read from your device to produce them: no analytics cookie, no browser storage value, no pixel, no fingerprint, and no third-party script. The consent rule in this area is about storage on your device, which is why it is not engaged here. That processing is also yours to switch off in Settings, and switching it off deletes what has already been recorded rather than only stopping what comes next. See “Product usage data” in the Privacy Policy for what is recorded and what is deliberately not.

If we ever add advertising, cross-site tracking, or any analytics that stores or reads something on your device, we will implement consent controls before that change takes effect, not after.

6. Do Not Track and Global Privacy Control

Some browsers send a Do Not Track (DNT) header or a Global Privacy Control (GPC) signal. Both are ways of asking a site not to sell your personal information, share it for cross-context behavioural advertising, or use it for targeted advertising.

TrackForge does none of those things for any user, whether or not a signal is present. There is no advertising, no data sale, and no cross-context tracking to opt out of, so on the question the signal actually asks, the answer is already the one it is asking for.

TrackForge does not sell personal information, share it for cross-context behavioral advertising, or use it for targeted advertising. DNT and GPC therefore do not change those practices. Product usage recording is controlled separately in Settings.

7. How to control these

You can delete cookies and local storage at any time through your browser’s site-data settings, and you can block cookies entirely. Doing so will sign you out and reset the preferences above. Nothing else is lost, because your training data lives in your account, not in your browser. Blocking the Clerk session cookie will prevent you from signing in at all.

8. Changes to this policy

We will update this policy and revise the “Last updated” date when the list changes.

9. Contact us

Questions about this policy? Email us at hello@trackforge.fit, or write to us at TrackForge LLC, 550 Congressional Blvd, Suite 390 #1059, Carmel, IN 46032, United States. That address is our business mailing address and is listed to identify us; email is the channel that reaches us fastest.