Privacy Policy

Information used to provide FencingScores

We process the information needed to run and record a competition. This can include participant, organizer, and referee names; competition and event settings; team rosters and substitutions; scores; bout results; and the scoring actions recorded for a bout.

An official scoring record can include cards and their stated reasons, medical-time decisions and injury codes entered by an official, video-review outcomes, corrections, and Directoire Technique decisions. Organizers and officials should enter only the detail needed for the competition record.

If you create a FencingScores profile, we process the display name and preferred weapon you provide, together with the official results you choose to verify for that profile.

Accounts and access

FencingScores supports sign-in with Apple and Google on iOS and on the web through Supabase. We process the account identity supplied by that provider, including an email address when the provider supplies one, to keep a signed-in profile separate from competition access.

Competition rooms and scoring roles use access credentials so participants, referees, and organizers can reach the appropriate competition view. The web app keeps participant access in a secure, HTTP-only browser cookie.

Information kept on your device

The app and web experience can keep working data on your device. The iOS app can retain an unfinished individual or team-relay scoring chronology so an official can recover work after leaving the scoring screen. The web app stores organizer drafts and unsent referee submissions in browser IndexedDB, a recent submission acknowledgement in local storage, and a small public-shell cache for offline use.

An unfinished or unsent referee record can include scores, official actions, and its strip access credential. The app keeps the working record on this device until the server accepts it; records awaiting an organizer decision remain available for recovery. Clearing FencingScores site data in your browser removes browser-stored working data.

How information is used and shared

• To create, run, display, and correct competitions and bout results.
• To provide the role-based participant, referee, organizer, and private-profile experiences.
• To authenticate a signed-in user and protect access to a competition or scoring role.
• To provide service infrastructure through Supabase and sign-in through Apple or Google when you choose those providers.
• To show competition information to the people who are given access to that competition, such as its organizer, participants, and referees.

Camera and sharing

The iOS app asks for camera access only to scan competition QR codes. FencingScores does not use that permission to create a camera-photo library. When you share a result graphic, the app sends it to the sharing destination you choose through your device's system share controls.

Analytics and advertising

The FencingScores web experience uses Vercel Web Analytics through the @vercel/analytics package to measure aggregate site traffic and improve the web experience. The web app currently sends automatic page-view events; a data point may include the event time, URL, referrer, filtered query parameters, approximate location, device type, operating system, browser, and analytics script version. FencingScores drops events for referee, strip, competition-room, and private-invitation access paths before they are sent, so scoring credentials, room codes, and private claim URLs are not included in analytics.

Vercel describes Web Analytics as anonymous, cookie-free measurement that does not use cross-site personal identifiers; its visitor session hash is discarded after 24 hours. Analytics data is retained for the reporting period available for the Vercel project plan. We do not sell this analytics data or use it for advertising. Where applicable law gives you a right to object or opt out, contact support@fencingscores.io and we will help with that request.

The iOS app does not use this web analytics package. FencingScores does not include advertising SDKs.

Account deletion, retention, and questions

We use access controls designed to limit competition and profile information to the relevant role or signed-in user. Keep room links and scoring credentials private, because someone with a valid credential may be able to access the associated competition role.

You can delete a signed-in account in the iOS app from Account > Delete Account. The deletion flow asks you to authenticate again with the sign-in provider before it proceeds. If you cannot sign in, contact support@fencingscores.io for help initiating the request.

Deleting an account removes its profile and account access. Official competition records can remain so that an organizer's published results and audit history stay internally consistent; when retained for that purpose, the deleted account's actor identity is anonymized. Browser-stored drafts and pending submissions are removed by clearing FencingScores site data in that browser.