Privacy: Synadata Tagger

01Controller

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

02Data the app processes

The app does not access location, contacts, photos, camera, microphone or health data. It contains no advertising, no tracking and no third-party analytics or crash-reporting services.

• Tags: time, type (e.g. shot, goal, face-off), location on the field, team, line, game situation and additional details defined by the club, optionally a jersey number.
• Name of the session (e.g. opponent and date) and the device name, so the cockpit shows which device set a tag.
• Sign-in: the app shows a code that a signed-in person confirms in the synadata cockpit. The app then stores a device token in the device keychain. On the server we store only its hash, the device name, the organisation and the time of last use. Email address and password are never entered in the app.
• Joining via QR code: additional devices receive a time-limited token valid for one session only.
• Demo without account: everything stays in the device memory, nothing is transmitted.

03Purpose

Exclusively for analysis in the club's synadata cockpit: placing tags on the game video, computing shots and metrics, finding scenes. No disclosure to third parties for other purposes.

04Roles

The club is the controller for the recorded game and practice data, in particular jersey numbers and thus personal data of players. synadata processes it on the club's behalf (Art. 9 FADP). Details are governed by the data processing agreement with the club.

05Where the data is stored

For providers in the USA we rely on the Swiss-U.S. Data Privacy Framework where certified, otherwise on standard contractual clauses (Art. 16 para. 2 lit. d FADP). Without a network the app stores tags on the device until they are uploaded, then removes them from this buffer.

• Render Services Inc.: operation of the synadata API that receives the tags (EU / USA).
• Supabase Inc.: cockpit database (EU, Ireland).
• Clerk Inc.: cockpit login used to confirm the sign-in code (USA).

06Retention and deletion

• Signing out in the app revokes the device token on the server and deletes it on the device.
• Sessions are kept for the duration of the club's contract and 12 months thereafter, unless the club requests earlier deletion.
• Deleting the app removes all locally stored data.

07Your rights

You can request information about your data, its correction or deletion. If the data concerns a club, we forward the request to it. Requests to hello@synadata.io. Complaints can be filed with the Federal Data Protection and Information Commissioner (FDPIC).