Transparency alternatives to Kitman Labs
Other Sports team management vendors we measure, sorted by how much we found at them and not at Kitman Labs. This is a comparison of disclosure, not of features or fitness.
12 shown of 39 that differ from Kitman Labs on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kitman Labs has 8 gaps in what we could measure: Data processing agreement, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at Kitman Labs” is the one that closes them.
| Vendor | Score | Found there, not found at Kitman Labs | Found at Kitman Labs, not found there | |
|---|---|---|---|---|
| SportsEnginesportsengine.comSee also Transparency alternatives to SportsEngine | 52/100 | 4 Data processing agreement, Status page with history, Public pricing, +1 | 2 Subprocessor list, Certifications named | Compare |
| TeamSnapteamsnap.comSee also Transparency alternatives to TeamSnap | 43/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Spondspond.comSee also Transparency alternatives to Spond | 39/100 | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Pitcheropitchero.comSee also Transparency alternatives to Pitchero | 35/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 3 Certifications named, Notice before subprocessors change, Named privacy contact | Compare |
| TeamLinktteamlinkt.comSee also Transparency alternatives to TeamLinkt | 35/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Trackmantrackman.comSee also Transparency alternatives to Trackman | 30/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| UDiscudisc.comSee also Transparency alternatives to UDisc | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | Compare |
| Hudlhudl.comSee also Transparency alternatives to Hudl | 50/100 | 2 Status page with history, HTTPS enforced with HSTS | nothing | Compare |
| Sportradarsportradar.comSee also Transparency alternatives to Sportradar | 30/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Named privacy contact | Compare |
| Kinexonkinexon.comSee also Transparency alternatives to Kinexon | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Clubforceclubforce.comSee also Transparency alternatives to Clubforce | 22/100 | 2 Public pricing, HTTPS enforced with HSTS | 3 Subprocessor list, Certifications named, Notice before subprocessors change | Compare |
| Playermakerplayermaker.comSee also Transparency alternatives to Playermaker | 22/100 | 2 Data location stated, Public pricing | 4 Subprocessor list, Certifications named, Notice before subprocessors change, +1 | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.