Privacy Policy

LOL Champion Replays — last updated 11 September 2026

This policy explains how LOL Champion Replays ("the application") accesses, uses, stores and shares Google user data. The application is operated by Huy Quảng Phạm ("the operator"), who is also its only user.

1. Scope of this policy

The application is a private desktop tool that organizes playlists on YouTube channels owned by the operator. It has no other users, no sign-up, and no public interface. The only Google Account whose data it accesses is the operator's own.

2. Google user data the application accesses

The application requests a single OAuth scope:

• https://www.googleapis.com/auth/youtube — manage the operator's YouTube account.

Using that scope, it calls only the following YouTube Data API v3 resources, and only against channels the operator owns:

From these calls the application reads video metadata belonging to the operator's own channels: video ID, title, publication date and privacy status. It does not read video files, captions, comments, subscriber identities, analytics or revenue data.

3. What the application does not access

• No data belonging to any Google Account other than the operator's own.
• No YouTube search, comment, subscription or analytics endpoints.
• No Gmail, Drive, Calendar, Contacts or profile data beyond the sign-in identity required to complete the OAuth flow.
• The application does not upload videos through the YouTube Data API.

4. How the data is used

The data listed in section 2 is used for exactly one purpose: deciding which of the operator's videos belong in which of the operator's playlists, performing those playlist changes, and verifying afterwards that each change took effect. It is not used for profiling, advertising, training machine-learning models, or any form of analysis unrelated to playlist organization.

5. How the data is stored and secured

• OAuth credentials. Refresh tokens and the client secret are stored in a single local file on the operator's own machine, in a directory outside every network share, with access restricted to the operator's account, the local Administrators group and the SYSTEM account. They are never transmitted anywhere except to Google's own OAuth endpoints.
• YouTube metadata. Video and playlist metadata is cached in a local database on the same machine, used only to avoid repeating API calls that have already been made. The database is not exposed to the internet.
• All API traffic uses HTTPS.

6. Retention and deletion

• Cached YouTube metadata is refreshed from the API on an ongoing basis and fully refreshed at least once every 30 days; entries for videos that no longer exist on the channel are deleted when that refresh runs.
• The operator can delete the entire local cache at any time; doing so removes all stored YouTube data and the application simply re-reads what it needs from the API.
• If the operator revokes the application's access, the stored refresh token becomes unusable and is deleted along with the cache.

7. Sharing and disclosure

Google user data obtained through the application is not shared with, transferred to, or sold to any third party. There are no third-party analytics, advertising, logging, or backup services involved. No human other than the operator has access to it.

8. Revoking access

Access can be revoked at any time at myaccount.google.com/permissions. Revocation immediately ends the application's ability to read or change anything on the account.

9. YouTube terms

The application uses YouTube API Services. By using it, the operator is bound by the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy.

10. Changes to this policy

If the data the application accesses or the way it is used changes, this page is updated and the date at the top is revised.

11. Contact

Questions about this policy: huyquang1376@gmail.com