Legal

Privacy Policy

Last updated October 28, 2026

This describes exactly what Jellyhook collects and why, split into what we collect about you as a Jellyhook customer, and what your tracker script collects about visitors to your site.

Data about you, our customer

IdentityYour user ID, email, name, and profile photo if you upload one.
Site configurationDomain, site name, API key, and tracking on/off state for each site you register.
Team membershipEmails and roles of anyone you invite to a site.
BillingYour plan, subscription status, and billing history, processed by our billing provider, not stored as raw payment details on our servers.

Data your tracker collects from your site's visitors

This is collected on your behalf, from people visiting the site YOU install the tracker on. It never leaves the boundary of that one site's data, and it's visible only to you and the teammates you invite.

Visitor & session identityA random ID generated in the visitor's browser (not tied to a real name unless they submit a form) plus session timing.
Page activityPage paths, time spent on each page, scroll depth, whether a page was revisited, and how long each part of the page (by its headings) was on screen.
Technical contextDevice type, screen width, approximate country, timezone, and referrer URL. The country normally comes from the hosting platform's own header. When that is missing, the visitor's IP address is held briefly, sent over HTTPS to a third-party lookup service (ipwho.is) to get the country, and then deleted whether or not the lookup worked. We also keep a salted one-way hash of the IP and of the browser's identifier string, which together recognise one device (so one person opening the site in several private windows on the same day counts as one visitor) but cannot be turned back into an address or a browser string. Our hosting provider's own request logs are outside Jellyhook's control.
First visitFor a new visitor, the referrer, campaign tags (UTM) and landing page of their very first visit, kept to show where visitors originally came from.
ClicksOnly on elements you mark with data-track-click on your own pages.
Form submissionsWhatever fields your form collects, commonly name, email, and phone, tied to the page and session it came from.
Waiting to be sentIf our servers do not answer, the tracker keeps what it was sending (including a submitted form's values, without the fields that are always left out) in that browser tab's session storage and tries again for up to 30 minutes. Each item is deleted as soon as our servers accept it, and in any case when the tab is closed.
Page structureHeading text and position captured from your pages, used to mark headings on the visit chart.

We do not build a cross-site profile of an individual visitor. Data is scoped per site, and a visitor can only be linked to a real identity (name/email) if and when they submit a form on that site.

Consent and your responsibilities

The tracker stores a random visitor ID and session details in the visitor's browser (local storage), keeps anything still waiting to be sent in that tab's session storage, and sends the data above to Jellyhook. It sets no cookies. When Global Privacy Control or Do Not Track is on, the tracker does nothing at all. When the site has a cookie banner it recognises (Cookiebot, OneTrust, CookieYes, Complianz, an IAB TCF banner or Google Consent Mode), it starts only after the visitor accepts analytics, and stops and erases what it stored if they refuse or withdraw. Sites with another banner can call the tracker from it (consent mode).

You are responsible for getting consent where your visitors' law requires it, and for describing the tracking in your own privacy notice; the Privacy and consent docs have text you can use. Jellyhook does not offer a data processing agreement yet, so it is not set up for sites that must have one, which is usually the case for sites with visitors from the EU or the UK. Nothing here is legal advice.

Enter Hook with AI

When you use Enter Hook with AI, your typed question, the query currently in the builder, today's date and up to 25 page paths of your site are sent to OpenAI, our AI processor, to turn the question into a Hook query. Your visitors' data, query results, names, emails and IP addresses are never sent. We record how many questions each account asks and what they cost, not the text of the questions.

How forms are measured

On a tracked form the script records when each field is clicked into and left, whether it was left filled or empty, how many times its value changed, when the browser refused the form because a field was invalid, the form's list of fields (their names, types and whether they are required), and how long the form was on screen before someone started. It never records what is typed, or how long it is. The values of a form are only sent when the form is submitted, as a lead, and even then payment card numbers and security codes, bank account numbers and government identity or tax numbers are left out in the visitor's browser and checked again on our servers. Site owners can leave out any other field.

Connecting an AI app

A site owner or admin can create an access token that lets an AI app they choose (for example Claude or Cursor) read that site's Hook data. Answers go to that app's AI provider. Emails, names and phone numbers are hidden unless the token was created with an extra confirmation, and form answers are never sent. Tokens expire and can be revoked. The owner is responsible for choosing apps they are allowed to share the data with. We record how many calls each token makes, not what was asked or answered.

How it's used

Solely to run the product you signed up for: showing you your own site's traffic, visit charts, leads, and page-health analysis. We don't sell tracked data, and we don't share it across accounts. Every query in the dashboard is scoped to sites you own or have been invited to.

Retention & deletion

Visit, lead and form data is kept for 13 months by default and deleted after that, once a day. A site owner or admin can choose 6, 13 or 25 months, or keep it for as long as the site is active. Pausing a site stops new data collection but does not erase history already collected. When a visitor asks a site to delete their data, an owner or admin erases them by the email they used in the form: their leads and the visits of the browsers that sent them are deleted, and only a count and a one-way hash of the email are kept as a record. Removing a site or a teammate hides it from the dashboard but does not erase the data on its own. If you want a site's data fully deleted, ask through the Support button in your dashboard and we will permanently delete it within 30 days of your request.

Service providers we rely on

Jellyhook runs on these providers. Each one only receives what it needs to do its job. Our database and hosting run in the United States (US West, Oregon).

SupabaseDatabase. Stores the tracked visit, form and lead data for each site, and your account settings.
VercelHosting. Serves the website, the dashboard and the tracker script, and keeps its own request logs.
ClerkSign-in and accounts for Jellyhook customers. It does not receive data about your site's visitors.
ipwho.isCountry lookup, only when the hosting platform did not provide a country. Receives the visitor's IP address over HTTPS; the IP is deleted afterwards.
Google Analytics and Vercel AnalyticsVisit statistics for jellyhook.com.
OpenAIOnly when you use Ask Hook: receives your typed question, the list of fields Hook can use, up to 25 of your site's page paths, and the question already in the builder. It never receives visitor records.