Privacy policy

01Controller

synadata, sole proprietorship, Kramgasse 2, 3506 Grosshöchstetten, Switzerland. Responsible: Yannick Rubini. Contact for privacy matters: hello@synadata.io.

02Data we process

• Website visits: hosting provider server logs (truncated IP address, time, page requested, browser). Vercel Web Analytics counts page views without cookies and without a personal profile.
• Contact form: name, email address, club, league, role, details on your video situation and the optional message. Plus time and browser identifier for abuse prevention.
• Cockpit (customers): login data via Clerk (email, name, organisation), usage log (which pages and functions were used when), uploaded game videos, tagged or detected events, roster (names, jersey numbers, lines) and the metrics computed from them.
• Game videos contain personal data of players, staff, referees and possibly spectators. We process this data exclusively on behalf of the club that provides the video.

03Purposes

• Answering enquiries and preparing a contract.
• Providing the agreed services: tagging, detection from video, computation of metrics, presentation and reports.
• Operating, securing and debugging the systems, including abuse prevention (rate limiting).
• Improving the detection models. For this we use only data from clubs that have agreed to it in the contract.

04Legal basis and roles

We comply with the principles of the Swiss Federal Act on Data Protection (FADP, Art. 6): lawfulness, good faith, proportionality, purpose limitation, accuracy and data security. Where justification is required we rely on performance of a contract, consent or an overriding interest (Art. 31 FADP).

For website visitors and contact enquiries synadata is the controller. For a club's game videos, rosters and events the club is the controller and synadata the processor (Art. 9 FADP). Details are governed by the data processing agreement.

05Processors and transfers abroad

We use the following service providers. For providers based in the USA we rely on the Swiss-U.S. Data Privacy Framework where the provider is certified, otherwise on the standard contractual clauses recognised by the FDPIC (Art. 16 para. 2 lit. d FADP).

06Retention

• Contact enquiries: 12 months after the enquiry is closed, then deletion.
• Customer data in the cockpit: for the duration of the contract and 12 months thereafter, unless the club requests deletion earlier. Game videos are deleted on request at any time.
• Server logs: at most 30 days.

07Data security

Transmission is encrypted only (TLS). Access to the cockpit only with a personal login and within one's own organisation. Public forms write only through audited database functions with rate limiting. Only persons who need it for operations have access to production data.

08Cookies and analytics

The website sets no tracking cookies. The cockpit uses technically necessary cookies for login. Vercel Web Analytics works without cookies and without cross-device identifiers.

09Mac app “Synadata Desktop”

“Synadata Desktop” is a macOS app for coding, sorting and presenting game video. It works locally on the Mac and exchanges data with synadata only through the user's own Synadata account, and only when the user triggers it.

• Local processing: videos, tags, notes, presentations and recordings stay on the Mac, in package folders the user chooses. The package holds backup copies of the tags (the last ten states). The app does not copy videos to the cloud unless the user actively uploads them (“Upload to Synadata”).
• Sign-in: sign-in is via the Synadata account, with a code in the app and confirmation in the cockpit in the browser. An access token is stored on the Mac, readable only by the user. On the server we store only its hash plus the name of the Mac, the organisation, the role and the time of last use. The purpose is sign-in and licence verification; the licence remains valid for up to 30 days offline. Devices can be signed out in the cockpit; “Sign out” in the app revokes the token. Signed-out device records are deleted 30 days after sign-out.
• Data transfer to synadata: only with the user's own account and only when the user triggers it. This covers loading games, events, line-ups (players' names and jersey numbers) and metrics, synchronising the user's own tags, notes, locations and passes, and video upload and video streaming via time-limited links (Cloudflare R2). The data passes through the same processors as the cockpit (Render, Supabase, Cloudflare R2, Clerk; see table above). Every request includes the app version and the macOS version, for technical troubleshooting.
• Microphone: the app accesses the microphone only for “Record presentation” and only after macOS has granted permission. The recording stays local (Movies/Synadata folder) and is not transmitted.
• No tracking: the app contains no advertising and no third-party analytics or crash-reporting services. Error messages go only to the local macOS log, without content and without tokens.
• Player data in local packages (names, numbers, statistics) is the responsibility of the club or the user, as in the cockpit. The club informs the data subjects and obtains consent where required, in particular for minors (see data processing agreement).
• Deletion: the user deletes local data themselves by deleting packages or removing the app. For data in the cloud the section “Your rights” applies; information and deletion via the contact named there.
• Distribution: the app is distributed as a notarised download (Apple Developer ID). A later version in the Mac App Store is possible; in that case Apple's terms apply in addition.

10Your rights

• Information on whether and which data we process about you (Art. 25 FADP).
• Correction of inaccurate data (Art. 32 FADP), deletion, restriction of processing.
• Hand-over or transfer of your data in a common format (Art. 28 FADP).
• Objection to processing and withdrawal of consent with effect for the future.
• Complaint to the Federal Data Protection and Information Commissioner (FDPIC).
• Requests to hello@synadata.io. We reply within 30 days.

11Changes

We update this policy when processing or the legal situation changes. The version published on this page applies.