LAST UPDATED · OCTOBER 21, 2026
Privacy policy
This policy covers this informational website and the owner-operated Dad Found Something production application. Aaron Hart is the operator. Contact: dadfoundsomething@gmail.com.
Website visitors
This site has no account registration, Google sign-in, contact form, advertising trackers, or analytics scripts added by the operator. GitHub Pages hosts the public pages and logs visitors' IP addresses for security purposes under GitHub's privacy statement. Following a social link takes you to another service governed by its own policies. If you email the operator, your address and message are used to respond to that inquiry.
The private production application
The application is for the operator's own production workflow, not a service accepting public account connections. It stores production briefs, scripts, storyboards, media, review decisions, and publication records on the operator's local computer. Authorized production can send selected briefs and media to configured AI providers; that is separate from access to Google account data.
Google and YouTube information
The application uses YouTube API Services. Google authorization requests youtube.readonly and youtube.upload. Read access is used to verify the intended channel and check uploaded videos' identity, title, description, processing state, visibility, and disclosure settings. Upload access is used to transmit the owner's approved video and publication metadata to YouTube.
The application keeps an OAuth refresh token, client connection details, and the selected channel ID in an owner-restricted local file. Access tokens are used for API requests. Local records include connection-check results, timestamps, approved publication metadata, and returned video IDs, URLs, and verification results. The application does not request Gmail or Google Drive access and does not collect Google passwords.
Use and sharing
Google authorization and API data are used only to provide the channel-connection, approved-upload, and publication-verification features described here. They are not sold, used for targeted advertising, or sent to AI providers to train general-purpose models. Authorization is sent to Google for authentication; approved video files and metadata are sent to YouTube for publication. They are not placed in this public website's repository. The operator can inspect local records to operate and troubleshoot the application.
Use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Google's handling of information is described in the Google Privacy Policy.
Storage and security
The private application runs locally. Credential files use owner-only filesystem permissions; they are not an encrypted credential vault. Production files and records remain on the operator's computer and any backups the operator makes. No security measure can guarantee absolute protection. The public website does not expose the application, its credentials, or its private media library.
Control, revocation, and deletion
The owner can disconnect the application at Google Account permissions. Revocation prevents further authorized access but does not itself erase local records or remove videos already published to YouTube. Videos can be managed separately in YouTube Studio.
To request deletion of information held by the operator, email dadfoundsomething@gmail.com. The operator will remove the associated stored Google authorization and API data within seven days of a verified deletion request or a detected revocation, including applicable local backup copies. Locally stored API metadata is reviewed and refreshed or removed within 30 days, subject to applicable YouTube API policy exceptions. These are operator-managed procedures, not an automatic deletion service. Original production assets supplied by the owner are separate from API-derived information.
Changes
This policy will be updated when data practices change. If Google account data would be used for a new purpose, the operator will provide an updated disclosure and obtain the required consent before that new use.