Privacy

Privacy policy

What we know about you and your devices, why we need it, who we share it with and how long we keep it. No small print and no advertising.

Effective from 29 September 2026

1. Who processes the data and how to reach us

The controller of personal data is the operator of the Sports Analysis service, based in Prague ("we"). We run the Sports Analysis software, the Sports Analysis app for Android, the sports-analysis.cz website and the secure portal on it.

For anything about personal data, including exercising your rights, write to licence@sports-analysis.cz.

2. When we are the controller and when we act for a club

As the controller we process data about customers and their contact persons, portal users, the devices the software and the app run on, and website visitors - everything we need to provide and protect licences, to give support and to run the website and the portal.

Clubs and organisations using the software also put their own data into it: rosters with player names and numbers, game files with marks and notes, game video and recordings, and personal player access to their own actions. For this data the club is the controller. We process it only as a processor, on the club's instructions and only to provide the service to the club. If you are a player or a staff member and want to raise something about this data, please contact your club first; we will help it respond.

3. What data we process

Visiting the website

The website uses no analytics, advertising or tracking tools and loads no scripts or fonts from third-party servers. The web server keeps technical records of requests (IP address, time, requested address, browser identification) used to run the service and to deal with faults and attacks.

Licence request from the website

Name, club or organisation, e-mail, phone (optional), your message, the form language, the time it was sent, IP address and browser identification. While we handle the request, our replies, its status and an internal note are added to it.

Account in the secure portal

Username, full name, e-mail, role and organisation, password (only as an irreversible hash, never readable), the two-factor authentication secret if you turn it on, and the dates the account was created and last signed in. What you create in the portal is stored with the account too: improvement suggestions and votes, playlists, drawings and mark edits in game reviews, and the game folder settings.

The software on your computer: licence and copy protection

On first registration (including the trial), on licence activation and on the regular licence check the software sends to the server:

  • a device identifier (HW ID) - a 32-character hash derived from the operating system's machine identifier,
  • the computer name and the name of the signed-in operating system user (with the domain for a domain account),
  • the software and operating system version and whether the software runs in a virtual machine,
  • a hardware description: maker, model and serial number of the computer, device type (for example laptop), processor, number of cores and threads, architecture, memory size, graphics card and disks (type, interface, size and model; we do not collect disk serial numbers).

The server adds the public IP address the software connected from, the time of the last contact and the licence data: licence key, organisation and licence holder label, device label, activations and deactivations, moves of the licence to another computer and suspensions (licence journal and operational records). Games, marks and video are not sent for the licence.

Your club's managers see the device name, the system and a shortened HW ID for the club's licences in the portal. The IP address, the system user name and the hardware description with the serial number are visible only to our administration.

Android app

When pairing and on regular contact the app sends the device name (the phone model by default), the platform, a random identifier the app creates on first start (not derived from the hardware), and a hardware description: maker, model, phone or tablet, processor, number of cores, memory, system version and storage. The app neither reads nor sends the phone's serial number. The server stores the pairing status, the link to a computer and the time of the last contact.

Live sessions and action sets

When you start a live session from the software or the app, the server stores the game title, team names, the stream address, the action set, rosters if you attach them (player names and numbers), and the individual marks (action, time, team, player numbers, note). A club's action sets are stored on the server so that all the club's devices have them.

Support, diagnostics and suggestions

Messages you write to support from the portal, the software or the app, and attachments you choose to add (error log, screenshot of the software window, image, game file or diagnostics; at most 20 MB per attachment).

The software puts the diagnostics together when you click and sends it only after a second, separate click; it never sends itself. It contains the software version and installation folder, the operating system, the computer name, whether it is a virtual machine, processor and memory, system and software language, monitors, licence status (edition, organisation, validity, shortened HW ID; the licence key and access token are not included in full), player status (the open file or address without credentials), ffmpeg and the names of capture devices, free disk space and the configured folders (a path may contain the user name), server reachability, crash records and the last 300 lines of the error log. Diagnostics from the Android app contain the device model, system version, permission status, cameras, network status and a log extract.

For improvement suggestions we store the text and category, the name of the person who submitted it and the software version.

Game reviews, rosters and player access (for the club)

In the portal a club's coaches and analysts can browse the club's games, marks and video, draw on them, build playlists and edit marks. This involves game files (marks, player names and numbers, notes), game video and recordings in which players can be seen, and the edits you make in the portal. The files are stored on the club's storage or on storage we run for the club. Before the portal writes to a game file, it saves the original version on the server as a backup.

A club can give players personal access to their own actions. For that we store the player's name, category, the assigned actions and folders, the password (only as a hash) and the last sign-in time. Every attempt to sign in through a player link records the time, the result, the IP address, a short browser and system description (for example "Chrome 127", "Android") and a random browser identifier from a cookie; they show when one personal access is used by several people. We do not store the full browser identification, and only our administration sees these records. Players may include minors; their access is set up and managed by the club.

Sign-in records and abuse protection

For every attempt to sign in to the portal, successful or not, we record the time, the result, the IP address and a short browser and system description. Only our administration sees these records. To protect against password guessing and form flooding the server also keeps, briefly and for at most an hour, a count of attempts per IP address in memory; this is not stored anywhere.

Private power-play analysis section

Only invited people have access to this part of the website. When you ask for access, we store the IP address, name, contact, your message and browser identification. An approved IP address is kept with the date until which access is valid and the time of the last visit.

Invoicing

