HookSignals Research

Extension privacy details

Effective October 9, 2026. This page describes HookSignals Research for Chrome and supplements the HookSignals privacy policy.

Automatic and selected public video research

Automatic research is enabled by default. On an active YouTube tab, the extension sends the current video ID and IDs from visible video cards to hooksignals.com to retrieve public metadata and statistics from the YouTube Data API. Card requests contain up to 20 IDs per batch, with at most 60 automatically checked cards per page visit. Successful public API reads also retain a shared, dated view-count observation at most once per half-hour slot per video for up to 30 days. These records contain the video/channel ID, publication time, duration, count and source time, without a browsing-account identifier. They also enter a shared public-video sampling queue when a video is inspected, together with up to 30 channel peers. Queue interest expires after 24 hours. A bounded scheduled collector samples up to 100 recent videos per run, at least 40 minutes between attempts, using the shared YouTube quota budget. Scheduling can be delayed; no continuous or complete coverage is promised. The collector does not extend interest. These observations support observed hourly pace and comparisons at similar publication ages when the required provider permission is active. Missing periods are not interpolated and expired observations are removed by scheduled maintenance. These IDs reveal which public videos are being researched. Full page URLs, search text, YouTube cookies, private watch-history records and activity on unrelated websites are not sent by automatic research. Manual Inspect and Compare send the IDs you select. Pause automatic research at any time in Settings.

Explicit topic searches

Clicking Search topic sends the topic you enter and your language and country choices to HookSignals and the YouTube Data API. Typing, opening Topics or loading a saved topic does not submit a search. This is separate from automatic page research, which does not send YouTube page search text. Search results contain up to 20 videos in API relevance order, not personalized ranking, search volume or a competition score.

The server caches result IDs, a request digest and the source time for 30-minute reuse. During an outage a dated search sample may be shown for up to 24 hours; expired records are excluded and removed during scheduled maintenance. The search cache does not store the query text. Selecting Save topic stores up to 20 of your own topics and choices in local extension storage, until you remove them or uninstall. They are not synchronized or searched in the background. Export creates a local CSV containing the query, available public values, API positions and source times. This feature does not call AI or spend HookSignals credits.

Explicit public comment research

Clicking Load comments or Load next 50 sends the inspected video ID, chosen ordering and, for later pages, a continuation token to HookSignals and the YouTube Data API. Opening the tools or filtering the loaded text makes no comment request. The service returns public top-level comment text, author display names, comment IDs, available like and reply counts, publication and edit dates, and a source check time. Reply text, private comments and moderation queues are excluded.

Up to ten pages, containing at most 500 comments, remain only in panel memory for up to 15 minutes. They are cleared on reload, account or inspected-video changes, and explicit Clear. Comment responses are not cached on the server or written to extension storage. The local text filter is not sent to the server. CSV export creates a local file with the filtered sample, comment and video links, and source times; that downloaded file remains under your control after panel data expires. This tool does not post comments, moderate discussion, send comment text to AI or spend HookSignals credits.

Local research and snapshots

Saved video IDs, your notes and save dates remain in Chrome's local extension storage. They are not synchronized to HookSignals or Chrome Sync. The extension retains at most 200 references and 100 cached video snapshots. Snapshot caches expire for normal use after 30 minutes and are not displayed after 24 hours. Expired cache entries are removed during extension use and browser startup. Your notes remain until you remove them or uninstall the extension. Saved references can include a dated title, channel name and thumbnail URL; these API details are refreshed on inspection or removed after 30 days during extension use.

Local channel watchlist

You can explicitly follow up to 10 channels using your own labels. Opening or refreshing a followed video can record public observations for that video and up to seven recent channel uploads. Each video keeps up to 24 distinct, dated API observations for no more than 30 days. Expired observations are excluded and pruned when the extension runs. Refresh channel sends that channel's public ID to HookSignals to request its recent uploads, even if the original video is unavailable. Your labels and stored observation history are not uploaded or synchronized. Stop following a channel to delete its local history. This is not scheduled background monitoring.

Optional account watchlist

