CCB is a Facility-run training platform for Coaches, Admins, and Athletes. The product runs on the storage below, and on nothing else. This page is the complete inventory.
CCB stores only what it needs to authenticate Users, authorize anonymous Athletes, keep Work-Phase submissions recoverable across a network drop, and remember a small set of interface choices. None of it is sold, shared with advertisers, or used to build a profile of you off the platform.
Required for sign-in, anonymous Athlete access, Session authorization, and Work-Phase submission recovery. Disabling these will sign you out, remove anonymous Athlete access, or drop in-flight submissions on a network drop.
ccb.session (dev) | __Secure-ccb.session (prod)Stored under ccb.session (dev) | __Secure-ccb.session (prod).
Keeps a signed-in User authenticated in the CCB platform. The cookie carries a signed JWT and is read-only by JavaScript.
athlete_token_{sessionId}Stored under athlete_token_{sessionId}.
Proves that this browser joined a specific Session as an anonymous Athlete. The token is HMAC-bound to the Session and is read-only by JavaScript.
pendingReportFreezeHolds a Work-Phase Checksum payload that the Athlete Node could not deliver to the server after three retry attempts. The queued payload is replayed on the next page load or connectivity event.
pendingRacePracticeResultHolds a Race Practice station result that the Athlete Node could not deliver after three retry attempts. The queued value is scoped to a single station so it cannot replay against a different station.
ccb.joinAttempt:{sessionId}Stored under ccb.joinAttempt:{sessionId}.
Caches the Join-attempt token (a short-lived HMAC-signed bearer) so that retries during a single page render resolve to the same anonymous Athlete identity. The storage key is the server-provided Session identifier; the QR bearer token is never embedded in the key.
ccb.consentHolds the visitor's per-purpose consent decision (analytics, diagnostics) so it persists across page loads. No Visitor identifier, no fingerprint, no tracking payload — only the per-purpose state, the policy version, the decision timestamp, and the surface that produced the decision.
ccb.consent.pendingFail-closed marker for an in-progress consent change. Holds the canonical structured PendingConsentMutation at schemaVersion 1 (kind, mutationId, consentVersion, requestedDecision, effectiveDecision, surface, requiresAccountSync, createdAt) so a half-applied change restores the conservative posture on the next mount rather than being lost. Carries no Visitor identifier. The canonical persistence status surface drives the visitor's recovery path; the marker does not auto-replay.
Browser storage that remembers a UI choice the visitor made (theme, language). The product continues to work without them; the visitor just loses the preference and re-picks on the next load. CCB does not gate these on consent because the preference belongs to the visitor in the first place.
ccb-themeHolds the visitor's light / dark / system theme choice so it persists across page loads. Removing the value falls back to the system preference; the product continues to work.
ccb-deck-langHolds the investor-deck language selection for the current tab. Removing the value falls back to English; the product continues to work.
CCB reports unhandled browser errors to Sentry so the team can fix bugs quickly. The reporter does not write any cookies or browser storage in the current configuration, and every event passes through a PII-stripping filter before it leaves the browser. The filter covers four surfaces: the request cookie jar, the top-level extra object, the top-level user object, and the top-level data object on each breadcrumb. On those surfaces, it removes the identifiers that pin an error to an individual User, Athlete, Session, or Facility, redacts emails and magic-link URLs from string values, and deletes auth-shaped cookie keys. Other event surfaces (tags, contexts, exception values, request headers and URL, nested extra or breadcrumb objects, breadcrumb messages) are not touched by the filter and should not be relied on to remove sensitive material. CCB never sets those fields with personal data.
PII filtering: CCB-owned beforeSend hook strips emails, magic-link URLs, auth-cookie values, and athleteId / sessionId / boxId / userId from the four surfaces it touches: top-level request.cookies, top-level event.extra, top-level event.user, and the top-level data object on each breadcrumb. Other event surfaces (tags, contexts, exception values, request headers / URL, nested objects, breadcrumb messages) are not covered — CCB never writes personal data there.
CCB does not use advertising or marketing trackers, and does not share any data with advertising networks. The two optional purposes CCB does offer — first-party product analytics and browser error reporting — are both consent-gated. The visitor can turn each one on or off independently at any time from the Your privacy choices panel below. A future change in posture (new third-party integration, new optional purpose) will require a consent boundary — see Changes to this page below.
The public CCB pages can send a single anonymous event per page view, CTA click, and outbound-link click to a first-party endpoint at POST /api/track. The endpoint is cookieless: no identifier, no persistent client ID, no session stitching, no fingerprint, no advertising profile is built from it. The wire shape accepts only name, path, slug, cluster, cta, href, and ts; any other field is dropped at the schema stage. Magic-link URLs, QR-join tokens, and email addresses that happen to appear in the wire fields or in the browser's Referer header are redacted to [redacted] before the line is written. The redactor is the same PII strip list used by the Sentry beforeSend filter.
The endpoint writes the redacted event to the application's standard log stream. It is not sent to a third-party analytics provider, and the Sentry error reporter is not invoked by the analytics path.
Analytics is opt-in. The tracker is inert until the visitor turns the “Analytics” switch ON in the Your privacy choices panel below. Until then the browser sends nothing to POST /api/track. Turning the switch back OFF removes the tracker without a page reload and suppresses further events for the rest of the session.
The full story of what CCB collects, why, and the rights you have over it is on the Privacy Policy.
The browser-side Sentry SDK is opt-in. The SDK is inert until the visitor turns the “Diagnostics” switch ON in the Your privacy choices panel below. Until then unhandled browser errors are not reported. Turning the switch back OFF tears the SDK down for the rest of the session. The same teardown runs whenever the diagnostics state transitions to unknown — for example after a consent-policy version bump, after clearing the consent record, or any reconciliation that returns unknown. The PII filter described in the error reporting section above is unchanged.
You can remove any of the above from your browser at any time. The trade-off: clearing the session cookie signs you out, clearing the anonymous Athlete cookie removes that browser's proof of join for any in-progress Session, and clearing the recovery queues drops any Work-Phase or Race Practice submission that the browser had not yet delivered to the server.
This page is updated whenever CCB introduces a new cookie or storage key, expands a storage purpose, or integrates an analytics, diagnostics, or marketing tool that requires consent. The current product has no third-party analytics or marketing integration. First-party analytics and browser diagnostics are consent-gated as described above.
Questions about CCB's storage choices can be sent to the team via the Contact link in the site footer.