Privacy and YouTube API data

Last updated: August 20, 2026.

Scope

This policy describes how Info Vault Studio handles data when the DELIGENDA operator connects a YouTube account through YouTube API Services. The public website itself does not require a YouTube account.

Data accessed

With operator authorization, the service may access the authorized YouTube channel identifier, upload a video, and read the uploaded video's processing, privacy, and channel state. OAuth authorization data is used only to perform the requested YouTube operations.

How data is used

YouTube API data is used only to identify the intended channel, deliver operator-authorized DELIGENDA videos, verify processing and visibility, prevent duplicate delivery, and support operator diagnostics. It is not sold and is not used for advertising.

Storage and protection

OAuth credentials and operational YouTube state are stored on the private production server with restricted filesystem permissions. Access tokens, refresh tokens, passwords, authorization headers, OAuth callback codes, and resumable upload session URIs are excluded from public diagnostics and application telemetry.

Retention and deletion

API-derived state is kept only while needed for delivery verification, operator control, duplicate-delivery protection, or an unresolved external operation. The authenticated operator can disconnect YouTube and request deletion of locally stored YouTube API data from the private control surface. Minimal non-API delivery fingerprints may be retained solely to prevent the same local media from being blindly uploaded again.

Revoking Google access

The operator can also revoke Info Vault Studio access from the Google account permissions page. Revocation prevents future authorized YouTube operations until the operator reconnects.

Third-party policies

The YouTube integration is subject to the YouTube Terms of Service and Google's Privacy Policy. This service uses YouTube API Services.

Privacy inquiries

Privacy inquiries may be sent using the operator/contact information displayed on the Info Vault Studio Google OAuth consent screen. No credential or token should ever be included in a support message.