Data processing agreement (DPA)
Confirm the processing arrangement and whether a DPA is required.
Request documents
GAMETRAQ 6 · GDPR & Privacy
GAMETRAQ 6 processes sports analytics locally on-device with Edge AI, reducing the need to transfer raw footage to cloud AI processing.
For European padel clubs, distributors and players. Local analytics support privacy-conscious deployment; recording, storage and sharing still need their own assessment.
01 / Local intelligence
Sports analysis runs on the camera rather than requiring raw footage to be sent to cloud AI for that analysis. This can reduce unnecessary transfers and supports a data-minimisation approach.
Privacy by design also depends on deployment choices: what you record, why you use it, who can access it and whether it is shared. Edge AI alone does not establish GDPR compliance.
02 / Sports, not face identification
Ball movement and play on the court.
Player movement and court coverage.
Sports statistics about rallies and play.
Selected moments from recorded play.
Video and player-related statistics can be personal data when a person is identifiable. No biometric face identification is advertised. Sports analytics should not be treated as automatically anonymous.
03 / Understand the data flow
The camera processes sports analytics locally using Edge AI.
Video storage, analytics outputs and dashboard use are separate from local AI. Confirm destinations and handling for your delivered configuration.
Publishing a livestream or sharing clips may send data to external services and a wider audience. Assess these flows separately.
Detailed technical data-flow and configuration information: available upon request / to be confirmed.
04 / Responsibilities
Controllers and processors depend on the actual processing arrangement and who determines the purposes and means. A club may be a controller and GAMECAM may process data on its behalf for agreed services, but neither role is assigned automatically by this page.
Confirm the responsibilities of the club, distributor, GAMECAM and any platform providers, and put a DPA in place where required.
05 / Before recording
Identify and document an appropriate lawful basis for each purpose. Do not assume that entering a court or seeing a sign amounts to valid consent.
Use clear signage before people enter the filmed area and provide a detailed privacy notice covering purposes, data use, recipients, retention, rights and a contact. Consider players, spectators and children, and assess whether a data protection impact assessment is needed.
06 / Confirm your configuration
Agree how authorised access and rights requests will be handled, and choose retention appropriate to your purposes. The following technical specifics are not asserted as verified by this page.
07 / Public broadcasting
A public livestream is a separate purpose and disclosure from local sports analysis. Assess its lawful basis, tell players where the stream will appear and consider the implications for spectators and children before broadcasting.
Review the platform's terms and privacy notices, possible international transfers, and how public clips can be reshared. Local Edge AI does not remove those requirements.
08 / Prepare with confidence
Request the documents and validated information relevant to your deployment. Availability and the final contents are to be confirmed; no approved templates or downloadable documents are represented here.
Confirm the processing arrangement and whether a DPA is required.
Request documentsRequest a template for review and adaptation to your club's actual use.
Request documentsRequest validated retention and deletion details for your configuration.
Request documentsRequest the relevant providers, locations and transfer information.
Request documents09 / Ready for your club
A practical starting point for your deployment review, not a legal sign-off.
For privacy requests or deployment questions, contact magnus@gamecam.se.
10 / Common questions
Talk through your club's use, request documentation and confirm the details before you record.
This page describes privacy-supporting design features and recommended deployment practices. It is not a certification or legal opinion; each deployment must be assessed for GDPR compliance.