01The short version
- CastMyGame never records or stores video. The live picture passes from the camera phone straight to YouTube.
- We keep what a match needs: its title, teams, scoring events, the phones paired to it and the YouTube channel it streams to.
- Organisers sign in to the web portal with Google. Camera and scorer phones do not need an account.
- We do not sell data, show ads, or use advertising identifiers or tracking cookies.
02Who we are
CastMyGame is operated by Agile Tech Forge ("we", "us"). We are responsible for the personal data described here. Questions and requests go to support@agiletechforge.com.
03What we collect
Organisers using the web portal
- Google account profile: your name, email address, profile picture and Google account identifier, received when you sign in with Google. We use them to identify you and show who is signed in.
- Connected YouTube channel: the channel identifier and name, and the OAuth tokens Google issues when you connect it. We use them only to create live broadcasts and streams on that channel, read their status, and check the daily API quota.
- Browser storage: your browser keeps the sign-in session and a few display preferences in local storage so you stay signed in. We set no advertising or analytics cookies.
Matches
- Match title, sport, team or player names, competition, venue, sponsor logo address and overlay settings.
- The scoring log (each point, goal, run or correction) and the match status and times.
- The join code, which phones joined, their camera slots and their live stream health (bitrate, connection state).
Phones running the app
- An anonymous identifier created when the app is installed, and the device name, which you can change.
- Camera and microphone access, used only while a phone is filming a match. The picture and sound are sent to the YouTube ingest for your broadcast and are not stored by us.
Spectators
The public watch page needs no account. It loads the match details and score and embeds the YouTube player.
What we do not collect
Location, contacts, photos or files on your device, payment details, advertising identifiers, or analytics about how you browse.
04How we use it and why
We use the data above to run the service you asked for: signing you in, creating and directing matches, drawing the scoreboard overlay, sending each broadcast to your channel and showing it on the watch page. We also use it to keep the service secure and to fix faults.
Where data protection law asks for a legal basis, we rely on performing our agreement with you (running your matches) and on our legitimate interest in operating and securing the service. Connecting a YouTube channel is based on your consent, which you can withdraw at any time.
05Google and YouTube data
CastMyGame uses YouTube API Services. By connecting a channel you also agree to the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy.
Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use YouTube access only to manage the live broadcasts you start, we do not use it for advertising, and we do not transfer it to anyone except as needed to provide the service or where the law requires.
You can revoke CastMyGame's access at any time from your Google Account permissions page. Revoking it stops new broadcasts; ask us at support@agiletechforge.com to delete the stored tokens and channel details as well.
07How long we keep it
- Video: never stored by us. YouTube keeps a broadcast on your channel until you delete it there.
- Account, matches and scoring logs: while your account is in use, and deleted when you ask us to.
- YouTube tokens: until you disconnect or revoke access and ask us to delete them, or they expire.
- Anonymous phone identifiers: while the app is installed and the phone is linked to matches, and deleted on request.
08Security
The portal, the API and the realtime connection run over HTTPS and secure WebSockets. Access tokens are verified on every request and each organiser only reaches their own matches. The live picture currently travels from the phone to YouTube over RTMP, the protocol YouTube provides for live ingest, which is not encrypted in transit. No method of transmission or storage is completely secure, but we work to protect your data and will tell you about a breach where the law requires.
09Your choices and rights
You can ask us for a copy of your data, to correct it, to delete it, or to restrict or object to how we use it. Depending on where you live (for example the UK, the EU or California) you may have further rights, including complaining to your data protection authority.
Email support@agiletechforge.com from the address on your Google account, or tell us the device name for a phone. We answer within 30 days.
10Children and people on camera
CastMyGame is for club organisers and is not directed at children under 13. We do not knowingly collect their personal data.
Matches often include people who are not users, including young players. The organiser who streams a match is responsible for having the permission of the venue, the players and, for minors, their parents or guardians. If you appear in a broadcast and want it removed, contact the channel that published it, or write to us and we will pass the request on.
11International transfers
Our providers may process data in countries other than yours, including the United States. Where the law requires it, those transfers are covered by appropriate safeguards such as standard contractual clauses.
12Changes to this policy
When we change this policy we update the date at the top of the page. If a change materially affects how we use your data, we will tell signed-in organisers before it applies.
13Contact
Agile Tech Forge, for CastMyGame: support@agiletechforge.com.