Privacy notice · Private pilot

Privacy Notice for Abraham Olvera Content Automation

Last updated: 10 September 2026

This notice applies only to Abraham Olvera Content Automation, an owner-operated internal tool run by Abraham Olvera via TheAIGNC. It does not replace the website-wide policies for other TheAIGNC services.

Data the tool may handle

How it is used and stored

The tool uses the data above only to connect the owner’s YouTube channel, verify the intended channel or videos, and support an owner-approved upload workflow. OAuth credentials are stored locally in private, owner-readable files. We do not claim that this local storage is encrypted. Google passwords are not requested or stored.

OAuth uses Google’s HTTPS transport and a local loopback callback on the owner’s computer. The tool’s local device storage consists of those files and limited API data. Its API requests go directly to Google for the requested YouTube operation. These informational pages contain no app analytics, advertising, cookie-based tracking, or sign-in form. The website hosting and delivery providers process technical request information, such as IP addresses and requested pages, to serve and secure the website; visiting these pages does not connect a YouTube account.

Limited access and sharing

Abraham Olvera, as the human operator, may inspect the minimum non-secret channel and video metadata needed to verify the connection or a proposed upload. The owner’s AI-assisted development tools may also inspect that minimum non-secret metadata for verification. Tokens are never sent to model providers or to this public website.

The tool does not sell data, serve advertising, create advertising profiles, or use this API data for generalized model training.

The app’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. This is an operating commitment, not a claim that Google has verified or certified the app.

Public videos and Google

A video uploaded with public visibility can be available to the public through YouTube. Google’s handling of data is governed by the Google Privacy Policy. This tool’s use of YouTube API Services is also subject to the YouTube API Services Terms of Service.

Revocation and local deletion requests

The owner can revoke this tool’s Google access through Google Account permissions. Revoking Google access is separate from requesting deletion of locally stored data. For a manual local-deletion request, contact abrahamisaiolvera@gmail.com.

The manual, owner-operated procedure is to remove locally stored tokens and YouTube API data as soon as practicable, and within 7 calendar days after a revocation or deletion request. Locally stored YouTube API metadata is reviewed and refreshed or deleted within 30 days. This is a manual procedure, not an automated deletion daemon.

Tokens are retained only while needed for the authorized connection, subject to their expiry and the revocation/deletion procedure above. Questions or complaints about these practices can be sent to the same support address. Material changes to Google data use require an updated notice and renewed consent before the changed use begins.

Videos already uploaded to YouTube are governed by YouTube and are not removed from YouTube by deleting local data. Owner-supplied source assets are distinct from YouTube API data and are handled separately from this procedure.