Privacy Policy — Creator Batch Publisher

1. Scope of this policy

Creator Batch Publisher runs on the owner's computer. It uses YouTube API Services only to verify the currently authorized channel and to upload a video after explicit local confirmation. This documentation website does not operate the client.

2. OAuth access requested

The client requests exactly these Google OAuth scopes:

https://www.googleapis.com/auth/youtube.upload
https://www.googleapis.com/auth/youtube.readonly

The upload scope starts a user-confirmed upload. Read-only access is used only for channels.list(mine=true) so the authenticated Channel ID can be compared in memory with the user's local routing configuration.

3. Data stored locally

OAuth tokens are stored locally in a per-channel file with mode 0600. Tokens are never uploaded to this website or to Vercel. The local ledger stores user-supplied titles, descriptions, privacy selections, channel aliases and configured Channel IDs, MP4/TXT paths, content hashes, and local safety state.

The authenticated Channel ID returned by YouTube is compared during the request and is not retained as separate API response data.

4. Remote API data and retention

DataRetention

OAuth tokenUntil revoke, invalid-token maintenance, or user deletion

Resumable session URIWhile incomplete, for no more than seven days

Remote video ID and URLMemory only after completion; printed once

Configured Channel ID and local inputsUntil the owner deletes local configuration or ledger data

A resumable session URI is cleared immediately after completion, revocation, or expiry. Remote video IDs and watch URLs are also cleared immediately after completion and are not shown by status. Daily local maintenance removes expired session data and detects a grant independently revoked through Google.

5. Errors, logs, and website hosting

The ledger stores fixed local error codes, never a Google or YouTube response body. The client does not send application logs to this site. Vercel may process ordinary request metadata in hosting logs as needed to deliver and secure these static pages. The site has no forms, analytics, advertising, account system, or embedded player.

6. Sharing and sale

Authorized API Data is not sold, rented, used for advertising, or transferred to data brokers. The local client sends only the data required for the user-requested YouTube API operation to Google.

7. Revocation and deletion

Revoke one channel from the local client with:

python -m pipeline.youtube_publish revoke <channel-alias>

This attempts programmatic OAuth revocation, deletes the local token, and clears locally retained API response data. Access can also be removed from Google's permissions page. Local deletion does not delete videos or other data held by YouTube; use YouTube Studio for that. Full instructions are on the Data Deletion page.

8. Policy acceptance and Google privacy

The local client requires versioned policy acceptance before OAuth, enqueue, or a confirmed upload. Visiting this website is not acceptance. Google's handling of information is governed by the Google Privacy Policy.

9. Security and support

Credential files use restrictive local permissions. Status and preview output exclude tokens and resumable session URIs. For privacy, revocation, or deletion support, use the public support contact in the footer. Requests are reviewed by the independent operator of the client.