Until It’s True Publishing
Publishing privacy policy
This policy covers the application used by the Until It’s True channel operator for YouTube publishing and reporting. The website’s quiz and purchase privacy disclosure covers those separate services.
Information the application uses
The application uses Google authorization tokens; channel and video identifiers; titles, descriptions and other video metadata; upload and processing results; and identifiers and records for thumbnails, captions, playlists and comments. Comment verification can read comment text, author-channel information and thread identifiers. Authorized reporting reads channel and video metrics such as views, watch time and engagement.
The operator also provides video files, scripts, images, captions and publishing instructions. Google handles sign-in; the application does not receive the operator’s Google password. Access and refresh tokens permit unattended operation within the permissions granted by the operator.
Purpose and access
Information is used to identify the authorized channel, carry out approved publishing actions, report results, understand content performance, diagnose failures and recover interrupted work without duplicate uploads or comments. Authorized operators can review operational information through the publishing system and its connected support tools.
Storage and sharing
Publishing records are stored in the operator’s controlled local systems, including a database, automation history and logs. Credentials are stored in protected configuration. Encrypted recovery archives can contain copies of operational records.
YouTube receives the media and metadata needed to perform authorized actions. Selected publishing information, including video links, status and error summaries, can appear in Telegram operator notifications. Operator-authorized automation and support tools can process the information needed to investigate or carry out an operation.
This website is hosted through OpenAI Sites on Cloudflare infrastructure. Hosting providers process requests to deliver and secure the site. The local Google connection flow uses a short-lived protective browser cookie. The publishing information pages add no registration form, embedded player or advertising code. Email service providers process messages sent to our contact address.
Retention and deletion requests
Operational records and recovery copies are retained for publishing, troubleshooting and recovery. The current application does not automatically erase all copies across its database, automation history, notifications and backups when a Google connection is removed.
To request access, correction or deletion of information held for the publishing application, email hello@untilitstrue.com. The channel operator reviews the request, verifies its scope and handles the affected stores and recovery copies. Receipt of a request is separate from confirmation that deletion is complete. Deleting stored application information does not itself authorize deleting videos from YouTube.
Google authorization and your choices
You can revoke the application’s access using Google account permissions. Revocation prevents future use of that grant; it does not automatically delete previously stored information. The publishing worker and automation service maintain separate connections, which must each be considered when removing access.
The application uses YouTube API Services. Google’s handling of data is described in the Google Privacy Policy.
Contact and changes
Send privacy questions or complaints to hello@untilitstrue.com. Changes to the application’s data use will be reflected here. See the publishing terms and application overview.