Your channel. Your access.
Privacy policy
This policy explains the personal desktop application, That Was Normal Publisher, operated by the owner of the THAT WAS NORMAL? channel. The application uses YouTube API Services to upload videos, manage owner-approved publication plans and read channel performance reports.
Information the app accesses
- Google authorization: access and refresh tokens issued after the owner grants permission. Google handles sign-in; the app does not collect the Google account password.
- Channel information: the connected channel's ID, title, handle and available channel statistics.
- Video information: video IDs, titles, links, visibility, publication schedules, audience declarations and upload or processing status.
- Performance reports: available video views, engaged views, watch time, average viewing duration and percentage, audience retention, likes, comments and shares as counts, subscribers gained or lost, traffic sources and aggregate country information. Empty or unavailable reports are recorded as unavailable rather than zero.
- Local publishing material: the video file, title, description, tags, audience declarations, publication plans and delivery records selected by the owner.
Basic permissions are youtube.upload and youtube.readonly. Enabling publication updates additionally requests youtube.force-ssl. Google's description of that permission includes seeing, editing and permanently deleting videos, ratings, comments and captions; this app uses it to apply approved video visibility and scheduling changes and has no deletion command. The app does not request Gmail, Google Drive, AdSense or monetary Analytics API access.
How information is used
The app identifies the chosen channel, uploads selected videos privately, prepares a publication plan for the owner's review and, when authorized, requests publication or a scheduled release. It reads YouTube's response to verify the actual result. Local records help prevent duplicate uploads and repeated publication attempts.
Performance reports help the owner understand viewing patterns and plan future videos. The app does not attempt to identify individual viewers from aggregate reports. It has no advertising, data-sale or AI model-training functionality. Google user data is used for the publishing and channel-analysis functions described here.
Storage and services involved
Google authorization tokens are stored on the owner's computer in a restricted local application folder. They are not part of this website or its hosted files.
Video files, delivery records, publication plans and channel performance reports are stored in the owner's project or application folders. Project folders may be synchronized by a storage service configured by the owner, including Google Drive. This is separate from the app's Google API permissions.
Selected videos, metadata and publication requests are sent to YouTube through the API. When the owner operates the app through an AI-assisted desktop service such as Codex, selected project information, performance reports and command outputs may also be processed by that service under its terms and account settings.
This informational website contains no account sign-in form, upload form, application database or analytics scripts added by the operator. Channel performance reports and authorization tokens are not published on this website. The hosting service may process ordinary connection and security logs, such as IP addresses and request information.
Retention and deletion
Authorization tokens remain on the owner's computer until replaced or removed; Google may also expire or revoke them. Local project files and delivery records remain until the owner deletes them. This version of the app does not automatically delete those local records.
The owner can remove the local token files and project records from their computer. If project folders are synchronized or backed up, copies and retention settings in those services should also be reviewed. Deleting a local record does not delete an uploaded YouTube video; video removal is managed separately in YouTube Studio.
For help with access, correction or deletion, contact the operator as described below.
Withdraw Google access
You can revoke the app's access at any time from Google Account connections. Find the app and remove its access. Revocation prevents continued authorized API use; it does not itself erase local project files or uploaded videos.
Google and YouTube policies
Use of YouTube features is also subject to the YouTube Terms of Service and Google Privacy Policy. The app's use and transfer of information received from Google APIs must follow the Google API Services User Data Policy, including its Limited Use requirements.
Contact and updates
For app and privacy questions, contact the channel owner using the support email displayed on the app's Google consent screen.
The operator will update this page if the app's permissions or data practices change. The date above identifies the latest version.