Privacy Policy

Last updated 2026-09-14

TubeAmplify is a YouTube growth toolkit. This page explains what data it collects and how it's used, in plain language.

TubeAmplify uses YouTube API Services. By using TubeAmplify you also agree to the YouTube Terms of Service, and Google's Privacy Policy describes how Google handles data on their side.

What we collect

Google account info: when you sign in with Google, we receive your name, email address, and profile picture.
YouTube data: read-only access to your channel's videos, view/like/comment counts, and YouTube Analytics history, via the scopes you grant during sign-in.
Extension usage: if you install the browser extension, it sends video IDs you're viewing on youtube.com and YouTube Studio to our backend to show tracked stats and AI suggestions.

What we never do

We never upload, edit, publish, or delete anything on your YouTube channel. Every AI-generated title, description, tag, or thumbnail is stored only as a draft inside TubeAmplify.
We never sell your data to third parties or use it for advertising.

How we use Google user data

TubeAmplify's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements.

In practice that means we use your YouTube data only to provide the analytics, scoring and optimisation features you can see in the product. We do not transfer it to anyone except as needed to provide those features (see third-party processing below), we do not use it for advertising, and no human at TubeAmplify reads your data except where you have explicitly asked us to for support, or where required by law.

Third-party processing

To generate AI suggestions, video titles/descriptions/tags are sent to Anthropic's Claude API for scoring. To generate thumbnail concepts, your existing thumbnail image is sent to Alibaba Cloud's Model Studio (DashScope) as a visual reference. These providers process the data to return a result; TubeAmplify does not otherwise share your content with them beyond that request.

How we store data

Your Google refresh token is encrypted at rest (AES-256-GCM) and used only to refresh read-only access on your behalf.
Your browser extension token is stored only as a one-way hash — we can verify it but can't recover the original value.
Login sessions use an encrypted cookie; no session data is stored server-side.

Your controls

You can disconnect TubeAmplify at any time from your Google Account permissions page, sign out from the dashboard, or regenerate/revoke your extension token from the dashboard settings panel.

Contact

Questions about this policy: fultonz@gmail.com.

← Back to TubeAmplify