OPTX
Log InSign In
ComplianceLast updated May 16, 2026

YouTube API Disclosure

optx.media uses Google Sign-In scopes for account authentication and YouTube Data API scopes only to connect authorized channels, read channel metadata, upload approved rendered videos, and support compliance/audit workflows.

optx.media uses YouTube API Services for authorized creator workflows and is not affiliated with, endorsed by, or sponsored by YouTube or Google.

Google Sign-In: openid

Used only during account sign-in to confirm the Google account identity.

Google Sign-In: email

Used only during account sign-in to identify or create the optx.media account.

Google Sign-In: profile

Used only during account sign-in to show basic account profile context.

YouTube channel connect: https://www.googleapis.com/auth/youtube.readonly

Used to read authorized channel metadata, including channel ID, title, handle, thumbnail, statistics, sync status, and diagnostics needed to show channel connection state.

YouTube channel connect: https://www.googleapis.com/auth/youtube.upload

Used to upload approved rendered MP4 files to connected channels through server-side execution after the user creates and approves a publish job.

Data stored

optx.media may store Google account identity context from account sign-in, YouTube channel IDs, channel titles, handles, thumbnails, retrieved channel statistics, granted scopes, encrypted refresh tokens, upload history, video IDs, video URLs, privacy/status values, and error/status metadata needed for user-facing workflow and compliance review.

Token handling

Refresh tokens are stored encrypted at rest, used only server-side, and never logged or exposed to the browser.

Upload behavior

Videos are created from user-uploaded source media and user-selected clip/render settings. Upload execution uses the approved clip metadata, visibility, scheduled time, and target channel from the publish job.

User control

Users control which YouTube channels are connected, which clips are approved, which publish jobs are locked, and when upload execution is requested. optx.media does not upload to disconnected, disabled, unavailable, reauth-needed, inferred suspended, or inferred closed channels.

Disconnect and deletion

Users can disconnect a YouTube channel to revoke or remove local refresh-token access and stop future publishing. In-app disconnect attempts server-side Google token revocation when a token exists, removes local token records, disables publishing, and blocks future unuploaded jobs for that channel. Users can also revoke Google access directly at https://security.google.com/settings/security/permissions and request data deletion at support@optx.media, subject to security, audit, and legal retention needs.