Cookie Policy

Cookies are small text files stored on your device when you visit a website. Your browser's local storage and session storage work in a similar way, and this page covers them too. We use them to keep you signed in, to remember a few choices and, outside the EU, the EEA, the UK and Switzerland, to understand how the site is used.

PostHog, our product analytics tool, doesn't use cookies; what it keeps in browser storage is described in section 3.

We use three analytics tools. What they keep on your device depends on where it is, judged by its time zone, and on your choices:

• Vercel Web Analytics and Speed Insights count page views and measure page speed for every visitor, without cookies or browser storage. Vercel counts visitors with a hash of the request that it discards after 24 hours.
• PostHog records page views and a few product events (it doesn't record every click). Outside the EU, the EEA, the UK and Switzerland, it keeps a random visitor ID in local storage (ph_<project key>_posthog) and a few values for the current tab in session storage, and once you sign in it links your events to your account ID, never to your email or name.
• In the EU, the EEA, the UK or Switzerland, or when your browser sends a Global Privacy Control signal, PostHog runs in cookieless mode: it stores nothing on your device and doesn't link your browser's events to your account. Its servers count visits with an ID made from your IP address and browser details plus a key that changes every day and is then deleted, so visits on different days aren't connected. After you refuse in section 5, PostHog reports nothing from this browser, wherever you are.
• Google Analytics sets the _ga and _ga_* cookies to count visits and traffic sources, with Google signals and ad personalization turned off. When you submit a form on our site, it also receives a hashed copy of the contact details you typed, such as your email address (Google's user-provided data collection). It loads only outside the EU, the EEA, the UK and Switzerland, without Global Privacy Control, and if you haven't refused in section 5; otherwise it doesn't load and any _ga cookies set earlier are deleted. See how Google uses data from sites that use its services.

hz_ft and hz_lt are set by our own site and read only by it. They don't track you across other websites. When you sign up or give us your email on a form, their contents are copied to your record so we can see which pages and sources bring people to HumanizeIt (see the Privacy Policy).

We don't set them, and delete any set earlier, when your device's time zone is in the EU, the EEA, the UK or Switzerland, or when your browser sends a Global Privacy Control signal; a form you send during that visit still says how you arrived, without anything stored on your device. You can refuse attribution on this browser in section 5: the cookies are deleted, and nothing about how you arrived is kept or sent with a form.

The button below refuses Google Analytics, PostHog and the attribution cookies on this browser. It deletes _ga, _ga_*, hz_ft, hz_lt and what PostHog stored, and from then on Google Analytics doesn't load, PostHog reports nothing from this browser and the attribution cookies aren't set. Vercel Web Analytics and Speed Insights, which store nothing on your device, still count page views and page speed (section 3). Signing in, the free tools and everything else work the same.

Your choice is saved in this browser's local storage (hz_attr_optout), so clearing your site data or using another browser resets it.

A few other small values are kept in your browser's storage, not in cookies: hz_lead (you already gave us your email, so we stop showing email popups), hz_exit_magnet_at (when we last showed a free-guide popup, so it appears at most once every 14 days), humanizeit_exit_shown (the home page popup was already shown), humanizeit_onboarded (you closed the getting-started checklist in your dashboard), hz_share_chip_day (the invite-a-friend prompt shows at most once a day) and, in session storage, prefill-text (text you typed on the home or compare page when you open the editor). If you connect our Chrome extension, its sign-in token is kept as humanizeit_ext_token. On our own team's devices, hz_internal keeps their visits out of our analytics. Apart from the extension token, which the extension uses to sign you in, these values never leave your device.

We do not use any advertising cookies. We do not sell your data to third parties or use cookies for ad targeting.

You can also control cookies through your browser settings. Note that disabling required cookies (Clerk session cookies) will prevent you from signing in.

• Chrome: Settings → Privacy and security → Cookies
• Firefox: Settings → Privacy & Security → Cookies and Site Data
• Safari: Preferences → Privacy → Manage Website Data

Questions about cookies? Email us at support@humanizeit.app