Privacy Policy
Last Updated: February 9, 2025
This service uses Google’s YouTube API Services (YouTube Data API v3). By using this service, you understand and agree that your Google user
data (such as playlists and video metadata) may be processed through the API. This is subject to the YouTube Terms of
Service (https://www.youtube.com/t/terms) and Google Privacy
Policy (https://policies.google.com/privacy).
1. Information Collected
The following information is collected through Google OAuth2 authentication:
- Basic Google account information (email address, unique identifier)
- OAuth2 access token and refresh token for accessing YouTube data
- User’s YouTube channel ID, playlists and video metadata
The following technical information is collected automatically for service operation:
- IP address and derived country code (via GeoIP) to identify region-restricted videos
- Service usage logs for quota management and operational monitoring
2. Purpose of Data Use
This service uses the sensitive scope youtube.force-ssl,
which is explicitly granted by users during OAuth authentication. No additional scopes are requested.
The collected information is used only for the following purposes:
- User identification and authentication
- Tracking and analyzing changes in YouTube playlists
- Synchronizing stored playlist data with actual YouTube playlist states
- Detecting broken or unavailable videos and inserting replacement videos
3. Third-Party Data Sharing
Google user data is transmitted only to Google APIs (YouTube Data API v3) as required to perform user-requested playlist operations.
This service does not share user data with any other third parties.
- Data sharing occurs only for normal service operation with Google APIs
- Data may be disclosed when required by applicable law
4. Cookies and Caching Technologies
This service uses essential technologies to maintain security and performance:
Session Cookies (SESSION):
-
Used solely to maintain authentication sessions and secure the OAuth2 login flow. These cookies are not used for tracking or advertising.
Security Cookies (XSRF-TOKEN):
-
Used exclusively to prevent Cross-Site Request Forgery (CSRF) attacks. This cookie ensures that requests made to the server are legitimate and initiated by you. It does not contain any personal data.
Static Resource Caching:
-
Static resources (CSS, Images, JavaScript) may be cached by the browser for up to 30 days to improve loading performance.
5. Data Storage and Retention
The service processes YouTube playlist data in an automated manner to provide its core functionality. This includes:
- Identifying broken or unavailable videos in registered playlists
- Inferring replacement video candidates based on metadata
- Inserting replacement videos into the corresponding playlists
User data is retained only for as long as necessary to provide the service and is not used for purposes beyond those described in this policy.
6. Data Deletion and Access Revocation
User data is managed according to the following data handling and deletion principles:
-
Users may delete their account at any time using the “Delete Account” feature. Upon deletion,
all stored personal data and registered playlist information are immediately removed.
-
Unregistering a playlist removes it from this service’s management without modifying the actual YouTube playlist.
-
OAuth refresh tokens may be revoked by the service or directly by users via Google Security
Settings (https://security.google.com/settings/security/permissions).
7. Security Measures
The following measures are implemented to protect user data:
- Access control based on the principle of least privilege
- Encrypted storage and controlled access to databases
- Periodic security reviews and monitoring
8. Overview of Google User Data Handling
The overall service registration and user data processing follow this sequence:
- User grants OAuth access to Google account and YouTube data
- Playlist data is analyzed to detect unavailable videos
- Once per day, replacement videos may be inserted via YouTube API
- Tokens and playlist metadata are stored securely during service use
- All stored data is deleted when the user revokes access or deletes the account