Privacy policy

1. Operator and purpose

CosmicOtterGames operates this tool to manage preset creator comments on its own YouTube videos. It is not offered as a public service. Google account authorisation is provided by the channel operator; this website does not collect Google passwords or provide a sign-in form.

2. YouTube data the tool accesses

With the operator's authorisation, the tool uses YouTube API Services to read the authenticated channel ID and uploads playlist; upload and video IDs; video titles, descriptions, publication times, duration, visibility and processing/live status; and owner-visible video dimensions, rotation and aspect ratio where available. Upload-list or video responses can include information about non-public uploads; the tool selects eligible public videos for commenting.

It also reads comment-thread responses to check whether a top-level comment was authored by our channel. These responses can include other commenters' identifiers and comment content. The tool checks author channel IDs; it does not build commenter profiles or publish or retain other viewers' comment bodies as part of its posting records.

The tool uses OAuth client credentials and a refresh token to obtain temporary access tokens. Google receives these authorisation requests. Permission is used for channel/video checks and publishing the operator's preset comments, not for modifying videos or deleting viewers' comments.

3. How data is used

Data is used to identify an eligible owned video, distinguish the intended publishing format, select an operator-approved preset, check for an existing creator comment, and record the outcome of an authorised posting attempt. Presets are fixed text, not AI-generated. Google user data is not sold, used for advertising, or sent to an AI service by this tool.

4. Storage, access and retention

Credentials are stored separately in private GitHub Actions Secrets and processed in the automation's runtime. Temporary access tokens and fetched metadata are held in memory during execution. Selected public video IDs, timestamps, format/outcome information and proposed creator-comment text can appear in private execution logs and run summaries.

A private Git posting ledger stores channel/video IDs, reservation and outcome state, timestamps and a comment ID where available. It does not store OAuth credentials or comment bodies. These records prevent duplicate attempts, including after interrupted executions. Private reviewed manifests may also pin public target IDs, publication times and approved creator-comment text.

Execution logs follow the repository's configured retention settings. Ledger records and Git history do not have automatic expiry. The operator is responsible for reviewing retained API-derived data, refreshing or deleting it as required by YouTube's applicable policies, and handling revocation and deletion requests. Removed files may also need to be purged from Git history, workflow logs, artifacts and local copies; deleting only the current file is not necessarily sufficient.

Do not assume revoking Google access automatically erases stored records or public YouTube comments. Public comments remain on YouTube until removed there.

5. Service providers and this website

Google and YouTube process authentication requests, API requests and published comments under their own terms. GitHub hosts the private automation and its operational records, and GitHub Pages hosts this public website. These providers may process technical request information such as IP addresses and browser details under their own privacy policies.

This website has no advertising, analytics scripts, embedded media, account forms or application-set tracking cookies. Its public repository contains only the information pages and their styling, not the private automation source, tokens or posting records.

6. Revoking access and requesting deletion

The channel operator can stop the automation by disabling its workflows and can revoke Google access at Google account permissions. Revocation prevents further authorised API access once the credentials are no longer valid; it does not by itself delete previously stored files.

To request access to, correction of, or deletion of data held by this tool, contact CosmicOtterGames@gmail.com. Requests are handled by the operator, including identifying relevant ledger records, logs and retained copies and taking the action required by applicable YouTube data policies. Never email a password, OAuth secret or refresh token. Changes to a posting record require the automation to be stopped so removal cannot cause a duplicate attempt.

7. YouTube terms and Google policy

This tool uses YouTube API Services. Use of the tool is subject to the YouTube Terms of Service. Google's handling of data is described in the Google Privacy Policy. The YouTube API Services Developer Policies include requirements for stored API data, revocation and deletion.

If the tool's data practices change, this policy will be updated before the changed practices are introduced.