Account daily tracking is separate from the device-only list. A separate permission on the connection screen lets the extension read and manage up to five channels in your HookSignals account. Only an explicit Follow action saves that channel ID in your account; local follows and notes are never migrated automatically. The existing server schedule collects public YouTube observations while your browser is closed. Collection is bounded by shared quota and may be delayed; the interface shows observation dates and unavailable data. It does not access private YouTube Analytics or spend AI credits.

Account follows remain until you unfollow in the extension or website dashboard. Disconnecting or uninstalling the extension revokes/removes extension access but does not stop those account subscriptions. Public daily snapshots are shared across accounts following the same channel, read for up to 30 days and removed after expiry by scheduled maintenance. Removing a follow does not delete shared public observations needed by other accounts. The extension keeps its loaded account list in panel memory only; account changes clear it. Older records without a provider timestamp are labeled accordingly.

The updates feed compares sourced observations collected after you followed. It reports newly published videos and observed title changes, not the exact moment a title was edited. Daily samples include up to 50 videos per channel and can miss changes between checks. When you mark updates read, HookSignals stores the per-channel observation timestamps under a hashed account key for up to 30 days after your last read action. Read status is shared across your connected extension sessions. An unfollow followed by a new subscription has a separate read state.

Optional desktop notifications

Notifications are off by default. Enabling them in Settings requests Chrome's optional notification permission and requires account tracking access. While Chrome is running and that browser-session connection remains valid, an alarm reads the existing updates feed about every 30 minutes. It does not start an extra YouTube collection, generate AI output or spend credits. Sleep, daily collection and outages can delay updates; this is not an instant alert guarantee.

Browser-session storage holds activation state, a hash binding it to the current connection, per-follow observation timestamps and check times. It stores no notification copy of video titles or channel metadata. Existing observations are the starting point when enabled. A generic desktop summary opens the extension's updates view and never marks account updates read. Ambiguous desktop delivery is not retried for the same observation to avoid duplicate alerts; the feed remains available. Turning notifications off clears their alarm and requests removal of the optional permission. Reconnecting, account or permission changes, and browser-session expiry stop alerts. Enable them again for the new session if desired. Server channel subscriptions continue until you unfollow separately.

Local packaging preview

Clicking Use paused YouTube frame copies only the paused watch player's video pixels into the selected local A/B draft. The extension checks the active tab and video again before accepting the frame. Ads, playing videos and browser-protected pixels are refused; no screenshot of the surrounding page is taken. Captured images are not sent to HookSignals, YouTube or an AI provider. Saving drafts or library copies keeps these pixels under the same local storage and deletion rules as images you select from files.

The separate thumbnail library stores up to 20 named copies and 64 MiB of image data in local IndexedDB. Each copy keeps your title, image, original editing source and applied settings. It is not synchronized or uploaded. Opening a library copy changes only the chosen preview; saving the A/B workspace is a separate action. Deleting the working A/B draft does not delete these named copies. Delete library copies separately or uninstall the extension to remove their local storage. Explicit editable JSON backups contain those image pixels, title and settings; downloaded files stay under your control. Import validates the images and adds a new copy only after your confirmation, without replacing existing records. Unapplied editing changes are excluded.

An image selected under Tools → Title & thumbnail is decoded in this panel. Images are not uploaded. Choosing Save drafts stores both title and image drafts in this extension's local IndexedDB so they survive closing the panel or browser. Unsaved edits are lost on close. Delete saved drafts removes the saved titles and images from this device. Clicking Continue in Thumbnail Tester sends that title to the website in the link. Website tools have their own upload and credit rules.

Publishing checklist and Studio

The Studio content script displays a draft-review button. Only after you click it does it read the visible title and description editor into a local browser-session handoff. The panel consumes that handoff. These texts are not sent by the import or local checklist. The checklist uses your own draft text, not private analytics or estimated keyword demand. You may explicitly save a publishing draft in local IndexedDB or delete its saved copy. A separate local library holds up to 40 named publishing drafts. You can search, open, update or delete individual copies and download a JSON backup containing only your draft name, title, description, topic and tags. Selecting a backup previews it; a separate import action adds new copies without replacing existing records. These library operations do not upload text or synchronize it with your account. Opening a library copy changes only the local editor. Separate Apply title and Apply description actions can update the selected visible field on an existing video's Details page. The reviewed field text, video, tab and page must still match. Description handoff supports plain text, paragraphs and URL text; richly formatted descriptions are left unchanged to preserve formatting. Each field supports one guarded undo, including an explicitly cleared description. The reviewed text and undo values stay in a browser-session record that is valid for 30 minutes. Expired targets cannot be applied and are removed on the next context read or extension worker startup. Upload dialogs are excluded. Review the change and press Save in Studio yourself; the extension does not save or publish videos.

