Tagside

Privacy policy

Version 2026-10-28 · last updated 28 October 2026

In short
  • Your club’s teams, players, matches and stats are kept on Tagside’s server so everyone in the club sees the same. Match videos never leave your device.
  • For players’ and matches’ data, your club is in charge and Tagside looks after it for the club (see our data processing terms).
  • No adverts, no third-party analytics, no selling data. We use limited club-level service usage and optional visitor statistics to improve Tagside. Optional statistics stay off until you choose Allow statistics. We use a few services to run Tagside (hosting, network security, email), listed below.
  • Ask us anything, or to see or delete your data: [email protected].

1. Who we are

Tagside (tagside.app) is run by Ionuț Zbarnea, a sole trader in the United Kingdom (“Tagside”, “we”, “us”). For anything about your personal information, email [email protected].

2. Two kinds of data, two different roles

Your account, our website and the emails we send. We decide how this is used, so we are the controller under UK data protection law (the UK GDPR and the Data Protection Act 2018).

Your club’s data (its members, teams, players, matches, tags and stats). The club decides what goes in and who sees it, so the club is the controller and we are its processor: we store and show it only to provide Tagside to the club, under our data processing terms, which every club owner accepts. If you are a player (or a player’s parent) with a question about what a club records about you, ask the club first; you can also write to us and we will pass it on and help the club answer.

3. What we hold

Your account

Paying for Premium

Club data (held for the club)

On public club pages, Tagside reads as a guest even if you are signed in. Player names are shown only for the teams the owner explicitly makes public and only when public names are enabled. Visitors receive the chosen display name, shirt number or position, and the details needed to show that player’s public stats. Stored full names, separate given names and surnames, and links identifying the same person across teams stay private to club members. Choose a first name or nickname as the display name if you do not want a surname shown. An opponent appearing in a public match does not make its player names public. Public copies are refreshed when connected, and rows and names that are no longer public are removed on the next successful refresh. Local video filenames, sizes and file fingerprints stay private. When a coach sets a shared video link, it opens automatically for people who can view that match, including visitors to a public match page. The browser streams from the original host, which receives the visitor’s IP address and usual request information. Removing the shared link or making the match private removes it from connected public copies on their next successful refresh. Choosing a local MP4 for overlay export does not remove the shared link.

On your device only

When you use the website

Service usage

While a verified member uses a club online, Tagside records the club’s identifier and the UTC day it was opened. For video exports, we record the club, day, whether it is highlights or a whole game, a random attempt reference, and whether rendering started, completed, failed or was cancelled. We also count subscription starts, endings and changes to scheduled cancellation from Stripe’s updates. Reports are available only to authorised Tagside service administrators.

These records do not identify which member used the club, and contain no player details, video or frames, filenames, page history or error messages. Demo visitors, public visitors and offline-only sessions are not included in these usage counters. These club-level counters do not use third-party analytics, analytics cookies or visitor tracking identifiers. Optional visitor statistics are separate and described below. Reporting is best effort, so some activity or outcomes may not be received.

Optional visitor statistics

Only after you choose Allow statistics, we collect fixed categories about pages and features used on the website, demo, public club pages and member app. These include opening Stats, trying the demo, starting signup, creating an account or team, tagging, opening the highlights editor, export outcomes, and broad failure categories. We do not collect typed form contents, search terms, player or club names, match identifiers, URLs, files, video, audio, screen recordings or raw error messages in these statistics.

Your browser creates a random visit reference after permission. A new visit starts after 30 minutes without a recorded action, on a new UTC day, after you clear the visit data or close the tab. The server stores a hash of that reference, the UTC day, the consent wording version and first reported consent time, broad device/browser/referral categories and a set of actions reached. Referral categories such as search, social or email are calculated in the browser; full referring addresses and campaign text are not sent. There is no persistent identifier connecting different visits or devices, and no third-party analytics service. A visit can include several pages; visits are not unique people.

Only authorised service administrators can see the aggregate reports. We do not expose individual visit histories through the app. Detected automated traffic, super-admin activity and marked testing clubs are excluded where identifiable. Statistics are best effort; offline or blocked reports can be missed.

You can refuse or withdraw permission through Usage statistics in the footer on the main pages, or change your statistics choice here. The app works the same if you refuse. We respect browser Do Not Track and Global Privacy Control signals. Refusing stops new collection and removes the current visit reference from this tab; already collected data is kept only within the retention period below. Your choice is stored in this browser until you change or clear it; Allow expires after one year or a material consent-version change. The optional visit reference and the deduplication categories for this visit live in tab storage.

Feedback

If you send feedback: your message, the reply email address if you give one, a screenshot if you choose to attach one (you see it before sending, and it may show player names), the app version and your browser’s description.

4. Why we use it, and our lawful basis

What forDataLawful basis
Running your account and the service you signed up for, including sign-in, plans, clubs and syncingAccount dataContract: we need it to provide Tagside to you
Selling Premium and keeping the club’s plan up to dateStripe references, subscription state, the owner’s email (given to Stripe at checkout)Contract
Storing and showing your club’s data to its members (and to the public if the club chooses)Club dataWe act for the club, on its instructions; the club relies on its own lawful basis (usually legitimate interests in running its teams)
Emails you need: confirming your address, password resets, club invitesName, email; for invites, the invited address and the club’s nameContract (your account); for invites, on the club’s behalf
Keeping Tagside secure and working: logs, backups, rate limitsLogs, all stored dataLegitimate interests: running a safe, reliable service
Optional website, demo and app statisticsRandom visit reference (hashed on the server), broad device/browser/referral categories and fixed action flagsConsent; you can withdraw through Usage statistics
Understanding club adoption and export reliability, and improving TagsideDaily club activity, export outcomes and subscription-change counts; aggregate reports from existing account and match recordsLegitimate interests: understanding and improving the service
Answering and acting on feedbackFeedbackLegitimate interests: improving Tagside and replying to you

