Privacy Policy

Effective date: October 2, 2026 · Last updated: October 2, 2026

This Privacy Policy explains what information RepBeat Uploader ("the app", "we") accesses, stores and uses when it connects to a Google / YouTube account, and how that information can be deleted.

Summary. RepBeat Uploader is a private tool with a single user - its own developer. It only connects to YouTube channels owned by the developer. All data stays on the developer's own computer. Nothing is sold, shared, or used for advertising.

1. RepBeat Uploader uses YouTube API Services

RepBeat Uploader uses YouTube API Services (the YouTube Data API v3) to upload videos and set thumbnails on the owner's channels. By using RepBeat Uploader you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms). Google's handling of your data is described in the Google Privacy Policy (http://www.google.com/policies/privacy).

2. Who uses the app

RepBeat Uploader is not offered to the public. It has no sign-up, no customer accounts and no third-party users. The only person who authorizes it is the developer, and only for channels the developer owns. Before authorizing, the owner agrees to this Privacy Policy.

3. Google permissions (OAuth scopes) requested

Scope	Why it is needed
`https://www.googleapis.com/auth/youtube.upload`	Upload the owner's videos (`videos.insert`) and set their custom thumbnails (`thumbnails.set`).
`https://www.googleapis.com/auth/youtube.readonly`	Read the basic details (channel ID and title) of the authorized channel (`channels.list` with `mine=true`), so the owner can confirm the correct channel was connected.

4. Information the app accesses and stores

From Google / YouTube (API Data)

OAuth tokens (access token and refresh token) issued by Google after the owner signs in. They are stored in a local token file on the owner's PC so scheduled uploads can run.
Channel ID and channel title of the authorized channel, read once during authorization and shown in the local log.
Video IDs that YouTube returns for videos uploaded by the app, kept in a local history file so the owner can find each upload.

Sent to YouTube

The owner's own video files, thumbnails and metadata (title, description, tags, category, privacy status, "made for kids" status and the altered or synthetic content disclosure).

What the app does not access

It never asks for, sees or stores the owner's Google password.
It does not read other users' data, comments, subscribers, messages, watch history or analytics.
It does not access any data of third parties, because there are no third-party users.

5. How the information is used

The information above is used only to upload the owner's videos to the owner's channels and to keep a local record of those uploads. It is not used for advertising, profiling, analytics or any other purpose.

6. Where it is stored and how it is protected

All information is stored locally on the owner's personal Windows PC (the token file and a local history file inside the app's folder). RepBeat Uploader has no server and no database, and does not send this information anywhere except to Google's own API endpoints over HTTPS. The token file is excluded from source control and is never published or shared.

7. Sharing

RepBeat Uploader does not sell, rent, trade or share any user information or API Data with anyone - internal or external. The only party that receives data is Google/YouTube, when the owner's videos are uploaded.

8. Third-party content, advertising and cookies

RepBeat Uploader does not serve advertisements and does not allow third parties to serve content or ads. The app does not place or read cookies or similar technologies on any device or browser. This website is a static page hosted on GitHub Pages; it has no cookies, analytics or trackers of its own (GitHub may keep standard server logs as described in GitHub's privacy statement).

9. Retention and deletion

OAuth tokens are kept only while the channel is connected. They are deleted when the owner disconnects a channel or revokes access, and become unusable immediately after revocation.
Channel ID/title and video IDs are kept only as long as needed to operate the app and keep a record of uploads, and are deleted when a channel is disconnected or the app is removed.
The owner can delete all stored data at any time by deleting the app's token and history files (or the whole app folder) from the PC.

10. How to revoke access

In addition to deleting the local files, access can be revoked at any time from the Google security settings page: https://security.google.com/settings/security/permissions (also available at https://myaccount.google.com/permissions). Select "RepBeat Uploader" and choose "Remove access". After that, RepBeat Uploader can no longer access the account.

11. Children

RepBeat Uploader is not directed to children and does not knowingly collect information from children.

12. Changes to this policy

If this policy changes, the updated version will be published on this page with a new "Last updated" date.

13. Contact

Questions or complaints about these privacy practices can be sent to the developer:
Tohirbek (individual developer, Uzbekistan) · tohirbek.a.1997@gmail.com