Effective date: 2026-09-27
Digital Dost Publisher privacy policy
Digital Dost Publisher is a private tool operated by the Digital Dost channel owner. It connects only the owner's authorized social accounts. It is not a service for collecting viewers' account information.
Data accessed and its purpose
Google OAuth permissions allow the tool to upload YouTube videos and view the authorized YouTube account. The implemented connection check reads channel identity information, including the channel ID, to confirm that the intended Digital Dost channel is connected.
The implemented publishing workflow uses owner-approved video files, titles, descriptions and visibility settings. A private YouTube API upload has been tested. Public YouTube API uploads remain disabled pending the YouTube API compliance audit and launch checks. Connecting an account does not approve a video for publication.
The tool does not request Gmail, Google Drive, contacts or payment permissions. OAuth authorization happens on Google's screens; the tool does not collect the owner's Google password.
Storage and sharing
OAuth credentials are stored in the private Digital Dost Publisher repository's GitHub Actions Secrets. The desktop OAuth client configuration is also retained in a restricted local configuration folder for the owner to reauthorize the app. Connection verification keeps access and refresh tokens in memory before transferring the required credential values to GitHub Secrets; it does not write those tokens into source code or transcript files.
The owner-selected destination channel identifier and non-secret setup settings are stored in the private project configuration. New publishing operations process YouTube API responses, returned video identifiers, processing status and visibility data in memory only, for the duration of that operation. These response fields are not written into new publication-journal records or execution reports. The journal retains local attempt/completion receipts, timestamps and fingerprints of owner-supplied content to prevent duplicate uploads. An interrupted operation requires an explicit recovery check; deleting API response data does not automatically permit another upload. Owner-supplied videos and publishing metadata are retained in the owner's local production library; selected publishing assets may be staged in the private publishing repository. Google/YouTube and GitHub process data needed for their respective authorization, storage and publishing functions. Local verification does not upload videos.
Google user data is not sold, used for advertising, shared with unrelated third parties, or used to train AI models. Access by the operator is limited to operating and maintaining the owner's publishing workflow.
Digital Dost Publisher's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
Retention and revocation
OAuth credentials and owner-selected destination settings are retained only while the authorized connection is needed. The operator checks authorization before accessing the channel. Local publishing receipts contain no returned YouTube video identifiers or cached video resources. Original videos and owner-authored metadata remain in the owner’s production library until the owner removes them. The owner can revoke Google access at Google Account connections, remove the repository's YouTube secrets, and delete the local OAuth client configuration and account records. Revoking access prevents future API access; it does not remove videos already on YouTube. Those videos can be managed in YouTube Studio.
Questions or deletion requests can be sent to digitaldostdaily@gmail.com. The operator will remove relevant stored account data under their control as soon as possible and within seven calendar days of a deletion request. Following revocation, the operator stops further access and removes remaining authorized API data as soon as possible and within 30 calendar days. This includes relevant repository history, retained workflow artifacts, logs and local copies; removing only the current file is not sufficient. Google may retain the videos and other platform data under its own policies. Deleting client data does not delete data held by YouTube.
Historical private-test API records created before the current memory-only response handling have been removed from active repository history, the verified local repository and the identified retained publishing workflow copies. GitHub may still retain unreferenced historical objects on its servers; provider-side removal remains unresolved. Public YouTube API publishing remains on hold while audit preparation is completed.
See Google's Privacy Policy and GitHub's Privacy Statement.
Updates
This policy must be updated before the tool starts using Google data in a materially different way. The owner must authorize any additional permissions before they are used.