If you buy a licence, we process billing data (company or personal name, address, company ID and VAT number if you have them) and payment records.

4. Why we do it and on what legal basis

  • Providing the licence and the service - software, updates, portal, game reviews, live sessions, the Android app and support: performance of a contract (Art. 6(1)(b) GDPR). Handling a licence request is a step taken at your request before entering into a contract (same article).
  • Protecting the licence against copying and misuse - HW ID, computer name, system user name, IP address, hardware description and virtual machine detection: performance of the contract (a licence covers a set number of devices) and our legitimate interest in a licence not running on more devices than are paid for, and in knowing whose device it is (Art. 6(1)(f) GDPR).
  • Support - the hardware description and diagnostics tell us what is happening on a device and whether it can handle, for example, high-resolution recording: performance of the contract and legitimate interest.
  • Security of accounts, the portal and player access (sign-in records, attempt limits, web server records): legitimate interest in protecting accounts and data against misuse.
  • Invoicing and accounting: compliance with a legal obligation (Art. 6(1)(c) GDPR).
  • Consent: no processing relies on consent today. You send diagnostics and attachments of your own accord, with a separate click, as part of support. Should we ever need consent, we will ask for it separately and you will be able to withdraw it at any time.

Automatic licence suspension. When one licence reports from an unusually high number of different devices within a short time, the server may suspend it on its own; an activation beyond the permitted number of devices is refused. We carry out no other automated decision-making and no profiling. If you disagree with a suspension, write to us and a person will review it.

5. Who we share data with

  • Nobody for marketing. We do not sell data. It is stored on a server we manage; the website, the database and outgoing mail all run on it.
  • E-mail. Licence keys, password resets and replies to requests are sent from our own mail domain; delivery is handled by your e-mail provider. Notifications about new licence requests and access requests for the private section, and an overview of expiring licences, go by e-mail to the administrator's mailbox.
  • Telegram. Our administrators get notified through the Telegram service about a new licence request (club, name, e-mail, phone, language, message and time) and about access requests for the private section (IP address, name, contact). Its operator is based outside the European Union.
  • AI assistant. When an administrator uses the Claude assistant from Anthropic while handling a support request, it receives the text of the messages in that thread, the organisation name and the software version (not the content of attachments). The assistant only drafts text; a person sends the reply. Anthropic is based in the USA.
  • Transfers outside the EU. For Telegram and the Claude assistant the transfer relies on the Chapter V GDPR safeguards the providers offer: standard contractual clauses approved by the European Commission or, where applicable, the EU-U.S. Data Privacy Framework.
  • Your club. A club's managers see the licences, devices and live sessions of their club in the portal (see above for what they see about devices).
  • Authorities - only where the law requires it.

6. How long we keep data

  • Portal sign-in records: 90 days, then they are deleted by the regular clean-up.
  • Player link sign-in records: 90 days, then they delete themselves; our administration can delete them sooner.
  • Backups of game files taken before the portal writes to them: 90 days.
  • Attempt counts in the server's memory: at most an hour.
  • Licence and device data, portal accounts, live sessions, support and suggestions: for as long as the licence or the account lasts, and after that only as long as strictly necessary to settle any claims and to protect the licence against misuse.
  • Licence requests: while the licence is being discussed and for any cooperation that follows. A request can be irreversibly deleted together with the personal data; we will do so on request.
  • Data we process for a club: for as long as the club decides, at most until our cooperation with the club ends.
  • Billing data: for the period required by accounting and tax law.
  • Web server records: as long as strictly necessary to run the service and to deal with security incidents.

7. Cookies and browser storage

The website uses only cookies strictly necessary for it to work, which do not require consent. We use no analytics, advertising or tracking cookies, which is why we do not ask you about them.

  • session - portal sign-in, protection of forms against forgery, and a timing check that keeps robots away from the licence request form. Lasts until the browser is closed.
  • remember_token - only when you tick the "stay signed in" box at sign-in; keeps you signed in for 14 days.
  • sa_hz - a random browser identifier for player links (sent only to /hrac addresses). It is created only when someone tries to sign in; lasts 400 days.
  • sa_pp - the entry ticket to the private power-play analysis section; lasts 180 days.

In the portal the browser also remembers the layout of some screens (panel widths, expanded sections) in its local storage. This is not sent to the server.

8. How we protect data

Connections to the website, from the software and from the app are encrypted (HTTPS). Passwords are stored only as an irreversible hash and you can turn on two-factor authentication for your account. Only our administrators have access to the administration. IP addresses, system user names, device serial numbers and sign-in records are visible only to the administration, not to other portal users.

9. Your rights

For data where we are the controller you have the right:

  • of access - to find out what data about you we process and to get a copy,
  • to rectification of inaccurate data,
  • to erasure where the data is no longer needed or the reason for processing it no longer applies,
  • to restriction of processing, for example while we deal with your objection,
  • to object to processing based on legitimate interest,
  • to data portability - to get the data you gave us in a machine-readable form,
  • to lodge a complaint with the supervisory authority, the Czech Office for Personal Data Protection (uoou.gov.cz).

Just write to licence@sports-analysis.cz. We will reply without undue delay and within one month at the latest. So that we do not hand your data to a stranger, we may check that the request really comes from you. Erasing the data of a device with a valid licence means the licence stops working on that device. For data we process for a club, contact the club; we may pass your request on to it.

10. Changes to this policy

We update this policy whenever what the software, the app or the website processes changes. The current version is always on this page. This policy is effective from 29 September 2026.