Optional AI title and description generation

AI title and description generation requires a separate account permission and an explicit Generate click showing the credit cost. That action sends the title, description, topic and chosen language from your publishing draft to HookSignals and OpenAI. It does not send thumbnail images, cookies or your other saved research. Draft text is not copied to our analytics tracing service. HookSignals stores a request identifier, input digest and generated titles or descriptions for up to seven days so an interrupted response can be recovered without generating again. Expired output is excluded immediately and deleted by scheduled maintenance. Credit reservation and settlement records remain part of account transaction records. The extension keeps the last request identifier for each tool on this device; it retrieves results only for the connected account. Status checks never generate content or spend credits. Suggestions require your review and are not measured CTR, search volume or future-performance predictions.

Optional creator coach

Coaching has its own account permission and requires an explicit Ask click after accepting the displayed credit cost. It sends your own title, factual notes, topic, goal, intended audience, question and the last three question-and-answer exchanges to HookSignals and OpenAI. It does not automatically attach channel Analytics, research snapshots, comments, transcripts or video content. Your notes, pending request and latest ten answers are stored in this device's local IndexedDB; exporting the conversation downloads that local copy. Account-scoped generated answers can be recovered from HookSignals for seven days. Deleting the local conversation does not cancel a server request or pending credit reservation. Advice requires your review.

Optional source-based coaching

Source-based coaching is separately controlled and may be unavailable. It requires both the coaching and public-source permissions; existing coach access does not enable it. You select up to three current or saved video IDs and explicitly request a preview. Saved research notes are not attached. HookSignals obtains public video titles, descriptions, publication dates, duration, raw video counts and channel statistics through the YouTube Data API. The account-bound preview expires 30 minutes after its oldest source observation and is removed by scheduled maintenance. Previewing alone does not call OpenAI or spend AI credits.

Only an explicit source question, after confirming that preview and its displayed credit cost, sends those public facts, your creator plan and question, and up to three unexpired source exchanges to HookSignals and OpenAI. Private Analytics, comment samples, transcripts, uploaded images and other saved research notes are excluded. Tracing is disabled. Source questions and answers use a separate account-specific local IndexedDB record, containing at most ten answers, their source IDs and observation times, retention deadlines and a pending receipt-based request. The pending input contains your text and receipt identifiers, not a copy of public source snapshots. Pending recovery records expire after seven days; source answers expire no later than 30 days after the oldest source observation. Startup, reading the conversation and local maintenance in an open panel remove expired output while preserving your authored notes. A closed browser performs cleanup on its next startup or access. Server answers are recoverable for seven days.

Export downloads the unexpired local conversation; downloaded copies remain under your control. Deleting local records does not cancel a server request or refund a credit reservation. A missing response is recovered through a status read, without another model generation. Advice is generated from dated public facts and requires your review; it does not establish that the model watched a video or knows its private performance.

Optional AI thumbnail concepts

Image generation has a separate account permission and requires an explicit Generate click after accepting the maximum displayed credit cost. It sends only your own idea, optional overlay text and selected style to HookSignals and OpenAI. Your existing image files and saved research are not uploaded by this action. HookSignals stores generated JPEGs and their verified result metadata with access restricted to your account for seven days. A server-side status record contains an input digest, timestamps and processing state, without the prompt, image pixels or credentials. The validated creative input is used in memory for the generation operation.

The extension saves your own idea and pending request locally before sending it. Status checks never start another generation or spend credits. Opening a private generated image requires an explicit load action; applying it to A or B and saving the draft keeps that JPEG on this device for local editing. Clearing the local generation record does not cancel server processing, refund a pending reservation or remove saved A/B drafts. The first free set is shared with the website; subsequent sets cost up to 20 credits, proportionally charged for valid partial results. Confirmed charges and uncertain outcomes are shown separately. Generated concepts are not audience experiments or CTR predictions.

