OPTX
Log InSign In
ComplianceLast updated May 16, 2026

Privacy Policy

optx.media stores the account, workspace, media, YouTube integration, publishing, notification, and audit data needed to operate a compliant creator workflow platform.

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

Contact and effective date

Effective date / last updated: May 16, 2026.

Privacy, data deletion, support, and abuse-prevention requests: support@optx.media.
API and Google/YouTube compliance contact: owner@optx.media.

Limited Use statement

Google API data is used only to provide and maintain user-facing optx.media features such as channel connection, channel diagnostics, publishing workflows, upload execution, upload history, compliance controls, and account support. Google API data is not sold, is not used for advertising or retargeting, is not used for credit scoring, and is not transferred except as necessary to provide or secure the service, comply with law or platform compliance requirements, or follow user direction.

Google and YouTube data categories

When authorized by a user, optx.media may process Google account ID, email, profile context, YouTube channel ID, channel title, handle, thumbnails, subscriber/view/video counts when retrieved, granted OAuth scopes, encrypted refresh tokens, upload/publish history, YouTube video IDs and URLs, privacy/status values, and error or diagnostic metadata returned by Google or YouTube APIs.

Application data categories

optx.media may process source media, rendered clips, music tracks, brand assets, metadata and templates, workspace data, team/user data, session cookies, Telegram notification metadata, upload history, audit logs, server logs, and operational status records needed to provide and secure the platform.

Data protection and security

We use administrative, technical, and organizational safeguards designed to protect Google user data and other sensitive data processed by optx.media.

Data transmitted between users, optx.media, and Google APIs is protected using HTTPS/TLS. Google OAuth tokens and YouTube channel access credentials are stored server-side and encrypted before storage. OAuth tokens, application secrets, and refresh tokens are not exposed in the browser or public user interface.

Access to Google user data is limited to the authenticated user, the user's workspace, and authorized optx.media personnel only when access is necessary for support, security, abuse prevention, troubleshooting, or compliance. Workspace access controls restrict users to their own workspaces, connected channels, uploaded media, publishing plans, and upload history.

We design logs and diagnostics so they do not include raw OAuth access tokens or refresh tokens. We use least-privilege handling, secure configuration, server-side storage controls, and operational access controls to reduce unauthorized access, disclosure, alteration, or loss of Google user data.

optx.media does not sell Google user data, does not use Google user data for advertising or retargeting, does not provide Google user data to data brokers or information resellers, does not use Google user data for credit or lending decisions, and does not use Google user data to train AI models. Google user data is used only to provide or improve user-facing optx.media functionality.

Users can disconnect YouTube access at any time through the product or by visiting the public Disconnect YouTube instructions. Users can request account and data deletion through the public Data Deletion instructions.

Token handling and security

YouTube refresh tokens are encrypted at rest, used only server-side, and never exposed to client-side code or public diagnostics. Access tokens are refreshed server-side when needed for channel sync or upload execution. Logs and audit records must not include token values, client secrets, Telegram bot tokens, encryption keys, passwords, or session cookies.

Retention, refresh, and deletion

Users can disconnect YouTube channels and request data deletion. We target a response or completion update within 7 calendar days where practical. Disconnecting a channel attempts server-side Google token revocation when a token exists, removes local token access, disables publishing for that channel, and prevents future scheduled jobs from executing. When deletion or revocation applies to Google/YouTube API data, optx.media will refresh, correct, revoke, or delete applicable local API-derived data within 30 calendar days where required and technically available. Audit, upload, security, legal, abuse-prevention, and compliance records may be retained where necessary.

Workspace archive and delete

Owners can archive workspaces to hide them from normal lists and block future publishing while preserving history. Owners can permanently delete a workspace with typed confirmation. Permanent delete removes workspace-owned operational records and local workspace-owned files where safe, but audit logs and redacted upload history summaries may be retained for security, abuse-prevention, legal, or YouTube API compliance review. Connected YouTube tokens must be revoked or locally removed before permanent workspace deletion can complete.

Infrastructure and processors

optx.media may use infrastructure providers for hosting/VPS, database, storage, background processing, server logs, and related security operations. If Telegram notifications are enabled, upload and workflow notification metadata may be delivered through Telegram Bot API. Providers receive only the data necessary for service operation, delivery, security, or compliance.

Google and YouTube disclaimer

optx.media is not affiliated with, endorsed by, or sponsored by YouTube or Google.