Privacy Policy

Last updated: 26.09.2026

This Privacy Policy explains how Megavid OÜ ("we", "us") collects and uses information when you use our website, Telegram-based workflow, and YouTube publishing features (together, the "Service"). The landing page itself does not ask for your name, email, or other personal details.

Information we collect through the Service

Depending on how you use megavid.io, we may process:

• Telegram account identifiers and profile information, language, time zone, delivery preferences, and messages needed to operate your megavid.io account;
• the content, captions, publishing choices, and instructions you submit;
• connection status, delivery status, timestamps, limited diagnostic logs, pseudonymous console-entry analytics, and masked recordings of interactions in the authenticated console; and
• the Google and YouTube information described below when you choose to connect a channel.

Google and YouTube user data

megavid.io uses YouTube API Services. When you choose to connect YouTube and grant permission on Google's consent screen, the Service may access the identifier and metadata of the YouTube channel you select and the authorization needed to upload videos that you approve. We do not receive your Google password.

The Google permissions requested by megavid.io are used as follows:

• youtube.readonly identifies and displays the selected YouTube channel;
• youtube.upload uploads a video only after you review its title, description, visibility, audience setting, and altered or synthetic content disclosure and explicitly approve publishing it.

We use this information only to provide user-facing megavid.io features:

• show and confirm which YouTube channel is connected;
• associate that channel with the correct megavid.io user;
• upload videos that you choose to publish through the Service; and
• report connection, upload, processing, and publishing status or errors.

Separately from the permissions you grant to connect and publish on your channel, we use an API key to read the public video identifier and public cumulative view count of videos published through megavid.io on YouTube. We check these known videos approximately once a day for up to 30 days after publication. We use the counts to determine whether an internal USD-denominated credit milestone has been reached and to help moderators review missing or disputed measurements. Users see credits for each video; detailed view statistics remain available to moderators and on YouTube Studio. This public-data check does not use your OAuth token or give us access to private YouTube analytics.

We do not sell Google or YouTube user data, use it for advertising, or use it to train generalized artificial intelligence or machine-learning models. megavid.io's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.

Sharing, transfer, and disclosure of Google user data

We share, transfer, or disclose Google and YouTube user data only with the recipients below and only as needed to provide the connection and publishing features you request:

• Post for Me, operated by Day Moon Development LLC. Acting as our OAuth connection and publishing service provider, Post for Me receives and stores the OAuth authorization, connected-account identifier, selected channel identifier and metadata, and publishing status. For a publishing request, megavid.io sends Post for Me a pseudonymous megavid.io user or assignment identifier, a time-limited video link, and the title, description, visibility, audience setting, and altered or synthetic content disclosure you approved. Post for Me processes this data to connect the selected channel, perform the requested upload, and return its status, errors, and resulting YouTube URL. It may also process the data to operate, secure, troubleshoot, meter, and improve its service, using the subprocessors described in its policy. You can review the Post for Me Privacy Policy.
• Cloudflare. Cloudflare hosts and secures our public website and provides domain and network services. It may process IP addresses, browser information, and website requests to deliver the site and protect it from abuse.
• Google Cloud. Google Cloud hosts our application and database. It processes account preferences, Telegram identifiers, the provider account identifier, selected YouTube channel mapping, connection and task status, publishing records, and limited diagnostic information on our behalf. Post for Me holds the Google OAuth access and refresh tokens; megavid.io does not store those tokens in its own database.
• PostHog Cloud EU. PostHog receives a pseudonymous megavid.io account identifier, whether the console entry used Google or Telegram, interface language, access and onboarding status, event time, and ordinary browser/request metadata so we can understand account entry and onboarding. After sign-in, we record console page views and when the page is left to measure visits and session duration; URL query parameters and fragments are removed from page URLs in analytics events. PostHog measures browser loading and interaction performance after sign-in. It also records masked console layout, clicks, scrolling, and navigation to help us find where users encounter problems. Text, input values, element attributes, images, video, and network requests are masked or omitted from these recordings. The sign-in screen and external Google authorization pages are not recorded. We do not send PostHog Google or Telegram credentials, Google email addresses, Telegram names or usernames, YouTube channel data, or user-submitted media. Console interaction autocapture remains disabled, and its analytics identifier is held in browser memory only. PostHog's current free plan retains recordings for one month. See the PostHog Privacy Notice.
• Telegram. The megavid.io bot sends the connected channel title, connection or publishing status, and resulting YouTube URL to your Telegram chat so that it can report the outcome to you.
• Google and YouTube. At your direction, we transmit the video and the title, description, visibility, audience setting, and altered or synthetic content disclosure you approved to YouTube for publication on the selected channel.
• Authorities. We may disclose data when required by applicable law or valid legal process.

