Data processing terms for clubs
- Your club decides what it records about its players and members; Tagside stores and shows that data only to run Tagside for your club.
- We keep it secure, tell you about problems quickly, help you answer requests from players and parents, and delete it when you leave.
- You make sure you’re allowed to record it, tell players and parents, and only show names publicly with consent.
1. Who these terms are between
These terms are between the club using Tagside (“the club”) and Ionuț Zbarnea, a sole trader in the United Kingdom trading as Tagside (“Tagside”, “we”). The person who creates a club on Tagside, its owner, accepts them on the club’s behalf and confirms they have authority to do so. They form part of the agreement under which the club uses Tagside, and meet the requirements of Article 28 of the UK GDPR.
For the club’s data, the club is the controller and Tagside is its processor. For the club members’ own Tagside accounts, Tagside is the controller, as our privacy policy explains.
2. What we process
The subject matter, duration, nature and purpose of the processing, the types of personal data and the people concerned are set out in Annex 1.
Tagside also acts as controller for limited club-level service usage, such as daily activity, export outcomes and subscription-change counts, to understand and improve the service. These records contain no player details or match video; their scope and 90-day retention are explained in the privacy policy.
3. What Tagside does
- Instructions. We process the club’s data only on its documented instructions, which are these terms and the club’s use of Tagside (what its owner and coaches enter, change, share or delete), unless UK law requires otherwise; if so, we’ll tell the club first unless the law forbids it. If we think an instruction breaks data protection law, we’ll say so.
- Confidentiality. Only people who need access to run Tagside have it, and they are bound to keep the data confidential. Today that is Ionuț Zbarnea alone.
- Security. We keep appropriate technical and organisational measures in place, described in Annex 2, and keep them up to date.
- Sub-processors. The club authorises the sub-processors in Annex 3. We give each one data protection obligations no weaker than ours, and remain responsible for them. We’ll email club owners at least 30 days before adding or replacing one; if the club objects on reasonable data protection grounds and we can’t resolve it, the club may close its account and we’ll delete its data as in point 8.
- Requests from individuals. Club owners and coaches can view, correct and delete their club’s data in Tagside, and export matches as files. Where that isn’t enough to answer a request from a player, parent or member (to see, correct or delete their data, for example), we’ll help, and we’ll pass on any request we receive directly.
- Breaches. If we become aware of a personal data breach affecting the club’s data, we’ll tell the club owner without undue delay and in any case within 48 hours, with what we know (what happened, the data and people affected, likely consequences and what we’re doing), and keep them updated.
- Help with compliance. We’ll give the club reasonable help with its security, breach notification, data protection impact assessments and consultations with the relevant data protection authority, taking into account what we process and the information we have.
- At the end. When the club closes its account or stops using Tagside, the owner can first export its matches. We then delete the club’s data from the active service within 30 days, unless UK law requires us to keep it. Backup copies are used only for recovery and are removed as the relevant backup sets expire under the backup retention arrangements in Annex 2. Before a restored service returns to normal use, completed deletion requests are checked and applied again.
- Information and audits. We’ll make available the information needed to show we meet these terms, and answer the club’s reasonable written questions. Where that isn’t enough, we’ll allow and contribute to an audit by the club or an auditor it appoints, on reasonable notice, at the club’s cost, no more than once a year unless there has been a breach.
- Transfers outside the UK. We only transfer the club’s data outside the UK with the safeguards UK law requires (an adequacy regulation such as the UK–US data bridge, or the International Data Transfer Addendum).
4. What the club does
- Has a lawful basis for recording its players, members and matches, and tells the people concerned (or their parents) about it, for example in its own privacy notice, including that it uses Tagside.
- Records no more than it needs. A shirt number is enough for Tagside to work; names, positions and notes are optional.
- Turns on public player names only with the consent of the players concerned, or their parents for players under 18, and keeps the club page private if that isn’t in place.
- Invites only people who should see the club’s data, gives coach and admin access only to adults (18 or over), and removes people who leave. Account holders must be 13 or over.
- Has the rights it needs in the match videos it uses. Videos stay on the club’s devices and are never sent to Tagside.
- Tells us at [email protected] if it needs help with a request or a concern.
5. General
If these terms conflict with any other terms between the club and Tagside about personal data, these terms win. Nothing in them limits liability that the law does not allow to be limited. When we publish a new version, the club owner is asked to accept it in Tagside; until they do, the previous version continues to apply. These terms are governed by the law of England and Wales, and the courts of England and Wales have jurisdiction.
Annex 1: Details of the processing
| Subject matter and purpose | Providing Tagside to the club: storing its teams, players, seasons and matches, the events its coaches tag on match video, and the statistics worked out from them; keeping copies in step across its members’ devices; showing them to its members and, if the club chooses, on a public page; sending invites to people the club invites. |
|---|---|
| Nature | Storage, retrieval, organisation, synchronisation, display, transmission (invite emails), backup and deletion. |
| Duration | While the club uses Tagside, then until deletion as in section 3, point 8. |
| People concerned | The club’s players (who may be children), coaches and other members; people invited to the club; opposing teams’ players, usually by shirt number only. |
| Personal data | Members: name, email address, role. Invitees: email address, role. Players: shirt number and, if the club enters them, name and position, and links between records of the same person across teams; the club’s and teams’ names, colours and logos; match details (date, venue, notes, kits, who played and their numbers); tagged events (actions, video times, court locations, players involved) and statistics; video details (file name, size, length, fingerprint or public link), never the video. A coach-set playback link is also shown to viewers of that match, including public visitors when the owner shares its team; local file metadata remains private. |
| Special category data | None is required or asked for. Clubs should not enter health or other special category information in names or notes. |
Annex 2: Security measures
- Encryption in transit (HTTPS/TLS) for all traffic, behind Cloudflare’s network protection.
- Passwords stored only as salted hashes; optional Google sign-in; sign-in sessions expire after two weeks.
- Access control on every request by club and role (owner, coach, admin, player, supporter, public): only owners, coaches and admins can change data, only members can see private clubs, player names stay off public pages unless the club allows names and explicitly makes that player’s team public (an incidental opponent’s roster remains private), and video details are never public. These rules have automated tests.
- Rate limiting against password guessing and abuse.
- Data minimisation by design: match videos never leave the club’s devices; shirt numbers are enough for every feature.
- Backups. Nightly application backups and separate release snapshots are kept for 7 days. Zume’s server-drive backups are configured for 2 weeks, with a minimum of 3 backups retained. Server-drive backups can contain older application backups or release snapshots, keeping deleted data in backup copies for longer than 2 weeks. The minimum-three-backups rule can also extend retention beyond the two-week setting. Backup copies are removed as the relevant backup sets expire.
- Recovery. Backup copies are used only for recovery. Before a restored service returns to normal use, completed deletion requests are checked and applied again.
- Server and application logs kept briefly (about 5 weeks and 7 days); the feedback form stores no IP addresses.
- Only Tagside administers the server and its data.
- Signing out of Tagside removes its member and public club copies from that browser. Connected public pages remove revoked rows and names on their next successful refresh.
Annex 3: Sub-processors
| Sub-processor | Purpose | Location |
|---|---|---|
| Zume (Alpha Internet Limited) | Hosts the virtual server storing and serving the club’s data, and provides server-drive backups | VPS: United Kingdom. Provider backup storage location has not been verified. |
| Cloudflare, Inc. | Website delivery and protection (data passes through its network) | Global, including the US |
| Resend | Sending invite emails | United States |