Cookie notice
We use cookies to enhance your experience. You control which ones.
How HoneyBill uses cookies and similar technologies on honeybill.ai.
Last updated: 29 April 2026
This policy explains how HoneyBill uses cookies and similar tracking technologies on our website at honeybill.ai. It should be read alongside our Privacy Policy at honeybill.ai/privacy.
By using our website with cookies enabled, you consent to our use of cookies as described in this policy and as managed through our cookie consent banner.
Cookies are small text files that are placed on your device when you visit a website. They are widely used to make websites work efficiently, to provide a better user experience, and to give the website owner information about how the site is being used.
Similar technologies include local storage, pixels, and tracking beacons. References to "cookies" in this policy include those technologies where they perform a similar function.
We use cookies in the following categories:
Strictly necessary cookies
These cookies are essential for the website and app to function. They enable core features such as keeping you logged in, remembering your session, storing your cookie consent decision, and protecting against security threats. You cannot opt out of these cookies through our banner; without them, the service will not work properly.
Functional cookies
These cookies and similar technologies remember choices you make to provide enhanced functionality, such as UI layout (e.g. sidebar state), theme where stored in the browser, or whether you have dismissed a promotional banner. We only use non-essential functional storage when you enable Functional in the consent banner (except where a technology is strictly limited to what is essential for the page).
Analytics cookies
We may use analytics technologies (including Google Tag Manager, Google Analytics where configured via GTM, Vercel Analytics on this marketing site, and Microsoft Clarity when enabled) only if you accept analytics in our cookie banner. Default consent is denied until you choose; we use Google Consent Mode so tags respect your choices.
Marketing cookies
Marketing or advertising-related storage (including signals used for personalised ads where applicable) is used only if you accept marketing in our cookie banner. Consent Mode controls how ad-related tags behave until you opt in.
The following table lists first-party and key third-party technologies we use. Fictional placeholder names (such as honeybill_session or honeybill_consent) are not used in our product; the consent cookie is named gdpr_consent.
| Name / key | Where | Provider | Category | Purpose | Duration |
|---|---|---|---|---|---|
| gdpr_consent | Cookie · Domain .honeybill.ai (shared across honeybill.ai and app) | HoneyBill | Strictly necessary | URL-encoded JSON: analytics, marketing, functional booleans. | Max-Age 365 days (12 months); you are asked again when it expires or you clear cookies. |
| banner_dismissed_at | localStorage · marketing site | HoneyBill | Functional (if consented) | Written only when Functional is on: stores a timestamp so a dismissible promo banner can reappear after a short cooldown. | Until you clear site data or withdraw functional |
| sidebar_state | Cookie · app.honeybill.ai | HoneyBill | Functional | Remembers whether the app sidebar is expanded or collapsed. | 7 days |
| honeybill.session_token | Cookie · api.honeybill.ai | Better Auth / HoneyBill | Strictly necessary | Authenticated API session (Better Auth). | Session (or as set by the auth product) |
| UI_THEME_PREFERENCE | localStorage · app | HoneyBill | Functional | Theme / UI preference (not the old placeholder honeybill_prefs cookie). | Until cleared by you |
GTM / _ga / related | Third-party / first-party | Analytics / marketing per choice | When GTM is configured, tags run under Google Consent Mode v2 (default denied). Analytics or ad-related cookies are set in line with your gdpr_consent choices. | Per Google | |
| Featurebase Messenger cookies / storage (names vary) | Third-party on featurebase.app, do.featurebase.app | Featurebase | Functional (only if you accept functional) | Featurebase Messenger for on-site support chat, help articles, and changelog updates. It loads only when Messenger is enabled for this deployment and you have accepted functional in the banner. See Featurebase privacy. | Per Featurebase |
_clck, _clsk · CLID, MUID, ANONCHK, SM, SRM_B, MR (exact names and domains may change when Microsoft updates Clarity) | First-party on .honeybill.ai; third-party on clarity.ms, c.clarity.ms, bing.com, c.bing.com | Microsoft | Analytics (only if you accept analytics) | Microsoft Clarity session and analytics cookies. Clarity only runs on our marketing site when it is enabled for that deployment and you have accepted analytics in the banner. See Microsoft Clarity - FAQ. | Session to ~13 months per cookie (see Microsoft) |
If you accept analytics, seeing _clck, _clsk, and Microsoft/Bing cookies such as CLID / MUID is expected when Clarity is enabled. Do not list a CSRF cookie unless it appears under your API host with a verified name. Stripe and AppSumo are covered in §5 when you use checkout or outbound links.
Some cookies are set by third parties when their services are used on our site or app:
_clck, _clsk) and on Microsoft/Bing domains (e.g. CLID, MUID, ANONCHK). See Microsoft privacy and Clarity FAQ.If we add other third party services in future (such as embedded videos), this policy will be updated.
When you first visit our website, you will see a cookie consent banner. You can:
You can change your preferences at any time by clicking Cookie settings in the footer of our website. That reopens the same consent dialog so you can accept, reject, or customise categories again.
Your choices are stored in the gdpr_consent cookie with a 12-month lifetime (365-day Max-Age). When it expires or you delete cookies, you will see the banner again.
You can also manage cookies through your web browser. Most browsers allow you to:
Instructions for the most common browsers:
Some browsers offer a "Do Not Track" signal. There is no agreed standard for how websites should respond, so we do not currently respond to Do Not Track signals. We do, however, honour the consent choices you make in our cookie banner.
We may update this policy as our website and cookie use evolve. The "last updated" date at the top reflects the most recent change. Material changes will be communicated via the cookie banner or in-app notice.
For questions about this policy or our use of cookies:
For more information about cookies generally and your rights under UK PECR and UK GDPR:
Information Commissioner's Office - cookies
Also see our Privacy Policy and Terms of Service.