Effective date: September 4, 2026 · Operator: Chris Rohn ("we", "us") · Contact: chrisrohn@gmail.com
1. What this site is
chrisrohn.com ("the Site") is Chris Rohn's personal new-music discovery feed, used to pick tracks for the "Indie Discotheque" playlists on YouTube Music. It is a static website hosted on GitHub Pages. We run no servers of our own, we do not operate user accounts, and we do not sell, rent, or trade any personal information.
2. Information we collect
2.1 Visitors who just listen
- No personal data is collected by us. There is no sign-up, no analytics, and no advertising.
- Browser storage. Your filter choices (sources, sort order, search text) are saved in your browser's local storage so they persist between visits. This never leaves your device.
- API activity log. For a signed-in user, the Site keeps a list of the last few hundred YouTube Data API requests it made from that browser (endpoint, playlist and video IDs, result, quota cost, and the reason), shown under ⚙ → API activity. It is stored only in that browser's local storage, is never transmitted anywhere, and is removed with Clear in that view or by clearing local state.
- Hosting logs. The Site is served by GitHub Pages. GitHub may log standard technical information (such as IP address and user agent) under the GitHub Privacy Statement. We do not receive or use those logs.
- Embedded YouTube player. Tracks play through YouTube's embedded player. When a video loads, YouTube/Google may set cookies and collect data as described in the Google Privacy Policy.
2.2 Curators who sign in with Google
Anyone may use "Sign in with Google". The Site uses YouTube API Services to let a signed-in user file tracks into playlists in their own YouTube library: the curator's approvals go to the "<year> | Indie Discotheque" playlists, and any other signed-in user's approvals go to "<year> Picks from chrisrohn.com" playlists in that user's library. No user can write to another user's playlists. When you sign in, the Site requests permission for:
- Basic profile (openid, email): your email address, display name, and profile picture. Used only to show who is signed in and to decide whether the account is the curator (Indie Discotheque playlists) or a guest (your own "Picks" playlists).
- App configuration data in Google Drive (drive.appdata scope): used to store one small JSON file, in a hidden folder only this Site can see, listing the tracks you have thumbed up or down (artist, title, YouTube video ID, year, timestamp). This is what keeps your ratings in step across your devices. The Site cannot see, read, or change any other file in your Drive.
- Manage your YouTube account (youtube scope): used only to list your playlists, create a year playlist or the unlisted "Skipped" playlist if one is missing, add a track to a playlist when you press Keep or Skip, and remove that entry if you press Undo. The Site never reads your watch history, subscriptions, comments, or private videos, and never posts, comments, or uploads on your behalf.
Optional: a GitHub token (curator only). A curator can paste a fine-grained GitHub personal access token into ⚙ so the Site writes the list of rated tracks (artist, title, YouTube video ID, year, decision, timestamp — never your Google account) to a file in the Site's own public repository, where the daily build learns from it. The token is stored only in that browser's local storage, is sent only to api.github.com, and is removed by clearing local state in ⚙. Without a token nothing is sent to GitHub.
Where this data lives. The Google access token, your email, name, and picture, and the IDs of your year playlists are stored only in your browser's local storage on the device you signed in from. The list of tracks you rated is kept in that local storage and mirrored to the hidden app-data file in your own Google Drive described above; deleting that file (Google Drive → Settings → Manage apps → this app → Delete hidden app data) or revoking access removes it. The access token expires after about one hour. Nothing is transmitted to us or to any server we control, because there is none; all YouTube API calls go directly from your browser to Google.
Sharing. We do not share, sell, or transfer any Google user data to third parties. We do not use it for advertising, profiling, or any purpose other than the playlist functions described above.
Retention and deletion. Press Sign out to forget your identity, ratings mirror and playlist IDs on that device (the hour-long access token is kept only for the browser session and is discarded when the tab closes), or use ⚙ → Clear local state to erase everything the Site stored. You can also revoke the Site's access at any time from your Google security settings. Because we hold no copies, revoking access removes all of it.
2.3 The daily feed build
Once a day an automated job builds the feed from public data: Last.fm listening statistics for the curator's account, public MusicBrainz and ListenBrainz release data, Bandcamp, Deezer, and music-blog RSS feeds. It also reads the curator's public YouTube year playlists and the unlisted "Skipped" playlist (by ID) to avoid re-suggesting tracks that were already saved or skipped. Artist names and track titles derived from those playlists are stored in the Site's public source repository. This concerns the curator's own playlists only; no other user's YouTube data is read.
3. YouTube API Services disclosures
- This Site uses YouTube API Services. By using the Site you agree to be bound by the YouTube Terms of Service.
- Google's handling of your data is described in the Google Privacy Policy.
- You can revoke the Site's access to your data via the Google security settings page.
- The Site stores YouTube authorized data (your access token and playlist IDs) only in your browser, as described in section 2.2, and does not store it on any server. It does not use authorized data for any purpose other than the playlist functions you invoke.
4. Cookies
The Site itself sets no cookies. It uses browser local storage as described above. Embedded YouTube players and Google sign-in may set their own cookies, governed by Google's policies.
5. Children
The Site is not directed at children under 13 and we do not knowingly collect information from them.
6. Changes
We may update this policy; the effective date above will change when we do. Continued use of the Site after a change means you accept the updated policy.
7. Contact
Questions about privacy: chrisrohn@gmail.com.