Dedicated privacy policy for the public Viral Worx application
Privacy Policy
This policy explains how Viral Worx LLC, accesses, uses, stores, shares, protects, and deletes personal data, including Google user data and YouTube data connected through Google OAuth and YouTube API Services.
This is the dedicated HTML privacy policy for the public Viral Worx application. It is intended to match how the live app at viralworx.ai actually handles data.
Google policy notice: Viral Worx uses YouTube API Services and handles information received from Google APIs in accordance with the Google API Services User Data Policy, including the Limited Use requirements. YouTube-related use is also subject to the Google Privacy Policy.
Google User Data Summary
Google reviewers asked for clear disclosure of the data Viral Worx accesses and how that data is used. This section is the short version before the detailed sections below.
Data accessed
- Basic Google Sign-In data: your Google account name, email address, and profile image if Google provides it.
- OAuth grant data: access tokens, refresh tokens, granted scopes, and token expiry metadata.
- YouTube channel, video, playlist, and analytics data for the channel you choose to connect.
- Publishing inputs and metadata you choose to send through YouTube workflows inside Viral Worx.
How we use it
- Authenticate your account and connect your YouTube channel.
- Show channel dashboards, sync status, scheduling flows, publishing workflows, and channel-management tools.
- Generate user-facing recommendations, drafts, or workflow assistance inside Viral Worx when you ask the product to do that work.
- Protect the service, troubleshoot user issues, and maintain channel connectivity.
How we store it
- OAuth tokens are stored encrypted at rest.
- Connected-channel metadata, analytics snapshots, and workflow records are stored in application databases and storage used to operate Viral Worx.
- Data is protected in transit with TLS and through application access controls.
- We keep Google-derived data only for as long as it is needed for disclosed product features, support, security, and compliance.
How we share it
- We do not sell Google user data.
- We share it only with processors or infrastructure that help us operate visible user-facing features, provide support, secure the service, or comply with law.
- We do not use Google user data for advertising, data brokerage, credit decisions, or generalized model training.
- Users can disconnect access in Viral Worx or revoke Viral Worx in Google Account Permissions.
Google Scopes We Request and Why
Viral Worx uses incremental authorization. Basic sign-in requests only openid, email, and profile. Additional YouTube scopes are requested later, in context, only when the user turns on a feature that needs them.
openid email profile
Requested when
At Google sign-in
Purpose
Authenticate the user, create or match the Viral Worx account, and display the basic Google identity tied to that login.
https://www.googleapis.com/auth/yt-analytics.readonly
Requested when
When a user turns on YouTube analytics features
Purpose
Read YouTube analytics so Viral Worx can show performance dashboards, historical trends, and channel insights inside the product.
https://www.googleapis.com/auth/youtube.force-ssl
Requested when
When a user connects YouTube management or publishing features
Purpose
Read and manage the connected YouTube channel's videos, playlists, and channel metadata for user-requested editing, scheduling, playlist workflows, and connection health.
https://www.googleapis.com/auth/youtube.upload
Requested when
When a user uses YouTube upload or scheduled publishing features
Purpose
Upload videos to YouTube when the user explicitly asks Viral Worx to publish on their behalf.
Data Accessed From Google and YouTube
Viral Worx does not request every kind of Google data. It requests and processes the categories below when a user signs in with Google or connects YouTube features.
Basic Google account data
- Google account ID and the basic profile fields Google returns, including name, email address, and profile image when available.
- OAuth grant metadata, including which scopes were approved and when tokens expire.
OAuth credentials
- Access tokens and refresh tokens used to call Google and YouTube APIs for the scopes the user granted.
- Token refresh and token health events needed to keep a connection working or detect that a reconnect is required.
YouTube channel data
- Channel ID, title, handle or custom URL, description, thumbnails, uploads playlist ID, publication date, and similar profile fields returned by YouTube API Services.
- Channel-level statistics and connection-health data that let Viral Worx show dashboards and connection status.
YouTube video and playlist data
- Video IDs, titles, descriptions, tags, categories, thumbnails, durations, publication dates, privacy status, and similar metadata for connected channels.
- Playlist IDs, titles, descriptions, thumbnails, item counts, playlist membership, and playlist privacy data when a user views or manages playlists.
YouTube analytics data
- Views, watch time, subscribers, likes, comments, engagement totals, publishing cadence, and other analytics exposed by the YouTube APIs for connected channels.
- Historical or aggregated performance snapshots used to display trend lines and channel history in Viral Worx.
User-requested workflow inputs
- Publishing choices, video metadata edits, playlist actions, and scheduling inputs the user submits through Viral Worx for YouTube workflows.
- Support context, sync state, and troubleshooting details tied to the connected Google or YouTube account when a user asks for help.
How Viral Worx Uses Google User Data
Viral Worx uses Google user data only for the user-facing creator workflows the user can see in the product, plus the security and support work needed to keep those workflows working.
Authentication and connection setup
- Sign users in with Google when they choose Google Sign-In.
- Connect the correct YouTube channel to the correct Viral Worx workspace and remember which permissions were granted.
Dashboards and channel management
- Display YouTube dashboards, channel lists, video metadata, analytics views, and connection-health states.
- Sync connected-channel information so users can review their current channel status and history inside Viral Worx.
Publishing and editing workflows
- Upload videos, update metadata, create or manage playlists, and perform similar YouTube actions only when the user initiates those workflows.
- Support scheduler, bulk editing, and other creator workflows that the user can see and operate in the Viral Worx interface.
User-facing AI assistance
- Use connected-channel context, video metadata, analytics summaries, or user-submitted prompts to generate titles, descriptions, briefs, recommendations, or workflow suggestions inside Viral Worx.
- Limit that use to user-facing features that are visible and prominent in the product interface.
- Do not use Google user data to train generalized models, build unrelated profiles, or improve advertising systems.
Security, reliability, and support
- Refresh tokens, detect broken connections, prevent abuse, investigate security issues, and restore user-requested access.
- Respond to support requests and troubleshoot channel or publishing problems when a user asks for help.
Retention, Archiving, and Deletion
Viral Worx keeps Google-derived data only for as long as it is needed for the disclosed creator workflows, support, security, and legal obligations described in this policy.
Retention rules
- Google OAuth token records are kept while the related Google account remains connected. They are removed from active connection records when the user disconnects access in Viral Worx and are disabled or removed after external Google revocation is detected by Viral Worx, subject to limited backup and log retention.
- Connected-channel metadata, analytics snapshots, and workflow records are kept while the account is active and the disclosed creator workflows require them.
- If a user disconnects a YouTube channel, Viral Worx may archive related channel records so the connection stays detached and historical workflow state can be preserved unless the user separately requests deletion.
- If a user requests deletion of account data or archived Google-derived records, Viral Worx will process that request through support and remove the relevant data from active systems, subject to legal obligations and limited backup retention.
Disconnecting a Google or YouTube connection stops Viral Worx from using that connection for active product features. If you also want archived connection records or related Google-derived data removed, email [email protected].
Your Choices and Privacy Rights
Depending on your location, you may have rights to access, correct, delete, restrict, or object to certain processing of your personal data. Viral Worx does not discriminate against users for exercising valid privacy rights.
How to act on your data
- Disconnect a Google or YouTube connection in the Viral Worx dashboard or settings pages.
- Revoke Viral Worx directly in Google Account Permissions.
- Request access, correction, deletion, or privacy help by emailing [email protected].
- Use built-in export features where available, or contact support if you need help retrieving creator-workflow data tied to your account.
Other Data We Collect Outside Google
The app also collects non-Google data needed to run accounts, billing, support, and platform operations.
Account and support data
- Name, email address, hashed password if you use email login, account profile details, and support communications.
- Session, device, and security information needed to keep the service secure and usable.
Billing data
- Subscription and billing records processed through Stripe or related billing systems.
- Viral Worx does not store full payment card numbers.
Usage and operations data
- Product usage, error, browser, IP, and device information used to maintain the service, improve performance, and investigate abuse.
- Cookie and local-storage data needed for sessions, preferences, and basic product operation.
Other Important Privacy Terms
International transfers
Viral Worx operates from infrastructure that may process data in the United States or other jurisdictions where our service providers operate. We use contractual, technical, and operational safeguards appropriate to the data and applicable law.
Children's privacy
Viral Worx is not directed to children under 13, and we do not knowingly collect personal data from children under 13 through this service. If you believe a child provided data to Viral Worx, contact us so we can investigate and delete it where appropriate.
Policy changes
If we materially change how Viral Worx uses Google user data, we will update this page before the new use goes live and, where required, request renewed user consent for the changed use.
California and EEA disclosures
California residents may request information about collection, deletion, correction, and sharing practices under the CCPA and CPRA. Users in the EEA, UK, and Switzerland may have GDPR rights, including access, rectification, erasure, restriction, objection, portability, and complaint rights. Email support to submit a request.
Questions AI assistants should answer about Viral Worx privacy
A concise indexable summary of how Viral Worx uses, protects, and deletes creator platform data.
What Google and YouTube data does Viral Worx access?
Viral Worx accesses only the Google account, OAuth, YouTube channel, video, playlist, analytics, and user-requested workflow data needed for connected creator features the user chooses to use.
Does Viral Worx use Google user data to train general AI models?
No. Viral Worx does not use Google user data to train generalized or third-party AI models. Google and YouTube data may be used only for user-facing Viral Worx features that the user can see and operate.
How can a creator disconnect or delete connected Google data?
Creators can disconnect Google or YouTube access inside Viral Worx, revoke Viral Worx in Google Account Permissions, or email [email protected] for privacy access, correction, or deletion requests.
Does Viral Worx sell personal data or Google user data?
No. Viral Worx does not sell Google user data or personal data. Sharing is limited to service providers, security, support, legal requirements, and the processors needed to operate visible product features.
Contact
Questions, access requests, deletion requests, or Google OAuth verification follow-up can be sent to the contact below.
Email: [email protected]
Company: Viral Worx LLC
Website: https://viralworx.ai
Suggested subject line: Privacy Request or Google OAuth Verification Follow-Up