Privacy Policy

Why this page exists

The site is designed to keep playlist browsing usable without a server-side app or a custom runtime API.

Because everything is static, privacy behavior is mostly determined by the build options and by what the browser stores locally.

How the site works in your browser

This site is generated as static files and does not require a live server-side application to render the main experience.

Most interactions happen in your browser using the data embedded into the generated pages.

When data leaves the page

Reporting is enabled for this build, so report submissions can send selected reasons to the configured endpoint.

The generated pages do not add background analytics or third-party API calls on their own.

Browser storage

Preference storage is enabled, so the site may keep appearance and current-view state in browser storage.

Stored preferences can usually be removed with the Clear local data action in Settings.

Shared URLs

State sharing is enabled, so copying the current view can place filters and pagination state into the URL.

You should review shared URLs before sending them if the current view contains state you do not want to expose.

Media loading

Thumbnail mode is remote, so the site may load thumbnail images from upstream hosts.

Embedded playback may load a YouTube player when you choose to play content on page.

Thumbnail and playback behavior can be changed by the build configuration and by the user's settings choices.

Trackers and third parties

The generated site itself does not add cookies for analytics, trackers, or advertising scripts by default.

External embeds or hosts may still apply their own tracking when you open third-party pages or players.

Hosting and transport

The configured public URL uses HTTPS, so page delivery can be protected in transit.

Your hosting setup may add its own logs, TLS termination, or caching behavior outside this generator, and it does not choose the certificate provider for you.

Where the playlist data comes from

Playlist pages are generated from input metadata files provided to the build command.

Those files may already include video, channel, and playlist metadata from upstream systems.

Data freshness and retention

The generated site itself does not keep a server-side session store.

Any longer-term retention depends on browser storage, shared URLs, and the external host serving the files, so the generator does not promise a universal automatic delete-after-28-days schedule.

Copyright and source material

Playlist and video metadata remain subject to the rules and licenses of their original sources.

This generated site only republishes the metadata and assets configured by the build process.