Privacy Policy
How ViralOnMe handles account, publishing, and connected platform data.
Updated November 11, 2026
About this document
ViralOnMe · Official domain: viralonme.com
Privacy and support contact: inirrabrand@gmail.com
1. Scope and operator
ViralOnMe is a creator workspace at https://viralonme.com. This policy describes the personal data we process when you sign in, plan content, connect social accounts, publish media, use automations, or review analytics. Contact us at inirrabrand@gmail.com for privacy questions or deletion requests.
2. Information we process
- Account information: name, email address, password hash when using email login, and profile photo when using Google sign-in.
- Workspace content: research queries, content plans, drafts, captions, carousel and Threads content, automation rules, uploaded videos, scheduling preferences, and publishing history.
- Connected-platform data: account identifiers and profile details, authorized access and refresh tokens, channel information, publication IDs, post status, and analytics or engagement data made available by the platform and the permissions you grant.
- Transaction and technical data: plan and order details, payment status from Midtrans, IP address, browser information, session cookies, and security logs. We do not store complete payment card numbers or CVV codes.
3. Google sign-in and YouTube access
Google sign-in requests basic identity information (openid, email, profile) to create and secure your ViralOnMe account. Connecting a YouTube channel is a separate, optional authorization. We request youtube.upload to upload videos you submit and youtube.readonly to identify the connected channel and check video status. You choose the title, description, visibility, audience setting, and whether to publish now or schedule within the available retention window.
We use the authorized channel data and tokens only to provide connection, upload, status, and related account features. We store the connected channel identifier and name, encrypted access and refresh tokens, token expiry, upload requests, video IDs, publication status, and related timestamps. Access tokens are refreshed when needed. We do not use Google or YouTube user data to train general-purpose AI models or sell it to data brokers or advertisers.
ViralOnMe uses information received from Google APIs in accordance with the Google API Services User Data Policy, including the Limited Use requirements. Google and YouTube user data is not used to train generalized AI or machine-learning models.
4. Other connected platforms
If you connect TikTok, Instagram, or Threads, we process the profile, media, insights, comments, messages, and publishing data permitted by the scopes you approve. We use these only for the features you choose, such as publishing, analytics, and creator-configured replies or direct messages. Available data and permissions depend on each platform.
- TikTok: account identifier, display name, avatar, public video metadata and engagement metrics, and video publishing permission when granted. Performance data helps show your own analytics and inform content ideas.
- Instagram and Meta: connected profile or Page identifiers, media and insights, comments and direct messages needed for your configured automation, and media you approve for publication.
- Threads: connected profile, post and reply data, insights, and content you approve for publication or reply management. You may disconnect each platform in Account settings.
5. How data is used and shared
We use data to operate accounts and subscriptions, save work, schedule and publish content, display history and insights, deliver requested automations, troubleshoot failures, and protect the service. Publishing sends the media and settings you approve to the selected platform. Payment details are processed by Midtrans. Hosting and infrastructure providers process data only as needed to operate the service. We do not sell personal data or share Google user data for advertising.
If you connect an external MCP client, including an AI assistant, and request YouTube tools, the client receives the requested connected-channel information, publication metadata, or tool results. Google OAuth tokens are not returned by these tools. The external client processes those results under its own terms and privacy policy. We do not automatically send your YouTube API data to our content-generation AI providers.
6. Data protection mechanisms, storage, and retention
We protect sensitive Google and YouTube user data, including OAuth credentials and connected-channel information, using the following mechanisms:
OAuth tokens are stored encrypted and transmitted over HTTPS. Staged video files are retained for up to seven days so scheduled publishing can complete. A file used for publication is retained for up to one day after upload, then is eligible for deletion. Publication records, account data, and technical logs may remain as needed to operate the service, investigate errors, meet legal obligations, or resolve disputes. Disconnecting an account removes its stored connection credentials; it does not delete a video already posted on the external platform.
YouTube channel details are checked and refreshed by our background worker daily. Connections whose channel data cannot be refreshed for 30 days are removed. Stored YouTube publication metadata is deleted 30 days after its publication request was created. These limits apply specifically to YouTube data; they override the general retention description above.
- Encryption in transit: the production website uses HTTPS, and our server communicates with Google OAuth and YouTube API endpoints over HTTPS to protect data while it is transmitted.
- Encryption at rest for OAuth credentials: connected-account access tokens and refresh tokens are encrypted using AES-256-GCM before being stored in our database. The server uses a secret from its server-side configuration to encrypt and decrypt these credentials.
- Access controls: user-facing requests for connected accounts and YouTube publications require authentication and are checked against the account owner. Token decryption and calls to Google APIs are performed on the server; Google OAuth tokens are not included in connected-account listings or YouTube MCP tool results.
- Account and session protection: passwords for email-based login are stored as bcrypt hashes rather than plaintext. Session cookies use HttpOnly and SameSite protections, with Secure cookies in production.
7. Your choices and deletion
You can disconnect a social account in Account settings and stop future access. You can also revoke Google access through your Google Account permissions. To request deletion of stored account or YouTube-related data, email inirrabrand@gmail.com. We will handle requests under applicable law and platform requirements. Removing data from ViralOnMe does not remove content already stored by YouTube, TikTok, or Meta; manage that content on the relevant platform.
Disconnecting YouTube attempts immediate token revocation with Google and deletes the local channel connection, staged video files, and YouTube publication records. If Google or storage is temporarily unavailable, the app reports a failure so you can retry. Our background worker also checks inactive connections daily and removes connection data when Google confirms that refresh authorization is invalid. You may request deletion of stored YouTube data by email; we delete the requested data as soon as possible and within seven calendar days. This does not delete videos on YouTube.
8. Third-party policies and updates
ViralOnMe uses YouTube API Services. Your use of YouTube is also governed by YouTube's Terms of Service and Google's Privacy Policy. We may update this policy when features or data practices change; the updated date above identifies the current version.
YouTube Terms of ServiceGoogle Privacy PolicyManage Google account permissions