Data storage & security

Where CompTeam stores branch and athlete data, how daily backups work, and which controls protect access to files and consent records.

1. 1

   Where your data is stored

   CompTeam stores its primary application data in Supabase.

   The current production database is hosted in West EU (Ireland). This covers the operational data branches need to run on CompTeam, including athlete profiles, memberships, attendance, billing records, consent records, and branch settings.

   CompTeam uses this hosted database as the system of record for day-to-day branch operations.

2. 2

   Backups and recovery

   Daily backups are enabled for the production database.

   If data corruption occurs, CompTeam can restore the database to a daily snapshot as a recovery measure.

   This is intended for serious recovery scenarios such as corruption or service-impacting data issues. It is not a per-record undo feature inside the normal app workflow.

3. 3

   How CompTeam limits access

   CompTeam applies authenticated access controls inside the app so users only see the data they are allowed to manage.

   In practice, this includes:

   • Branch-scoped access so one club's staff does not manage another club's records
   • Role-based permissions for athletes, coaches, branch admins, and organisation admins
   • Access to operational screens only after sign-in

   This keeps day-to-day data access tied to the branch and role the user is acting under.

4. 4

   Files and audit records

   CompTeam also applies extra controls around uploaded files and compliance records.

   • Uploaded files such as athlete photos, medical documents, pending-registration documents, and membership agreements are delivered through time-limited signed links, rather than permanent public file URLs
   • Consent-related records are stored with timestamps and audit history, so branches can show when key consent actions were recorded

   For AI-specific handling of athlete data, see the separate AI & data privacy guide.