Heard On Tape Uploader · Effective 30 September 2026
Heard On Tape Uploader ("the application") is a private, single-user publishing tool operated by Bobby Dionido ("the owner", "I") in Singapore. It has exactly one user: the owner himself. This policy explains what the application does with data it receives from Google APIs, in the plainest terms available.
The application serves one person — the owner of the Heard On Tape YouTube channel (@heardontape). There are no other users, no sign-up, no accounts, and no third parties whose data could be affected. No data belonging to any other person is accessed, requested or stored.
The application uses the YouTube Data API v3 with two OAuth scopes, and no others:
https://www.googleapis.com/auth/youtube.upload — to upload the owner's own
finished videos to the owner's own channel, to set their titles, descriptions and thumbnails, and
to set the video's scheduled publish time.https://www.googleapis.com/auth/youtube.readonly — to read back metadata and
processing/upload status for the owner's own videos, so the owner can confirm an upload landed and
is scheduled as intended.That is the complete list. The application does not request access to Gmail, Google Drive, Google Contacts, Google Calendar, Google Analytics, or any other Google service. It does not collect information about viewers, subscribers or any other YouTube user — no audience data, no analytics, no personal data of anyone but the owner.
Solely to publish the owner's own videos to the owner's own channel and to report back whether the upload succeeded. Concretely:
~/.hermes/youtube-token.json, readable only by the owner's own
user account (file mode 600). It is never transmitted anywhere except to Google, to
authenticate the owner's own API requests.None. Google user data is not shared with, transferred to, or disclosed to any third party for any purpose. There is no analytics processor, no marketing tool, no advertising network, no affiliate, and no service provider who receives any part of it. No human other than the owner ever sees it. No data is disclosed to law enforcement or anyone else except where the owner is legally compelled, and given that the only data involved is the owner's own public video metadata, this is not a meaningful possibility.
The application's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, the application limits its use of Google user data to providing and improving the single-user functionality described on this page, does not transfer that data to third parties except as necessary to provide that functionality (it does not, in fact, transfer it to anyone at all), does not use it for advertising, and does not allow humans to read it.
~/.hermes/youtube-token.json) removes the only stored credential. There is no remote
copy to request, because there is no remote system.The token is held in a permission-restricted file on a single machine that only the owner uses. Credentials are never printed into logs or transmitted in plain text. The application's requests to Google are made over TLS.
The application is not directed at children and has no users other than the owner. It does not knowingly access, collect or store information relating to children.
If the application's data practices change, this page will be updated and the effective date above revised. The practices described here will not be broadened without the owner's explicit decision to do so.
Questions about this policy or this application: bobbydionido@gmail.com