YT-LOOPERBack to Billboard

PRIVACY

Privacy policy

YT-LOOPER lets people arrange embedded YouTube videos into audiovisual pieces. This page explains what stays in your browser, what is stored when you publish a share link, and when third-party services receive data.

Last updated: November 15, 2026

Data stored in your browser

The editor keeps working project data and preferences in browser storage so you can return to them on the same device. This may include your song arrangements, video identifiers and settings, theme, editing-mode preferences, and local song history. A small cookie may remember viewer preferences such as whether the MIDI note view is shown.

This local information is controlled by your browser. It is not a cloud account and will not automatically follow you to another device. You can remove it by clearing site data for yt-looper.com, though doing so can erase projects that have not been published elsewhere.

Shared projects, charts, and views

When you choose to create a share link, YT-LOOPER stores a server-side project snapshot so the performance can be recalled by its unique link. A snapshot can include the project title, YouTube video IDs and related source details, arrangement and playback settings, and any artist name or provider badge you chose to publish.

A shared piece updates its play count only after its samples load and confirmed media playback begins, once per browser tab session. Merely opening a link, failed loading, replaying, and looping do not add plays. Published titles, thumbnails supplied through YouTube, optional artist credit, and aggregated play counts may appear on the public Billboard chart.

Server logs and security

Our web server, application host, and infrastructure providers may create standard technical logs. Depending on the provider and request, these can include an IP address, browser or device information, requested URL, timestamp, response status, and security diagnostics. We use this information to operate, secure, troubleshoot, and understand the service—not to build a local YT-LOOPER user account.

Privacy-focused site analytics

YT-LOOPER uses a self-hosted Umami analytics service to understand visits to the Billboard, editor, and shared Experience pages. It records aggregated usage details such as the page visited, referrer, browser and device category, and an approximate country or region derived from network information. The analytics service does not use tracking cookies, does not create advertising profiles, and does not receive the contents of your locally saved songs.

YouTube and other external services

YT-LOOPER embeds YouTube players rather than hosting the source video or audio. Loading or interacting with an embedded player connects your browser to YouTube and Google. Those companies may receive technical data and may read or set cookies according to your browser settings, Google account settings, and their own policies. See Google’s Privacy Policy.

Links that leave YT-LOOPER are governed by the destination’s policy. Blocking third-party media or cookies may limit playback.

Optional identity-provider verification

If YT-LOOPER offers an optional “verify with” feature and you choose it, your browser will be sent to the named OAuth provider for sign-in. That provider handles your credentials. YT-LOOPER may request the basic profile information needed to display the verified name and provider badge with your creation. The sign-in screen identifies the provider and permissions before you continue.

You can instead use an unverified text artist name, or publish without artist credit. Verification providers process information under their own privacy policies.

Google AdSense and advertising

If advertising is enabled, ads appear only alongside the Billboard homepage. Google AdSense and its advertising partners may use cookies, device identifiers, IP addresses, and information about prior visits to deliver, limit, personalize, measure, and protect ads. Google explains this use in How Google uses information for advertising.

You can manage Google ad personalization in Google Ads Settings and may have additional industry opt-out choices through YourAdChoices. Browser controls can also block or delete cookies, although doing so may affect ads and embedded media.

Where law requires it, a consent or privacy message may ask you to accept, reject, or manage advertising choices before eligible advertising storage or personalization is used. Some regions may treat certain advertising disclosures as a “sale” or “share” even when information is not exchanged for money; applicable privacy controls will be presented when configured for those regions.

Retention and deletion

There is no local YT-LOOPER account dashboard for data requests. To report a privacy problem or request review of a specific public share, open an issue through the contact link below and include the share URL. Do not post sensitive personal information in a public issue.

Contact and policy changes

For privacy questions or a request concerning a shared piece, use the YT-LOOPER GitHub issue tracker. GitHub issues are public, so describe the request without including private credentials or unnecessary personal data.

We may update this policy as the service and its providers change. The date at the top shows the latest revision.