Version 3.0 · Effective from 1 July 2026
Names, contact details, scores, equipment loans, meeting records and finance
entries the club chooses to enter. Nothing is collected about members beyond
what the club itself records.
Junior records require a recorded parental or guardian consent before any
data is stored. Consent can be withdrawn at any time by contacting the club.
Club data is visible to the club's own admins and members according to the
roles the club assigns. BowHub staff access data only to provide support, at
the club's request.
Data is kept for the life of the subscription, plus 12 months after
cancellation, after which it is deleted unless the club exports it sooner.
Members can ask their club to correct or erase their data. The club is the
data controller; BowHub is the data processor.
We use Sentry to capture crashes and performance data. For logged-in users we attach your account ID and club ID to error reports so support can reproduce and fix issues faster; no names, scores, or other club data are attached.
Sentry Session Replay records a visual replay of what happened in your browser immediately before an error, to help us diagnose it: 10% of sessions are recorded at random in production, and 100% of sessions that hit an error are recorded regardless of the random sample. Replays are not recorded outside production.
Error and performance reports normally include the page you were on, your IP address, and your browser's request headers. We strip the auth_token session cookie and any Authorization header before a report leaves your browser, so your session token is never sent to Sentry. Your IP address and the rest of your request headers are not stripped and are retained by Sentry under its own data retention policy.
Pages load fonts from Google Fonts. Loading a font makes your browser send a request directly to Google, which — like any web request — includes your IP address. We don't control what Google does with it; see Google's own privacy policy for details.