Privacy policy

Soccer Match Studio runs on the editing computer. It keeps source recordings, renders, project files, and match tags on that computer. The operator chooses when to send the rendered videos to YouTube.

Google and YouTube access

Google handles sign-in. The app receives OAuth tokens and uses them to identify the connected channel, upload selected renders, and check video IDs, processing status, and visibility. Uploads include the selected video and its upload settings, such as title, description, audience, and visibility. YouTube makes each upload available according to its visibility setting and handles that data under Google’s Privacy Policy.

Storage and removal

The editor stores the refresh token, upload checkpoints, selected upload settings, and YouTube video IDs in the current user’s local application data folder. It uses those records to reconnect, resume interrupted uploads, and avoid uploading the same video twice. The public information pages do not receive those records, OAuth credentials, or match footage.

Use Disconnect YouTube in the editor or remove the app in Google Account connections to revoke access. Disconnecting in the editor removes the local saved account credential. Local project files and upload records remain until the operator removes them. Manage published videos in YouTube Studio.

Use and disclosure

Soccer Match Studio uses Google user data to provide the YouTube features described above. It does not sell that data or use it for advertising. Its use of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

The site’s hosting provider may process standard web request information to deliver these pages. For questions about the editor or its data practices, use the support contact shown on the Google consent screen.