Legal

Cookies And Browser Storage

Last updated: 21 May 2026

The public CatchLab marketing website does not intentionally set CatchLab cookies and does not use advertising or behavioural tracking cookies.

Portal And Admin Authentication

The CatchLab portal and admin apps currently use Supabase authentication through @supabase/ssr. That setup reads and sets authentication cookies for signed-in users so server-side routes can identify the current user and enforce club access. These are strictly necessary for the logged-in application, not marketing or analytics cookies.

Browser Storage

CatchLab uses localStorage and sessionStorage for product settings and temporary UI state, including examples such as theme, cached current-user profile, dashboard filters, chart preferences, smoothing settings, pushed-to-Intervals markers, sculling sport preferences, and admin UI settings.

Website Technologies

• The public website currently loads Google Fonts. Google may receive technical request information such as IP address, browser, and page request metadata.
• If Cloudflare protection or email-obfuscation is active on the public website, Cloudflare may process technical request metadata to deliver and protect the site.
• Chart.js is loaded on the demo page from jsDelivr. This is used to render the interactive demo.
• The demo page embeds a Tally form for demo requests. Tally may use its own cookies or browser storage when the form is loaded or submitted.

Analytics

CatchLab does not currently intend to use analytics or advertising cookies. If analytics are added later, this page will be updated and consent will be requested where required.

Managing Site Data

You can clear cookies and site data through your browser settings. Clearing logged-in app storage may sign you out or reset product preferences.