Privacy Policy
ViralHook AI — Last updated: 2026-03-22
This policy describes how ViralHook AI (“we”, “the service”) handles information when you use
the ViralHook AI browser extension and our backend API
(hosted on Fly.io). By using the extension, you agree to this policy.
1. Single purpose
ViralHook AI is built to help YouTube creators inside YouTube Studio by
analyzing hooks/titles and, when you connect Google, showing retention-related
insights for the video you are working on.
2. What we collect
2.1 Extension (on your device)
-
Local storage (
chrome.storage.local): recent hook analysis
history (title, hook text, and analysis results you generated), UI preferences (e.g. active
tab, layout mode), and similar extension state. This stays on your device unless you send
data to our API as described below.
-
YouTube Studio page context: the extension may read the current
video ID from the URL and attempt to read the video title
field to reduce manual entry. It does not read your general browsing history on other sites.
2.2 Backend API (our servers)
-
Hook analysis requests: when you click analyze, we receive the fields you
submit (e.g. title, hook script, thumbnail text, video type, optional channel type). We use
this only to generate coaching output.
-
OpenAI: if configured on our servers, we may send portions of your submitted
text to OpenAI’s API to generate analysis. OpenAI processes that content under their terms.
-
Google sign-in & YouTube: if you choose “Connect YouTube”, we use
Google OAuth. We may receive basic profile identifiers (such as your Google account
sub and email) to associate stored credentials with your account. We store
OAuth tokens needed to call Google APIs on your behalf.
-
Extension session handoff: after Google sign-in, we may show a short
success page that passes a signed, short-lived token to the extension panel
so it can open a server session cookie in the extension context. The token expires within
minutes and is not stored long-term.
-
YouTube Analytics / Data API: with your authorization, we fetch video and
analytics data (e.g. duration, audience retention metrics) needed to show retention insights
in the extension.
-
Retention coaching requests: when you load retention, we may send your
current title and hook text along with analytics-derived metrics so we can generate optional
coaching text (including optional AI-assisted summaries if enabled server-side).
2.3 Technical / hosting data
Like most web services, our hosting provider and infrastructure may automatically process
technical data such as IP addresses, request timestamps, and error logs for
security and reliability. We do not use this to track you across unrelated websites.
3. What we do not do
- We do not sell your personal information.
- We do not load remote executable code into the extension; extension logic runs from the packaged files.
- We do not collect your general web browsing history outside YouTube Studio.
- We do not log keystrokes or mouse movements.
4. Legal bases & use
We process data to provide the service you request (analysis, OAuth, YouTube API calls) and to
secure and operate our systems.
5. Retention
OAuth tokens are stored on the server only as long as needed for you to remain connected and
to refresh access. Server logs may be retained for a limited period for security. Extension
local history remains on your device until you clear extension data or uninstall.
6. Your choices
- Disconnect: revoke the app’s access in your Google account settings if you no longer want us to use YouTube APIs.
- Clear local data: remove extension storage via Chrome extension settings or uninstall the extension.
7. Children
The service is not directed at children under 13 (or the minimum age in your jurisdiction).
8. Changes
We may update this policy from time to time. The “Last updated” date at the top will change
when we do.