Effective date: 2026-09-23
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 and basic channel details, to confirm that the intended Digital Dost channel is connected.
The planned publishing workflow uses video files and publishing metadata supplied by the owner, such as titles, descriptions and publication settings. Uploading and scheduling are currently disabled pending implementation and launch checks.
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.
Channel identifiers and non-secret setup records are stored in the private project configuration. 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
The owner retains account identifiers, credentials and publishing records while the connection is needed. 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 stored account data within their control when it is no longer needed or when deletion is requested. GitHub and Google may retain data according to their own policies and technical retention processes.
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.