Privacy Policy

Why this page exists

This project generates static playlist pages, but even a static site can still use browser storage, open third-party media, or sit behind normal hosting infrastructure. This privacy page is here so you can see those tradeoffs clearly before you browse.

In short: the generated site tries to keep as much state as possible in your browser, loads YouTube only when a feature needs it, and does not add ads, trackers, or account-gated behavior on top of the playlist data.

How the site works in your browser

The interactive parts of the site run on the client side. JavaScript in your browser handles filtering, sorting, pagination, current-view sharing, modal dialogs, the Data View, and other page interactions after the static files have loaded.

Normal browsing does not send that page state back to the site operator for server-side processing. Searches, filter choices, hide/lock state, and viewer interactions stay in the browser unless you deliberately use a feature that shares or submits data.

When data leaves the page

If this build shows Report video, a report is only sent when you intentionally submit that form. The submission goes to the configured HTTPS report endpoint.

Outside of that exception, network traffic is limited to the static files themselves plus any third-party resources you intentionally trigger, such as YouTube thumbnails, YouTube playback, or opening a YouTube page in a new tab.

Local preference storage

Theme, contrast, large-text, and videos-per-page preferences can be stored in this browser when preference storage is on.

When these preferences are stored, they stay on this device for this site origin. Using Clear local data removes those saved settings from this browser. That keeps appearance choices local instead of turning them into a remote profile of what you watch or how you configure the interface.

Shared state in the URL

Filter, sort, and pagination state can be written into the page URL so the current view can be shared.

When shared state is enabled, the URL can include search text, selected filters, sort order, page-size choices, the current results page, and current-view lock/hide state on both playlist pages and the index page. That can be useful for sharing a view, but URLs can also show up in browser history, screenshots, copied links, referrer headers, and routine server logs.

Thumbnails, embeds, and media loading

Video thumbnails load from YouTube image hosts when they enter view.

The in-page player stays inactive until you choose Playlist or Current View under Play on this page, and then loads youtube-nocookie in the configured player shell.

Remote thumbnails and playback depend on YouTube-controlled hosts. Local placeholder thumbnails are generated during site build and shipped with the static output. Keeping those requests optional matters because every third-party image or media request can reveal timing information, IP address, and normal browser request metadata to another service.

Cookies, trackers, ads, and device data

The generated site itself does not add cookies for analytics, does not ship trackers, and does not serve ads. It also does not include device fingerprinting logic or other analytics code meant to profile your browser.

That said, normal web hosting can still see ordinary request metadata such as IP address, user-agent, and request timing. This page describes the behavior of the generated site code; it does not erase whatever routine logs your host or CDN keeps outside that code.

Hosting, HTTPS, and routine logs

The public URLs for this build use HTTPS, so requests are expected to be encrypted in transit. Certificate management is handled by the deployment rather than by the generated site itself.

The generated site code does not choose the certificate provider, so this policy does not promise a specific issuer such as Let's Encrypt for every deployment. Your hosting provider or CDN may also keep ordinary request, error, or bandwidth logs outside the generated site itself.

Where the playlist data comes from

The pages are generated from playlist JSON inputs. In the intended workflow for this repository, those inputs are assembled from YouTube API-backed collection and publishing steps rather than by scraping YouTube page HTML.

The static site generator then reads that prepared data and renders HTML, CSS, JavaScript, and optional local placeholder assets. In other words, the browsing interface is static, but the content it shows comes from an upstream metadata pipeline.

Data freshness and retention

This repository is designed around refreshable YouTube API data, not around treating the generated site as a permanent archive. Upstream collection, organize, publish, and redirect workflows are responsible for deciding when data is refreshed, replaced, redirected, or removed.

Because that maintenance happens outside the browser-facing site generator, this privacy page does not promise a universal automatic delete-after-28-days schedule or a guaranteed redirect replacement policy for every deployment. What it can say truthfully is that the project expects API-derived data to be maintained through rebuilds and publishing workflows instead of being treated as timeless scraped content.

Copyright and ownership

The videos linked from these pages remain the property of their original creator, publisher, or other rights holder. Running this site does not transfer ownership of those works, and the site operator does not claim copyright in the linked video content itself.

This site republishes metadata and links so the playlists can be browsed in a simpler static interface. Watching a video on YouTube or through a YouTube-powered embed is still governed by YouTube and the original publisher.