What sovereignty actually means here
Data sovereignty is a simple idea wrapped in an intimidating word. It means the data your organization produces stays under your control: you decide where it is stored, who can see it, what is done with it, and when it leaves. Nothing about that requires you to run everything yourself. It requires that the choice remains yours rather than a vendor's.
For a sports team the phrase carries a second, more literal meaning. A lot of your data is generated in one physical place, on a field or a court, at a known time, under conditions nobody else can reproduce. That is not ordinary business data. It is a record of how your athletes actually perform, and it cannot be regenerated once it is gone or once somebody else controls the terms of access.
What a team actually produces
It is worth being concrete, because "our data" tends to mean whatever a particular department is looking at that week. A single season typically generates:
- Positional and tracking data. Optical or wearable tracking, often at high frequency, for every player in every session and game.
- Video. Game footage, training footage, tactical angles, and whatever the analysts have cut and tagged from it. Usually the largest volume by far.
- Load and availability. Training load, session RPE, sleep and readiness inputs, rehabilitation progress.
- Medical records. Injury history, screening, imaging, treatment notes.
- Scouting and recruitment. Reports on your own players and on targets, which is often the most commercially sensitive material in the building.
- Venue and operations. Ticketing, access, crowd flow, and increasingly the network and sensor telemetry from the stadium itself.
Each of those tends to arrive with its own platform, its own login, and its own contract. That is how a team ends up with a dozen partial pictures and no complete one. The team data inventory breaks each category down: who uses it, and what each one demands of you.
Where it usually ends up
The default arrangement in most of the industry is that a vendor collects the data, stores it in their cloud, and gives you a dashboard to look at it through. That is convenient, and for a while it is genuinely the fastest way to get value. It also quietly creates three problems.
Access is mediated
You see what the interface shows you. Asking a question the dashboard was not designed for becomes a support ticket, a feature request, or a professional services quote. The data exists, and you cannot get at it.
Portability is theoretical
Most contracts say you can export your data. Fewer specify the format, the granularity, or the timescale. An export of aggregated summaries is not the same asset as the raw tracking feed, and by the time you discover the difference you are usually mid-migration.
Leverage shifts
This is the one that costs real money. If several years of your performance history sits in a vendor's system in a format only they write, your negotiating position at renewal is weak no matter how the contract reads. The switching cost is the leverage, and it grows every season.
A useful test: if you had to change every data supplier at the end of this season, how much of your history would you still have in a form you could actually use? If the honest answer is uncomfortable, that is a sovereignty problem rather than a technology problem.
Why it is not only a commercial question
Player data is personal data. Performance and medical information relates to identifiable individuals, and in most jurisdictions medical information attracts stricter protection than ordinary business records. That places obligations on the team as the organization the athletes have a relationship with, regardless of which supplier happens to be holding the files.
Two practical consequences follow. You need to be able to say precisely where an athlete's data is stored and who has access to it, which is difficult when the answer is spread across several vendors' infrastructure in several countries. And you need to be able to act on a request about that data, including deleting it, which you cannot fully honor if you do not control the systems it lives in.
Athletes are also increasingly aware of this. A player who asks what happens to their data, and what happens to it when they transfer, is asking a reasonable question. Being able to answer it clearly is becoming part of how a team presents itself.
What sovereignty looks like in practice
None of this argues for refusing to work with specialists. It argues for a particular shape of arrangement, where the team holds the primary copy and suppliers work against it, rather than the reverse.
- The primary copy sits where you control it. On hardware at your ground, in your own racks, or in cloud infrastructure held under your own account. The distinction that matters is control, not the building.
- Open or documented formats. If the raw data is written in a format you can read without the original vendor's software, you can always leave.
- Encryption and real access control. Encrypted in transit and at rest, with access scoped to the people who need it rather than everyone with a login.
- An audit trail. A record of who accessed what and when. This is what turns a claim about data handling into something you can evidence.
- Export as a routine operation. Not a project. If getting your own data out requires a support ticket, you do not really have it.
- Infrastructure that survives game day. Whatever holds the data has to work under the load, heat and network conditions of a live game, not just in a quiet office.
Questions worth asking a supplier
Most of the useful diligence here fits on one page. Before signing, ask:
- Where is the primary copy of our data physically stored, and under whose account?
- Can we hold a complete copy ourselves, continuously rather than on request?
- What exactly can we export: raw data, or processed summaries? In what format, and at what granularity?
- How long does a full export take, and has it been done for another client?
- Who at your organization can access our data, and is that access logged?
- Is our data used to train models or build products sold to anyone else, including our competitors?
- What happens to it if we do not renew, and how long is it retained afterwards?
- If you are acquired or cease trading, what is the mechanism by which we retain access?
The answers matter less than the willingness to answer plainly. A supplier who treats these as reasonable questions is usually a supplier worth working with. Each question is expanded on the supplier questions page, with what a good answer sounds like.
How we approach it
We build the arrangement described above. The primary copy of your data stays on hardware you control, encrypted and access-controlled, with a clear record of who touched what. We work alongside your analysts and technical staff to turn it into the few measures that actually change how the team trains, recruits and plays, and we design the compute, storage and networking underneath for the stadium and the practice facility rather than the office.
The point is not that you should distrust your suppliers. It is that owning your own history should not depend on trusting anyone.