In short
- We set only the cookies PromptHelm needs to sign you in and keep you signed in.
- Analytics from Ahrefs, Google Analytics, Google Ads, and PostHog runs only if you accept it: on our public pages, for Google Ads on the sign-up page too, and for PostHog in the dashboard too. Section 3 lists the cookies it sets; you can change your mind at any time.
- Our public pages load nothing from third parties unless you accept analytics. Signing in talks to Supabase, which runs our sign-in, and Plan & billing loads Paddle's checkout.
1. What cookies are
Cookies are small files a website stores in your browser. Some are needed for the site to work; others, such as analytics cookies, are optional and need your permission. The UK Privacy and Electronic Communications Regulations and the EU ePrivacy rules set out when we can use them.
2. Strictly necessary cookies
These make sign-in work and keep your account secure. The law lets us use them without asking, because PromptHelm can't work without them. Sign-in runs on Supabase, so its cookies start with sb- and our Supabase project's ID, shown as … below. On secure connections they are sent only over HTTPS.
| Cookie | What it does | How long |
|---|---|---|
sb-…-auth-token | Keeps you signed in to the dashboard. A long one is split into numbered parts (.0, .1). | Until you sign out, at most 400 days; the session behind it ends after 7 days without activity |
sb-…-code-verifier | Lets a sign-in you started, by email link or with GitHub, finish securely. There may be more than one. | Until you sign out, at most 400 days |
ph_consent | Remembers whether you accepted or rejected analytics, so we don't ask again. | 180 days |
3. Analytics
With your permission, our pages are measured by Ahrefs, Google Analytics, Google Ads, and PostHog. Analytics is off until you accept it. Ahrefs, Google Analytics, and Google Ads never run in the dashboard: when you go on to sign in or to the dashboard, the page reloads without them. Google Ads also runs on the sign-up page, to count the accounts our ads bring, but never on the sign-in page. PostHog keeps running there, so we can see how the dashboard is used, and your browser hides the dashboard's text from it first. When you withdraw your consent the page reloads without any of them, and their cookies and anything they stored in your browser are deleted. Each tool receives your IP address with every request; what each one learns is listed in our Privacy policy.
Ahrefs
It counts visits to each public page and where they came from, so we learn which help. Your browser loads its script from analytics.ahrefs.com. It sets no cookies and keeps nothing in your browser; we ask first all the same, because your browser then tells it about your visit.
Google Analytics
It shows how visitors find and use our public pages (the pages they view, how far they scroll, the links out, downloads and forms they use), so we learn which pages work. Your browser loads its script from www.googletagmanager.com.
| Cookie | What it does | How long |
|---|---|---|
_ga | Tells visits from the same browser apart, by a random ID. | 2 years |
_ga_0888MVT2ZM | Keeps the current visit together. | 2 years |
Google Ads
It tells us which of our Google ads bring visitors and sign-ups, so we spend on the ads that work. Your browser loads its script from www.googletagmanager.com. Google may also set or read its own cookies on its domains, such as google.com and doubleclick.net, under its own cookie policy.
| Cookie | What it does | How long |
|---|---|---|
_gcl_au | Tells visits from the same browser apart by a random ID, so a sign-up can be linked to an ad. | 90 days |
_gcl_aw | Remembers the Google ad you clicked to get here, by Google's click ID. | 90 days |
_gcl_gs | Keeps details of that ad click. | 90 days |
_gcl_gb | Like _gcl_aw, for the other kinds of click ID Google uses. | 90 days |
_gcl_ag | Like _gcl_aw, for the other kinds of click ID Google uses. | 90 days |
PostHog
It shows how our pages and the dashboard are used, replays visits so we can see where people get stuck, and reports errors your browser hits, so we can fix what doesn't work. Your browser loads its script from s.prompthelm.app, a name of ours for PostHog's servers.
| Cookie | What it does | How long |
|---|---|---|
ph_phc_pq8xHFtL7wSrqyUrG7Xj8cChgJaBzM38rC8Pdqo9CGWt_posthog | Tells visits from the same browser apart by a random ID, keeps a visit together and, once you sign in, holds your account's ID. | 1 year |
ph_phc_pq8xHFtL7wSrqyUrG7Xj8cChgJaBzM38rC8Pdqo9CGWt_posthog_cpm | Keeps that cookie in step with what PostHog stores in your browser. | 1 year |
4. Your choices
You can accept or reject analytics, and change your mind at any time:
You can also block or delete cookies in your browser's settings. If you block the strictly necessary ones, you won't be able to sign in.
5. Other storage
Unless you accept analytics, we don't use local storage or similar technologies to track you. If you pick Dark or System under Appearance in the dashboard, your browser keeps that choice in local storage as ph-appearance. It never leaves your browser, and choosing Light, the default, removes it.
If you accept analytics, Google Ads also keeps the ad click it measured in your browser's local storage, under keys that start with _gcl_. Rejecting analytics, or withdrawing your consent, deletes them along with its cookies.
If you accept analytics, PostHog also keeps its random ID and the state of your visit in your browser's local and session storage, under keys that start with ph_. Rejecting analytics, or withdrawing your consent, deletes them along with its cookies.
Our fonts and images are served from our own domain, so visiting PromptHelm sends nothing to third parties, with three exceptions. When you sign in or out, your browser talks to Supabase, which runs our sign-in, to send your sign-in link or end your session; Supabase is one of the providers listed in our Privacy policy. And Plan & billing, inside the dashboard, loads the checkout script of Paddle, our reseller, from Paddle's servers. That script sets no cookies on our domain; the checkout itself runs in a frame on Paddle's domain, and any cookies it uses to take your payment safely are Paddle's, under its own cookie policy. On the live service the script also loads Paddle Retain, which Paddle uses to recover failed payments for subscribers. And if you accept analytics, our pages load the scripts of Ahrefs, Google Analytics, Google Ads, and PostHog, as section 3 describes.
6. Contact
Questions about cookies: privacy@prompthelm.app. More about how we use personal data is in our Privacy policy.