Human Player One Uploads

Privacy policy

Effective October 17, 2026. Operated by the owner of the Human, Player One channel. For questions, contact the operator using the support address shown in the Google authorization screen.

Information accessed and why

This private desktop tool uses YouTube API Services with upload and read-only permissions. It sends owner-selected video files and metadata to YouTube. It reads channel identity, the channel's upload list, video metadata, visibility, processing status and file details to confirm the destination, prevent duplicates and verify upload results. It does not request or store a Google password.

Storage and security

Authorization tokens and resumable-upload session details are encrypted using Windows current-user protection on the operator's computer. They are excluded from version control and website deployment. Production files and verification records are stored in the operator's workspace, which is within OneDrive and may be synchronized through the operator's Microsoft account. Locally encrypted credentials remain encrypted if synchronized.

Retention and deletion

The operator manually refreshes or deletes stored API-derived channel and video information within 30 days. This is an operator maintenance responsibility, not an automatic cleanup feature. Authorization credentials are kept while the connection is in use and are removed when the operator disconnects it. Original videos, scripts and owner-authored approval records are maintained separately as the owner's creative work.

To disconnect, revoke access through Google account permissions and remove the locally stored uploader credentials. To request removal of locally held API data or ask a privacy question, contact the operator using the support address shown in the Google authorization screen. The operator handles deletion requests and detected revocations within seven days. Removing local data does not delete videos already on YouTube; those are managed in YouTube Studio. Copies in service backups, synchronized storage or assistant conversations are managed through those services' controls.

Sharing and AI-assisted operation

Google receives the videos, metadata and API requests needed for uploads and checks. The operator uses OpenAI's Codex to help run the workflow; relevant channel identity, video identifiers and verification results may appear in the assistant conversation. Tokens and client secrets are not intentionally included in assistant output or public pages. Microsoft may process synchronized workspace files through OneDrive. Information received from Google APIs is not sold, used for advertising or provided by this tool to train a general-purpose AI model. Service providers process information under their applicable terms, privacy policies and account settings.

This website and email

These information pages contain no analytics, advertising, embedded videos, forms or application cookies. Hostinger serves the site and may process ordinary request information, including IP addresses, browser details and hosting logs. If you email the support address, the email providers process your message and reply address. Support correspondence is retained as needed to respond and then deleted within 90 days after resolution. Do not send passwords or authorization tokens.

Google policies

See the Google Privacy Policy. Use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.