Privacy and YouTube API data

Scope and consent

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. Before the private control surface starts a new Google authorization transaction, the operator must review and explicitly accept this Privacy Policy and the Terms of Service.

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, raw provider responses, and resumable upload session URIs are excluded from public diagnostics and application telemetry.

Disconnect, retention, and deletion

The authenticated operator can withdraw consent and disconnect YouTube from the private control surface. The disconnect action immediately blocks the stored credential from normal YouTube API use and asks Google's OAuth revocation endpoint to revoke the active authorization.

Locally stored YouTube Authorized Data used for upload, verification, visibility, and publishing authorization is deleted as soon as possible after that withdrawal and, in all cases, no later than seven calendar days after the operator withdraws consent. The control surface attempts that local deletion during the same disconnect operation even if Google's revocation response is ambiguous or unsuccessful.

If Google revocation cannot yet be confirmed, the encrypted OAuth credential may remain isolated only so the operator can explicitly retry Google's revocation request. While that resolution is pending, the credential cannot be used for normal YouTube API operations and a fresh authorization is blocked. This isolated credential is removed after a terminal revocation result.

Local deletion does not delete videos or other content already hosted by YouTube. Content already hosted by YouTube remains subject to the operator's controls on YouTube.

A minimal local delivery fingerprint containing only the local job identifier and canonical MP4 SHA-256 may be retained after deletion solely to prevent the same local media from being blindly uploaded again. This fingerprint contains no YouTube video ID, YouTube channel ID, OAuth token, provider response, title, or description.

Independently of a disconnect request, per-job YouTube API state is pruned on a bounded 28-day retention schedule.

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. The service periodically validates whether its stored authorization remains usable; when Google reports that the stored authorization is no longer valid, the service invalidates the local credential and triggers deletion of the related locally stored YouTube API data. This periodic validation and the bounded retention schedule are designed so externally revoked Authorized Data is deleted within 30 calendar days.

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.