Privacy policy

YouTube API Services — Edward Auto Reply

Edward Auto Reply is a private, owner-operated Python desktop application that uses YouTube API Services (YouTube Data API v3) to manage comments on the owner's channel. It is separate from this bookstore and does not provide public customer accounts. This disclosure describes the reviewed Python implementation as of October 28, 2026.

Information accessed and its purpose

The application retrieves the authorized channel's identity, comment text, author display names and channel identifiers, comment and thread identifiers, video identifiers, publication times, reply counts and existing replies. It matches configured keywords, prepares a local review queue, checks for existing channel-owner replies and records reply attempts to reduce duplicate responses. In the reviewed implementation, the operator approves queue entries and confirms a send command before predefined replies are posted.

Google authorization and sharing

Access uses Google's OAuth 2.0 authorization and an existing local token.json file. The reviewed script uses that authorization and attempts to refresh expired credentials; it does not itself implement the initial consent screen. The permissions granted are those shown by Google during the owner's authorization. No specific scope list is asserted here. Google account passwords should never be entered into this script or sent to bookstore support.

API requests and approved replies are sent to Google/YouTube. Posted replies become visible on YouTube according to YouTube's settings. The reviewed script does not transmit its comment database to this bookstore's payment or fulfillment systems, serve advertisements, or use browser cookies. Local exports and any device backups remain under the operator's control. Google's handling of information is described in the Google Privacy Policy.

Local storage, retention and deletion

The local replied.sqlite3 database stores comment candidates, identifiers, text, author information, keyword matches, queue and batch state, reply identifiers, timestamps and attempt results. Review CSV files contain selected comment information for operator approval. OAuth credentials remain in the separate local token file. The updated Python source includes cleanup of managed API records and exports older than 29 days, plus cleanup after confirmed authorization loss. These safeguards have not been verified as installed or running on the owner's Windows computer. Cleanup requires the updated application to run, including any separately configured maintenance task. Copies and backups outside its managed folder require manual deletion; local data is not application-level encrypted.

To remove local application data, stop the application and close programs using its database, then remove replied.sqlite3 and any associated -wal and -shm files, review_queue CSV exports and copies or backups under your control. Removing the database also removes duplicate-prevention history; review existing channel replies before using a new database. Remove token.json when disconnecting the application, and revoke Google's authorization separately as described below.

Revoke access or request deletion

The channel owner can revoke the application's Google account access through Google account security permissions. Google revocation alone does not erase local records. If installed and run, the updated script detects confirmed authorization loss and removes its managed API records and exports; until then, remove local records manually. Deleting local records does not delete comments or replies held by YouTube; manage those through YouTube's own tools.

For questions or requests to delete information held by the operator, contact dr.chung.edward@gmail.com and identify the relevant channel or comment without sending passwords or OAuth tokens. See also the Edward Auto Reply terms.