Except as described above, we do not share, transfer, or disclose Google or YouTube user data to third parties. We do not sell or rent it, share it with advertisers, data brokers, or information resellers, use it for credit or lending decisions, or use it to train generalized artificial intelligence or machine-learning models.

Video preparation and storage

RunJob and its Puzl Cloud storage infrastructure process and store source media, prepared clips, captions, and rendering instructions on our behalf. AssemblyAI transcribes audio used to prepare clips. OpenAI helps select scenes and prepare creative material. These services process the material needed for those tasks; we do not send Google OAuth access or refresh tokens to them. This content preparation is separate from connecting your YouTube account and does not authorize an upload to your channel.

Storage, retention, and deletion

We retain account-to-channel mappings, publishing records, and diagnostic information only while needed to provide and secure the Service, comply with law, and resolve disputes. Post for Me stores the OAuth authorization on our behalf; megavid.io does not store Google OAuth access or refresh tokens in its own database. When you ask us to disconnect and delete your YouTube connection, we instruct Post for Me to revoke the authorization and delete the associated active connection and authorized Google or YouTube data as soon as possible and no later than seven calendar days. We may retain only minimal records that do not contain Google or YouTube user data when required for legal, security, or fraud-prevention purposes. Videos already uploaded to YouTube remain in your YouTube account until you remove them there.

Public view-count snapshots are replaced as new measurements arrive and deleted no later than 30 days after measurement. The queue that schedules checks is deleted after the tracking period. We keep awarded credit entries and review records without copying the raw view count into them, for account history, dispute resolution, and fraud prevention as described above.

Disconnecting YouTube and revoking access

You may ask us to disconnect or delete your YouTube connection by contacting support@megavid.io. You can also revoke megavid.io's Google access at any time from Google Account connections. Revocation prevents future API access but does not automatically delete a video that has already been published to your channel. You may request a copy, correction, or deletion of your personal information using the same contact.

YouTube terms and Google privacy

By using the YouTube features, you also agree to the YouTube Terms of Service. Google's handling of information is described in the Google Privacy Policy.

How we use your data for advertising

We run ads (including through Google Ads) to bring visitors to this page. To measure how those ads perform, we use cookies and local storage to record that you arrived from an ad. If you accept advertising cookies, we share that choice between megavid.io and app.megavid.io and send Google Ads a conversion when your onboarding is completed after connecting your first channel. The conversion event does not include your Megavid user ID, email, Telegram identity, or connected channel details. This helps us understand which ads lead to completed onboarding.

Third-party vendors, including Google

Third-party vendors, including Google, use cookies and device identifiers to serve and measure ads based on your past visits to this and other websites. Google uses this data to help us measure ad conversions and to show relevant ads. You can learn more about how Google uses information from sites that use its services at google.com/policies/technologies/partner-sites.

Cookies and device identifiers

We and our advertising partners may store and read cookies (such as Google's advertising cookies) and device identifiers on your device. These are only set for advertising and measurement after you accept cookies in our consent banner. If you reject, advertising and analytics storage stays disabled and only limited, cookieless signals may be sent.

Your choices and how to opt out

You can control or opt out of ad personalization in several ways:

• Use the Manage Cookies link at the bottom of our landing page to change your consent choice at any time.
• Adjust Google's ad settings at adssettings.google.com.
• Opt out of interest-based ads from participating vendors via the Network Advertising Initiative at optout.networkadvertising.org and the Digital Advertising Alliance at optout.aboutads.info.
• Use your device or browser controls to block or delete cookies and reset your advertising identifier.

Contact

Questions about this policy? Contact us at support@megavid.io.