Cookie policy
Last updated: 2026-07-08The widget is cookieless
The LeadButton widget that runs on your site sets no tracking cookies and only starts when a visitor clicks it. Widget analytics is first-party and can run fully cookieless. This policy is mainly about the cookies on our own sites — leadbutton.app and the back office.
- Widget: no tracking cookies
- Visitor-initiated — only starts on a click
- Widget analytics can be cookieless
What are cookies?
Cookies are small files a website can store on your device. Some are needed for the site to work (e.g. staying logged in), others are optional (e.g. analytics).
Which cookies do we use?
On our own sites we use a small set. The marketing site (leadbutton.app) only stores your language preference; the back office uses a necessary session cookie.
| Cookie | Purpose | Type | Retention |
|---|---|---|---|
| lb_mkt_lang | Remembers your language choice (NL/EN) | Preference | 1 year |
| lb_session | Keeps you logged in to the back office | Necessary | Session |
| lb_analytics | Aggregated, cookieless site stats (optional) | Analytics | n/a |
And the widget on my site?
The widget itself sets no cookies on your visitors. It loads async, renders in a Shadow DOM and only starts on a click. That means no WhatsApp policy risk and no consent headache. If you choose cookieless analytics in the back office, that stays the case.
Your choice
We only set optional cookies with your consent; necessary cookies are required to log in. You can always manage or delete cookies via your browser settings.
Want to know more?
Read our privacy & GDPR policy for how we handle data, or email privacy@leadbutton.app. We update this policy when we add or change cookies.
This page is provided for transparency and is not legal advice; review with counsel before relying on it.