1. Application and purpose
Pinky Friends Automation is a personal tool operated by the owner of the YouTube channel identified as UCqv8HKW7Oew6Pop_QU6yMvA (Iran Dot Cadastre). It is designed to generate educational English videos, store the resulting files in Google Drive, and upload and schedule the owner's videos through the official YouTube API.
The tool is intended for the channel operator. It does not offer Google account onboarding to website visitors or viewers of the videos. The direct Google connection is being configured; publication capabilities are checked before unattended publishing is enabled.
2. Google information accessed and its use
| Permission | What the application uses it for |
|---|---|
youtube.readonly | Verify the connected channel and read video identifiers, metadata, upload/processing status and publication status, including checks to prevent duplicate uploads. |
youtube.upload | Upload the operator's generated videos and specify their titles, descriptions, audience settings, privacy and scheduled publication time. |
drive.file | Create, read, update and organize specific video, script, caption and log files that this application creates or is authorized to use. |
The application processes OAuth credentials, channel and video identifiers, video metadata and status, generated media and captions, file identifiers, file checksums, schedule information and technical error records needed for this workflow. It does not request Gmail, contacts or unrestricted access to all Drive files.
Google user information accessed through these APIs is used for the publishing and backup workflow described here. It is not sold, used for advertising profiles or used to train general-purpose artificial intelligence models.
3. Storage, services and disclosure
Google stores the files in the operator's Drive and the uploaded videos on YouTube. The operator controls sharing and publication settings. A video becomes visible according to the visibility and schedule authorized by the operator.
GitHub Actions runs the application. Long-lived OAuth refresh credentials are stored in GitHub Actions Secrets. Access tokens and upload-session information are handled in memory during execution. The implementation is designed to keep token values out of source files, ordinary logs and generated artifacts.
A private GitHub repository stores the publishing ledger and operational metadata, such as video/file identifiers, hashes, times and processing results. Reports and related files can also be stored in the operator's Drive. These services process the information needed to provide the workflow; their own service and privacy terms also apply.
Retention
Videos, scripts, captions and Drive reports remain until the operator deletes them or a configured provider retention rule applies. GitHub ledger history and logs follow the operator's repository settings and GitHub's retention behavior. Temporary output artifacts are configured for three days of retention. Credentials remain in Secrets until removed or replaced; the owner can separately revoke Google's authorization. Deletion of one working copy does not automatically delete copies or history retained by another provider.
4. Access, revocation and deletion
The account owner can review or revoke the application's connection at Google Account → Third-party connections. Revoking access stops subsequent authorized API calls; it does not itself delete already uploaded videos, Drive files or GitHub records.
The operator can delete or change the visibility of videos in YouTube Studio, remove files from Drive, remove the application's Secrets, and delete operational data using the corresponding provider's controls. Repository history, logs and provider backups can have separate deletion and retention controls.
For support or questions about this application, use the operator support email displayed in the application's Google authorization details. This is a single-operator application; external users should not connect Google accounts to it.
5. Website visitors and children
These informational pages do not contain account-registration forms, payment forms, advertising pixels, third-party analytics or embedded video players. They do not intentionally request personal information from visitors. The hosting and network providers can process ordinary connection information to deliver and secure the pages.
The generated videos are intended to help children learn English. The operator tool itself is for the account owner and does not collect children's account information or viewer submissions. Watching content on YouTube is subject to YouTube's own terms and privacy practices.
6. Google API data use and changes
Use of information received from Google APIs will follow the Google API Services User Data Policy, including its Limited Use requirements. This policy will be updated if the application's data practices change. The date above identifies this version.