Last updated: July 29, 2026
We collect the information needed to operate your TitleHook account:
The current channel scan uses public YouTube data. It can read public channel details, video titles, thumbnails, publish dates, durations, and view counts.
TitleHook does not currently connect to your Private YouTube Analytics. It cannot see impressions, click-through rate, traffic sources, audience retention, revenue, or private subscriber data. It also cannot change your channel or videos.
The current public scan does not collect video transcripts. We will update this policy before any transcript-storage feature is introduced.
When you ask chat about a specific published upload, TitleHook may temporarily read that upload's public description and a small sample of public comments to ground the answer. The raw fetched comment set is not added to your stored channel profile; the resulting chat answer remains in your conversation history.
If you explicitly use Scout's viewer-language research, TitleHook checks a small public-comment sample from up to four recent long-form uploads. Raw comments are processed transiently and are never saved. We retain only sanitized, repeated topic hypotheses for up to seven days; an empty result is cached for up to 24 hours. Disconnecting the channel or deleting your account removes those saved hypotheses.
We do not sell or rent personal data, use it for targeted advertising, or expose one customer's workspace to another customer.
Chat messages, video context, and the public channel data needed to answer a request may be sent to a processing service. Only the information needed for that request is included.
We do not use private account content to train unrelated services or to improve another customer's workspace. We do keep account history and limited operational records so your projects work, plan limits can be enforced, and failures or abuse can be investigated.
We do not use advertising or retargeting pixels. Browser tracking protection or an ad blocker can block analytics without preventing the core product from working. Clearing session cookies signs you out.
Account and workspace data is kept while your account is active so your channels, projects, conversations, and history remain available.
Removing a chat from your history hides it from your account, but TitleHook retains an internal copy of the transcript to review quality and improve the product. Internal transcripts are accessible only to the TitleHook team, and are purged when your account is deleted or on request to support@titlehook.com.
You can permanently delete your account from Settings (Security section) or by emailing support@titlehook.com from your account email. Deletion purges user-owned app data, including account details, conversations, channels, competitors, projects, Next Video decisions and their evidence records, generation history, saved items, and usage limits, and cancels an active subscription.
A small number of records may remain only in anonymized form or when required for security, fraud prevention, accounting, or legal obligations. Stripe may retain billing records under its own policies and legal duties.
Depending on where you live, you may have rights to access, correct, delete, restrict, object to processing, or receive a portable copy of your personal data. We do not sell personal information or use it for targeted advertising.
Email support@titlehook.com from the address linked to your account to make a privacy request. We may need to verify that the account belongs to you.
Questions about this policy or a privacy request? Email support@titlehook.com.
Plain answers about account data, channel analysis, sharing, and deletion.
We store account details such as your email, first name, profile image, sign-in method, plan, and account dates.
We also store workspace data you create or add, including public channels, conversations, projects, competitors, title history, saved items, preferences, request counts, and service errors.
No. TitleHook never sells, shares, licenses, or rents your personal data for advertising, marketing, data brokering, profiling, or analytics.
Operational services receive only what is needed to run the product: Stripe for billing, a processing service for chat requests, Google for sign-in and site analytics, and the public YouTube Data API for channels you add. Full card details never pass through TitleHook servers.
We do not integrate with ad networks, data brokers, social media tracking pixels, or retargeting systems.
Traffic is protected by HTTPS. Sign-in uses Google or a one-time email link, so TitleHook does not store account passwords.
Authenticated routes verify a signed session, admin routes require an allowlisted account, and abuse-prone endpoints use validation and rate limits.
Stripe hosts checkout and billing management.
Yes. Email support@titlehook.com from your account email to request deletion. We purge user-owned app data such as account details, conversations, channels, competitors, projects, generation history, saved items, preferences, and usage limits.
The flow attempts to cancel an active subscription. Operational records may remain only in anonymized or legally required form, including billing records retained by Stripe.
Deletion cannot be undone.
A session cookie keeps you logged in, short-lived cookies protect sign-in flows, and Google Analytics 4 measures basic site and feature usage.
You can block analytics with browser tracking protection or an ad blocker without preventing the core product from working. Clearing session cookies requires you to sign in again.
No advertising, retargeting, or social media cookies are ever set.
Depending on where you live, you may have rights to access, correct, delete, restrict, object to processing, or receive a portable copy of your personal data.
We do not sell personal information or use it for targeted advertising.
Contact support@titlehook.com from the address linked to your account. We may need to verify ownership.
Chat messages, video context, and the public channel data needed to answer may be sent to a processing service.
TitleHook keeps account history and limited operational records so projects work, limits can be enforced, and failures or abuse can be investigated. Private workspace content is not used to improve another customer's workspace.
No. The current channel scan uses public YouTube data and cannot see private impressions, click-through rate, traffic sources, audience retention, revenue, or private subscriber data.
The current public scan does not collect video transcripts. This policy will be updated before any transcript-storage feature is introduced.
When you ask chat about one of your specific published uploads, TitleHook may temporarily read its public description and a small public-comment sample to ground the answer. The raw fetched comment set is not stored in your channel profile; the resulting answer remains in your conversation history.