Ad Studio privacy policy

1. Information the Studio handles

When the operator connects a YouTube channel, Google provides authorization credentials and the Studio reads the channel's identifier and name. For videos uploaded through the Studio, it handles video identifiers, processing results, visibility and scheduled publication times.

The Studio also stores the video files the operator prepares, source references, transcripts, edit instructions, review results, titles, descriptions, posting schedules and job history. These records support editing, quality review, publishing and recovery of interrupted work.

The requested Google permissions are youtube.upload and youtube.readonly. Although the read-only permission permits access to YouTube account information, the current integration uses it to verify the channel and check uploaded videos. It does not request access to Gmail, Google Drive, contacts or calendars, and it does not receive the operator's Google password.

2. How information is used

Information is used to prepare and review videos, confirm the intended destination channel, upload approved files, set posting times, show processing and publication status, and prevent duplicate or incorrect uploads.

Google account data and credentials are not sold, used to build advertising audiences, or used to train generalized AI or machine-learning models. Publishing a PodGuard promotional video is separate from using the connected account's data to target advertisements.

3. Sharing and service providers

Google and YouTube receive authorized video uploads, titles, descriptions, requested visibility and posting times, as well as the requests needed to operate the connection. Their own privacy policies govern their handling of that information.

The Studio uses OpenAI's Codex service to assist with editing, copy and quality review. Relevant video frames, transcripts, source information, proposed edits and operator feedback may be sent for those tasks. Google authorization tokens and resumable upload credentials are kept out of model prompts and public Studio responses.

The operator may receive operational notifications through Telegram, such as completion messages, posting times and errors. The Studio does not intentionally include Google authorization credentials in those messages.

The operator's computers and service providers process information as needed to run these functions. Information may also be disclosed when required by law or necessary to investigate security incidents. This public site does not provide access to the private editing workspace or stored videos.

4. Storage and protection

Media and workflow records are stored on operator-controlled computers. Google authorization tokens and resumable upload credentials are stored in an owner-restricted private folder. Connections to Google's APIs use HTTPS. These measures reduce risk, but no storage or transmission system is completely secure.

Credentials remain while the connection is needed. The Studio's disconnect control removes its active local YouTube token and channel connection record. Revoking access in Google prevents further authorized requests, but does not automatically erase local files, job history or videos already uploaded to YouTube.

Drafts, source excerpts, review evidence and upload records may be retained for ongoing editing, troubleshooting and avoiding duplicate publication until the operator removes them. Temporary full-source files may be removed after verified excerpt creation or transfer. There is no general automatic deletion deadline for the retained workflow records.

5. Your controls and deletion requests

The authorized operator can disconnect the channel in the Studio and revoke access through Google Account connections. Videos already uploaded can be managed or deleted in YouTube Studio.

To ask about access, correction or deletion of Studio-held information, contact support@podguard.app. We may need to verify control of the relevant account before acting. Please do not send passwords or authorization tokens. Some records may need to be retained for legal or security purposes; where applicable, we will explain that limitation.

6. This informational website

These pages contain no sign-in form, advertising pixels, embedded videos or analytics scripts. The hosting provider may process standard web-request information, such as an IP address, browser details and requested page, to deliver and protect the site. Contact links open your own email application.

7. Google and YouTube policies

PodGuard Ad Studio'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. The Studio uses YouTube API Services. You can also read the Google Privacy Policy and YouTube Terms of Service.

8. Changes and contact

We will update this policy when the Studio's data handling changes and update the effective date above. Material changes to Google access will be disclosed before obtaining any additional consent required.

Questions: support@podguard.app. Operator: Colin O'Brien, PodGuard.