5. Children

Youth clubs record children: their shirt numbers, sometimes their names, and what they do in matches. Clubs must only record what they’re entitled to, tell players and parents about it, and get consent before showing names on a public page. To help, Tagside asks for as little as possible (a shirt number is enough), keeps names off public pages unless the club turns them on, and never stores video.

You must be 13 or over to have a Tagside account. Club owners, coaches and admins must be 18 or over. Younger players can be followed through a parent’s supporter account.

6. Who else handles it

We don’t sell or share personal information for anyone’s marketing. These services help us run Tagside and only act on our instructions:

ServiceWhat it doesWhere
Zume (Alpha Internet Limited)Hosts the virtual server that stores accounts and club data, and provides server-drive backupsVPS: United Kingdom. Provider backup storage location has not been verified.
CloudflareDelivers the website and protects it from attacks; sees requests (including IP addresses) as they passGlobal network, including the US
ResendSends our emails (confirmations, password resets, invites, copies of feedback)United States
GoogleSign in with Google, only if you choose itGlobal, including the US
Stripe (Link)Sells Premium as merchant of record: takes payment, handles tax, receipts, refunds and payment support. Stripe is responsible for the payment data it collects.Ireland, the US and elsewhere

Club members see their club’s data according to their role. If a club makes its page public, anyone can see its teams, matches and stats (with names only if the club allows it). Public clubs and the teams the owner explicitly shares can also be found by name through the homepage search. We would disclose information to authorities only where the law requires it.

7. Outside the UK

Cloudflare, Resend, Google and Stripe may handle some data in the United States or elsewhere. When they do, it’s protected by safeguards UK law recognises: the UK–US data bridge for certified companies, or the UK International Data Transfer Addendum to standard contractual clauses.

8. How long we keep it

DataKept
Your accountUntil you delete it (Account → Delete my account) or ask us to. We may delete accounts unused for over 3 years, after emailing first.
Club dataFor as long as the club uses Tagside. When its owner closes the club in Tagside it is deleted straight away; if they ask us instead, within 30 days.
BackupsNightly application backups and separate release snapshots: 7 days. Zume server-drive backups: configured for 2 weeks, with a minimum of 3 backups retained. See backup copies and deletion below.
Admin change historyUp to 12 months; entries for a closed club are deleted with the club, with backup copies following the backup retention arrangements below.
Admin authenticator credentialsUntil the administrator removes the authenticator or the admin account is deleted, with backup copies following the backup retention arrangements below. Unconfirmed setup expires after 10 minutes and is cleared by an hourly cleanup. Failed-attempt limits expire after 3 minutes; their counters may remain with an enabled credential until the next successful verification or removal.
Server request logsAbout 5 weeks (web server) and 7 days (application logs).
Service usage records90 days, or until the club is closed if sooner. Backup copies follow the backup retention arrangements below.
Optional visitor statistics90 UTC days. Backup copies follow the backup retention arrangements below.
Feedback12 months, then deleted.
Stripe references on a clubUntil the club is closed. Stripe keeps its payment records for as long as the law requires it to.
Copies on your deviceUntil you sign out, or clear your browser’s data. Videos and saved exports are yours to keep or delete.

Backup copies and deletion

The periods above describe data in the active service. Backup copies are used only for recovery and are removed as the relevant backup sets expire.

A server-drive backup can contain older application backups or release snapshots. This can keep deleted data in backup copies for longer than 2 weeks. The provider’s minimum-three-backups rule can also extend retention beyond its two-week setting.

Before a restored service returns to normal use, completed deletion requests are checked and applied again.

9. Your rights

You can ask to see the personal information we hold about you, to correct it, to delete it, to restrict or object to how we use it, and to have it in a portable form. Email [email protected]; we reply within one month. For data a club holds about you, we’ll help the club answer.

You can delete your account yourself in Tagside (Account → Delete my account); a club owner hands the club over or closes it first. You can leave a club at any time from Settings, club owners can remove members, and owners can close their club, which deletes its data for everyone. A parent or guardian can make these requests for a child.

If you’re unhappy with how we’ve handled your information, please tell us. You also have the right to complain to the relevant data protection authority.

10. Cookies and browser storage

Tagside uses no advertising or analytics cookies. It keeps the things listed under “On your device only” in your browser’s storage because the app can’t work without them. Cloudflare may set a short-lived security cookie to tell people from bots. Those operational and security items are necessary to provide the service. Optional usage statistics use separate tab storage only after you give permission. The saved statistics choice is used to respect your preference; you can change it through Usage statistics in the footer.

11. Security

Everything travels over encrypted connections (HTTPS). Passwords are hashed. Every request to the server is checked against your club and role, and these checks are tested automatically. The server is backed up every night. Videos stay on your device, so they can’t leak from ours. If something goes wrong that puts your information at risk, we’ll tell the affected clubs and people. Where required by law, we’ll also notify the relevant data protection authority.

12. Changes

If we change this policy we’ll update the date above, and tell account holders by email about anything significant.