Privacy policy

Last updated: 2 October 2026

Music Shorts is a private, local application operated by Daniel Ropot to prepare and upload his own music videos to his own YouTube channel. This policy covers that application and its public information website at music-shorts.ropot.de.

Information used by the local application

• Supplied song audio, images or videos, lyrics, song titles, artist information, editing choices and rendered output files.
• Google OAuth authorization tokens and the connected YouTube channel's ID and title. Google handles sign-in; the application does not ask for or store the Google account password.
• Video IDs, titles, descriptions, tags, visibility, release times, audience and synthetic-content settings, and upload and approval records.
• Approved thumbnails, subtitle tracks, playlist identifiers, the owner's comment drafts and the IDs/status of comments posted by the application.
• The connected channel's video inventory and aggregate performance reports, including available views, engagement, watch time, traffic sources, subscriber changes, and optional thumbnail impressions and click-through rates. The inventory may include channel videos uploaded outside Music Shorts.

How information is used

Media processing and model inference use the local setup. The application uses YouTube API Services to verify the connected channel, upload approved videos and metadata, check publication state and schedules, and perform approved thumbnail, caption, playlist and comment tasks. It can retry unfinished approved tasks while the local application is running.

The channel Performance page stores reports and observations locally. While the application runs and remains connected, its collector checks current counters approximately hourly and processed reports approximately every six hours. A separate per-project performance comparison is displayed on request without saving that response into project records.

Aggregate reports help the owner review his releases. The application does not identify individual viewers, train models on Google user data, sell personal data, or use Google data for advertising. Local creative suggestions use supplied media and lyrics, rather than YouTube viewer data.

Storage and sharing

Project files, authorization tokens, channel records and performance history are stored on the owner's computer. OAuth credentials and runtime records are excluded from the source repository. Videos, approved metadata and approved follow-up assets are sent to Google when the corresponding action is authorized. Google receives API requests needed for connection, delivery and performance reporting.

Google's handling of information is governed by the Google Privacy Policy. Uploaded videos and comments are subject to the visibility and platform settings selected by the owner. Local backups or exports made by the owner remain under the owner's control.

Retention, disconnect and deletion

Local projects and generated files remain until the owner deletes them. The project's Delete action removes the app's working copy; exported files in the song library and videos already on YouTube remain unchanged.

Hourly counter observations older than 30 days are removed during subsequent collection. Selected age checkpoints and saved reports can remain while the owner's authorization and video access continue to be checked. Successful collection refreshes the inventory and removes observations and report rows for inaccessible videos. A saved analytics cache whose last inventory check is over 30 days old is deleted before it is displayed again.

The local Privacy and YouTube data page requires explicit acceptance of this policy before using the application. It also offers Disconnect and delete Google data, with a separate confirmation. This attempts to revoke Google's authorization and removes saved credentials, channel information, downloaded analytics, YouTube identifiers and links, and delivery approvals from the app's working records. Songs, lyrics, artwork, rendered files and unused publishing drafts remain. A local deletion marker blocks further uploads from projects with completed or uncertain uploads to prevent duplicates after their delivery records have been removed. Published videos remain on YouTube.

A permanent authorization-refresh failure also stops access and schedules the same cleanup. Cleanup waits for active local work, persists unfinished requests, and retries while the application runs; it cannot run while the computer or app is stopped. Pending deletion is shown in the local interface and blocks further project changes and YouTube use until it finishes. Separate exports and backups made by the owner are not automatically deleted.

If revocation cannot reach Google, the application asks the owner to revoke access directly through Google Account connections. For deletion help or any unfinished cleanup, contact the operator below. Deleting local data or revoking access does not delete published YouTube content; manage that content in YouTube Studio.

Information website and browser storage

This public website contains static information pages hosted on a Hetzner server. It has no login, upload form, embedded video, tracking script or analytics cookies. The server processes connection information such as IP addresses and requested URLs to deliver pages; technical error logs may contain this information. The local application uses browser session cookies for its own interface and request protection.

Contact and changes

Operator: Daniel Ropot. Privacy questions and deletion requests: ropotdaniel@gmail.com.

This policy is updated when the application's data use changes. Its current version is available at this URL and from the local application. A versioned acceptance record is stored locally; a new policy version requires renewed acceptance.