This page describes the data practices of the DMPGH Auto-Uploader, a private, personal-use automation tool built by Douglas Morse. This tool is not a public application and has no third-party users. It runs locally on the developer's own computer and is authorized to access only the developer's own Google/YouTube account via OAuth 2.0.
This tool uses YouTube API Services to upload the developer's own original videos to the developer's own YouTube channel (DMPGH), to post and manage comments on those videos, to update their titles and descriptions, and to read their public view counts. By using this tool, the developer (its only user) agrees to the YouTube Terms of Service and the Google Privacy Policy.
The tool does not collect, store, process, or share any data belonging to any other person or account. The only data it handles are: OAuth authorization tokens (stored locally on the developer's own machine) and basic public statistics (view counts) about the developer's own YouTube videos. No data is sold, shared with third parties, or used for advertising. No cookies or tracking technologies are used, and no data is disclosed to any external or internal party.
Stored authorized data is limited to OAuth tokens and self-owned video statistics, retained only as long as the tool remains in use. Any stored API data older than thirty days is deleted or refreshed. All stored data can be deleted at any time by removing the local token and data files from the developer's machine.
The tool's access to the Google/YouTube account can be revoked at any time via the Google security settings page at https://security.google.com/settings/security/permissions. Revoking access immediately invalidates the stored OAuth tokens.
Questions or deletion requests can be directed to claude@dmpgh.com.
See also: Terms of Service — DMPGH Auto-Uploader