Data & authorization
Privacy policy
Veo Backup Personal is a personal recording-backup tool, not a public service.
Effective November 16, 2026
Who operates this tool
The tool is operated for personal use by the owner of the mhayes1426 GitHub account. It runs on the owner's computers and personally operated server, including an Unraid installation. This policy covers the tool's handling of Google and YouTube data and this informational website.
Information accessed and permissions requested
The owner signs in through Google's OAuth authorization flow. The tool does not collect the owner's Google password. It requests these permissions:
youtube.upload: upload selected local video recordings to the authorized YouTube channel.youtube.force-ssl: list the owner's playlists, check playlist membership, assign uploaded videos to selected playlists, check channel access, and update recording dates. Google's consent screen describes this scope more broadly than these specific functions.
Data handled includes local video files; recording titles and dates; YouTube video IDs and links; playlist IDs, names, and membership; channel ID and title; upload status, retry and error information; and OAuth access and refresh tokens. Resumable upload URLs are also stored because they are needed to recover interrupted uploads.
How information is used
Data is used to maintain the owner's recording archive, upload selected videos, apply configured visibility and audience settings, assign playlists, update recording dates, display status, check authorization, and resume interrupted work. The tool does not use its Google permissions to read comments or delete YouTube videos.
Google data is not used for advertising, profiling, sale, or training machine-learning models. Its use is limited to operating this personal backup workflow. Veo Backup Personal's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Storage and security
Videos, the recording database, operational logs, and saved authorization files are stored on the owner's devices and server. Database backups can contain video and playlist identifiers and resumable upload URLs. OAuth token files are stored with restrictive file permissions and must be protected like passwords. The application communicates with Google APIs over HTTPS.
The public website does not receive or store OAuth tokens, local recordings, or the operational database. It contains no analytics scripts, advertising, account sign-in, or application cookies.
Sharing and third-party services
Selected video files and their upload metadata are sent to Google and YouTube at the owner's direction. A video configured as public becomes available to the public on YouTube. Its audience depends on the visibility and sharing settings applied to that video.
The tool does not sell Google user data or send it to a separate application-operator backend. Google processes uploaded data under its Privacy Policy, and use of YouTube is subject to the YouTube Terms of Service.
This informational website is hosted by GitHub Pages. GitHub may collect technical request information, including IP addresses, under the GitHub Privacy Statement.
Retention, revocation, and deletion
Local videos and operational records remain until the owner removes them; configured log rotation and database-backup retention may remove older copies. Uploaded videos remain on YouTube until removed there. Revoking authorization does not delete previously uploaded videos or local backups.
- Revoke Google access through Google Account third-party connections.
- Remove the local OAuth token file to stop the tool from using that saved authorization. Remove protected copies and backups as appropriate.
- Delete uploaded videos through YouTube Studio. Remove local recordings, database records, logs, and backups separately from the owner's storage when no longer needed.
Contact and policy updates
For questions about the tool or its data handling, contact its operator through the GitHub profile. This policy will be updated when the personal tool's data practices change, with the effective date shown above.