Last updated: July 27, 2026

Privacy Policy

This policy applies to Google authentication, the optional YouTube upload feature, and optional match-data sharing in LeagueRecord Custom (“the App”).

1. Purpose of the feature

The App lets a user explicitly select a completed local recording or clip and upload it to the user's own authorized YouTube channel. The App never uploads a video without an explicit user action.

2. Google and YouTube information

The App uses Google OAuth 2.0 and YouTube API Services. It requests openid and email to establish the user's identity, youtube.upload to upload user-selected videos and thumbnails, and youtube.readonly to identify the connected channel, check upload processing, and determine whether videos previously shared through the App are still available. The read scope is not used to collect or analyze the user's general YouTube activity.

• The email address is used by Firebase Authentication to identify the user and manage ownership of match data. It is not included in public match JSON.
• Google access and refresh tokens stay on the user's computer and are encrypted at rest using operating-system-backed encryption.
• An ID token is used briefly to establish a Firebase session. It is not stored in match JSON or the developer's database.
• The App does not send or store Google passwords, YouTube login credentials, access tokens, or refresh tokens on the developer's servers.
• Google and YouTube data is not sold, used for advertising, or shared for unrelated purposes.

3. Information sent to YouTube

Only after the user starts an upload, the App sends the selected video file and the user-confirmed title, description, visibility, audience setting, category, and thumbnail to YouTube. The App displays the connected channel and visibility before the upload begins.

4. Match data stored in Firestore

If the user separately chooses to publish match data, the App stores the YouTube video ID and the match JSON needed to display the timeline and scoreboard in Google Cloud Firestore. Google tokens, email addresses, and local file paths are excluded from public match JSON.

Shared match data is not available through a browseable public index, but a person who knows the corresponding YouTube video ID can retrieve it. An anonymization option can remove player-identifying fields before publication. Private rate-limit information may be stored to prevent abuse.

5. Retention, deletion, and revocation

Local Google tokens may remain until the user disconnects Google in the App or revokes access through Google. Disconnecting requests token revocation from Google and deletes the encrypted local token file. The App does not copy or retain uploaded video files on the developer's servers.

To request deletion of match data published to Firestore, contact support with the relevant YouTube video URL. Do not send a password or token. Users can also review or revoke access from Google Account permissions. Data subject to a valid deletion or revocation request will be removed as required by the applicable YouTube API Services policies.

6. Third-party services and Limited Use

Use of YouTube features is subject to the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.

The App's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

7. Security

Access and refresh tokens remain in the Electron main process and are not exposed to the renderer UI. The App refuses to persist a Google connection if secure OS-backed storage is unavailable. More detail is available on the Security and Shared Data page.

8. Contact and changes

Privacy and deletion requests are accepted through LeagueRecord Custom support. Do not include credentials or sensitive personal information. If this policy changes, this page's last-updated date will be revised.

Never send a password, access token, or refresh token in a support request.