Optional account connection

Connecting uses your existing HookSignals account. A one-time code and PKCE verifier establish a token scoped to reading public research data, plus AI title and description generation, creator coaching, separately confirmed public-source coaching, thumbnail generation, account watchlist management or private Analytics reading only if you separately enable those permissions on the connection screen. Old research-only tokens cannot read account watchlists or spend AI credits. The token is stored in Chrome session storage, is not exposed to page scripts, and expires after at most 7 days. The server stores a hash of the token, the account identifier, scope and expiry. Disconnecting revokes that token. This connection cannot edit YouTube channels or change billing. Private Analytics requires its own scope and a separate Google channel authorization described below.

Optional private YouTube Analytics

This feature is available only when enabled by the service. Connecting a Google channel requires explicit Google consent for youtube.readonly and yt-analytics.readonly. The extension also requires a separate Analytics reading permission on the HookSignals connection screen. These permissions read your authorized channel identity and activity; they do not edit videos or access monetary reports.

The server encrypts Google access and refresh tokens and channel identity with an account-bound encryption key. Connection records expire after 30 days; one-time consent state expires after 10 minutes. Expired records are excluded immediately and removed in scheduled maintenance. Reports are fetched only after you click Read private report or Read current video's retention. The latter sends the active YouTube/Studio video ID and selected period to HookSignals and Google; the server checks that the video belongs to your connected channel. Report rows are not saved on the server or in extension storage; the isolated extension panel holds them in memory for up to 15 minutes, clears them on account change and loses them on reload. They are not sent to AI, advertising services or website analytics. The website connection page receives connection status only, without channel identity or report rows.

Disconnecting the extension does not revoke Google authorization. Use the Google channel connection page to request revocation. A failed revocation disables report reading and remains available for retry. Expiry of the application connection does not revoke Google's grant. You can also remove HookSignals directly in your Google account connections. Thumbnail impressions, CTR and revenue are not included. Optional video retention reports display Google's audience watch ratio and relative retention performance for returned video segments. Missing days or segments are not estimated or filled with zero. Repeated viewing may produce an audience watch ratio above 100%.

The server excludes public snapshots older than 24 hours and removes them in scheduled maintenance. Expired connection records are also removed during that maintenance. Cleanup runs with the research-data refresh job; expiry checks still apply when a scheduled job is delayed.

Service providers and operational data

Vercel hosts the HookSignals service, Supabase stores public snapshots and connection records, as well as account-scoped AI results and status records. Clerk handles the optional HookSignals sign-in. OpenAI processes the explicitly submitted creator text for writing, coaching or thumbnail concepts, and the public source facts you explicitly confirm for source-based coaching, and generates the requested output. Google provides the YouTube Data API, the optional YouTube Analytics API and public thumbnail images. The server receives the network information necessary to answer requests, including an IP address; the application hashes it for rate-limit keys. Public thumbnails load from YouTube image servers, which receive the ordinary network request. The extension contains no advertising or analytics SDK and does not sell personal data.

Permissions

Storage keeps your local research and session connection. Side panel displays the research interface. Identity opens the secure HookSignals connection flow. Alarms schedule optional update checks after you enable notifications; the notifications permission is requested separately on that click. Access to hooksignals.com makes the API requests. A content script on YouTube shows public metrics on the current video and visible cards, and extracts video IDs from links. No access to all websites, downloads history, private cookies or channel editing is requested.

Your choices

You can use public lookups without connecting an account, disconnect in Settings, pause automatic research, clear snapshot caches, export your notes, remove individual references or uninstall the extension. Contact support@hooksignals.com for questions or account data requests.

YouTube

The extension uses YouTube API Services. YouTube data remains subject to the YouTube Terms of Service and Google Privacy Policy. HookSignals is independent and is not endorsed by YouTube or Google.

HookSignals' use of information received from Google APIs follows the Chrome Web Store User Data Policy, including its Limited Use requirements. That information is used to provide the requested research features and protect the service, and is not used for personalized advertising.