← Back

Privacy Policy

Last updated: 7 October 2026

Overview

Playlist Sorter (“we”, “our”, or “us”) helps you sort and combine your YouTube Music playlists. This policy explains how we handle information when you use playlist.yong.ee, including the data shared for AI sorting and the connection saved in your browser.


YouTube API Services

Playlist Sorter uses YouTube API Services to read your playlists and carry out the playlist changes you request. Google and YouTube also process information under their own policies.

Google Privacy Policy · YouTube Terms of Service


Information we access

When you connect your Google account, we receive OAuth access and refresh tokens that let the app make authorized YouTube API requests. We do not receive your Google password.

  • Your YouTube channel name and profile image.
  • Playlist names, IDs, descriptions, item counts, and thumbnails.
  • Videos in selected playlists, including video IDs, titles, video-owner channel labels, and thumbnails. Channel labels appear as artist information in the app.
  • Your choices in the app, including selected playlists and moods, edits to song groupings, and destination playlist names and IDs.

Some metadata is returned with API responses even when it is not displayed. The playlist features do not read your watch history, subscriptions, comments, payment information, or audio recordings.


How we use your data

We use this information to display your library, combine and deduplicate selected songs, suggest mood groupings, and create or update playlists when you choose to save your results. Mood suggestions use song metadata; the app does not listen to or analyze the audio.

New playlists created by the app are private. If you add songs to an existing playlist, its existing visibility setting remains in place. These changes are saved in your YouTube account.


AI processing and other services

Before each AI sorting run using your connected library, we ask you to agree to the AI-sharing notice. If you agree and start sorting, our server sends the selected songs’ titles and video-owner channel labels, along with the selected mood IDs, labels, and descriptions, to OpenRouter. OpenRouter forwards the request to the AI model provider serving it and returns suggested mood labels, confidence values, and explanations.

The app replaces YouTube video IDs with temporary track references for each AI request. It does not include your Google OAuth tokens, account profile, playlist names or IDs, or image URLs in the classification request. Song titles and channel labels can still identify the songs; the request is not anonymous merely because the video IDs are replaced.

You can decline AI sorting and use the combine-only workflow. Combine-only and demo classification do not call the AI service. Demo classification uses sample data and runs locally in your browser. AI suggestions come from Playlist Sorter and its AI service providers, not YouTube.

OpenRouter and the model provider process requests under their policies and the service configuration. Logging, retention, and use for training can differ by provider and settings. We have not verified the production retention periods or training settings and cannot promise zero retention or no use for training.

OpenRouter Privacy Policy · Model provider data policies

Google receives the API requests needed to load and update playlists. When your browser loads account images or video thumbnails, it also contacts the image host, which receives the network information needed to deliver those images. Our hosting services process network requests to operate the app.


Data retention and cookies

Working playlist data and classification results are held in the page’s memory and processed during server requests. The app has no application database storing your playlist library or sorting history. It does not intentionally save unsaved working data for later browser sessions.

To keep your YouTube connection available, the app stores an encrypted authentication cookie in your browser containing OAuth tokens. It is configured to expire 365 days after it is set and can be renewed when you use the app. Google may invalidate the tokens earlier. A separate sign-in cookie is configured to last up to two hours. Temporary sign-in state is also held in server memory to validate the sign-in flow. A separate connection-state cookie lasts up to 400 days from sign-in or clearing the connection. It prevents late requests in another tab from restoring access after you clear the connection; a new sign-in replaces it.

The authentication cookie is HttpOnly, so page scripts cannot read it. It uses SameSite=Lax and is marked Secure in production. These are connection cookies; clearing the current workflow alone does not remove them.

Hosting services, OpenRouter, and model providers may keep independent logs or other records of requests they process. We have not verified their retention periods. Removing browser data does not erase those records, and the absence of an application database does not mean all data is immediately deleted.


Your choices and deletion requests

Clear this browser’s connection

Use “Clear connection” in the app to expire its authentication and sign-in cookies, mark the browser connection as cleared, and reset the current page’s working state. A late request may return an authentication cookie, but the separate connection-state cookie prevents it from restoring access. You can also remove site cookies through your browser settings. Close or reload other open app tabs to clear their working state.

This does not revoke the permission recorded by Google, undo requests already sent to a service, or delete playlists saved in YouTube. “Start over” restarts the workflow without clearing the connection.

Revoke Google access

To revoke Playlist Sorter’s access to your Google account, remove its access in Google’s app-permissions settings. You can then clear the browser connection as described above.

Manage Google app permissions →

For privacy questions or to request deletion of data held by Playlist Sorter, email yongee2003@gmail.com. Please do not send passwords or access tokens. Deletion from this app does not delete playlists or other information stored by YouTube; manage or delete those items in YouTube or YouTube Music.


Security

The app encrypts its authentication cookie before storing it in your browser and uses HTTPS for requests to Google and OpenRouter. The server uses the tokens to perform authorized YouTube operations. These measures reduce risk but cannot guarantee absolute security.


Changes to this policy

We may update this policy as the app changes. The date at the top identifies the current version. If a change requires renewed consent, we will ask for it before the new processing begins.


Contact

For questions about this policy or requests concerning your data, contact yongee2003@gmail.com.

Also see our Terms of Service