HookScore Privacy Policy

Last updated: May 6, 2026

This policy explains what HookScore collects and processes when you create an account, use a free guest check, or ask the app to score a short-form video hook.

Information We Collect

Account and Supabase auth data

HookScore uses Supabase for authentication. When you register or log in, Supabase processes your email address, password authentication data, Supabase user identifier, session identifiers, and the name you provide during registration. HookScore uses that information to create your account, keep you signed in, and associate saved hook checks with your account.

Hook check content

When you score a hook, HookScore processes the text and context you enter, including the hook text, video description, target audience, niche, selected goals, selected output language, and score results returned by the analyzer.

Microphone dictation

HookScore can use your microphone only when you choose the Dictate action in a text field. Microphone input is used to turn speech into editable hook text through the device speech-recognition service. HookScore receives the resulting transcript and does not store raw microphone audio from dictation.

Selected video, frame, and audio processing

Adding a video is optional. If you select a video, HookScore samples the opening window you choose, currently three to five seconds. The app extracts still frames from that opening window and sends those image samples to the configured AI provider. On web builds, if the configured provider supports audio input, the app may also extract a short WAV audio sample from the same opening window and send it to that provider.

HookScore stores video metadata for authenticated history, such as filename, MIME type, local source URI, selected opening window, preparation time, and duration. HookScore does not store the raw selected video file, extracted frame images, or extracted audio samples in its Supabase history tables.

Usage and history storage

For authenticated users, HookScore stores daily usage counts and saved hook history in Supabase. Saved history includes the analysis result, score, goals, model metadata, hook context, selected clip metadata, and timestamps. Guest checks are not saved to account history.

Result reports

If you report an AI-generated hook result from inside the app, HookScore stores the reported result identifier, the result content, report reason, timestamp, and, when available, your account identifier and email address. HookScore uses these reports to review analyzer quality, safety, and policy compliance.

Guest device UUID

If you use the free guest check, HookScore creates a random device UUID and stores it locally on your device. On web, it is stored in browser local storage. On native builds, it is stored in secure device storage. Supabase stores that UUID with guest usage count, first seen time, and last used time so HookScore can enforce the guest check limit.

AI Provider Usage

HookScore can be configured to use Google Gemini or OpenAI. Depending on the build, the app sends analyzer requests either directly to the configured provider or through a Supabase Edge Function that calls the provider with server-side credentials. The selected provider receives the hook text and context you enter, sampled frames from an optional selected video, and, when supported and available, a short audio sample from the selected opening window. The provider returns structured analysis, scores, observations, and rewrite suggestions.

AI provider processing is governed by the provider's own terms and privacy practices. HookScore sends only the information needed to generate the hook score.

How We Use Information

Authenticate accounts and keep sessions active.
Generate hook scores, observations, and rewrite suggestions.
Show saved history for authenticated accounts.
Apply authenticated daily limits, guest limits, and promo-code usage.
Review reported AI-generated results and improve safety controls.
Debug service reliability and protect against misuse.

Retention and Deletion

Authenticated hook history and daily usage records are retained while your account remains active, unless you ask for deletion. Guest UUID usage records are retained as needed to enforce the one-time guest check limit. Local guest UUID storage remains on your device until you clear app data, clear browser storage, or request deletion where HookScore can match the UUID.

You can delete your HookScore account and saved history from Settings in the app. If you cannot sign in, you can request deletion of your account data or guest usage record by emailing the contact address below. Some provider-side logs or backups may remain for a limited period according to Supabase, Google, or OpenAI retention practices.

Contact

For privacy questions or deletion requests, email penkin.yauhen@gmail.com.