Cookie Policy

1. The categories we use

Everything below is set either by chatdrill.com itself (first-party) or by a provider we have named (third-party), and each entry states how long it lasts — a session cookie disappears when you close the browser, a persistent one stays until the stated duration expires or you delete it. Local storage, session storage and pixel tags are treated exactly the same way as cookies throughout this policy.

Strictly necessary — always on

• Purpose: signing you in, keeping your session, load balancing, CSRF protection and remembering your cookie choices.
• Examples: session identifier, authentication token, security token, consent record.
• Typical duration: session to 12 months.
• Consent: not required — the service does not work without them.

Functional

• Purpose: remembering preferences such as language, timezone, inbox layout and whether you dismissed a banner.
• Examples: language preference, UI state, announcement dismissed.
• Typical duration: up to 12 months.
• Consent: requested where required by local law.

Analytics

• Purpose: understanding which pages and features are used so we can fix what is confusing and improve what is working.
• Examples: product analytics identifier, page-view and event counters, error monitoring.
• Typical duration: up to 24 months.
• Consent: requested before these are set where required.

Marketing

• Purpose: measuring which campaigns bring visitors to us and avoiding showing the same message repeatedly.
• Examples: campaign attribution identifier, advertising pixel.
• Typical duration: up to 12 months.
• Consent: always requested, and off by default until you accept.

2. Cookies set by the Chatdrill widget

When a business installs the Chatdrill widget on its own website, the widget sets a small number of first-party identifiers on that website's domain. These are necessary to run the chat.

• A visitor identifier so a returning visitor keeps their conversation history instead of starting again.
• A session identifier linking messages in one conversation.
• Widget state — whether the window is open, minimised or previously dismissed.

The business operating that website is the controller for those identifiers and is responsible for disclosing them in its own cookie notice and, where applicable, obtaining consent. Widget behaviour can be configured so the chat only loads after consent is given.

3. Third-party cookies

Some cookies are set by providers we rely on — for analytics, error monitoring, payments, video embeds and campaign measurement. We do not control how those providers use the data they collect; please review their own policies. The current list of providers is available on request from privacy@chatdrill.com.

4. How to control cookies

• Use the cookie banner or preference link on this site to accept or reject non-essential categories, and to change your mind later.
• Use your browser settings to block or delete cookies. Blocking strictly necessary cookies will break signing in.
• Use browser or extension controls to block third-party cookies specifically, if you would rather not adjust each site.

We honour Global Privacy Control signals where they are legally recognised. We do not currently respond to legacy Do Not Track headers, because there is no consistent standard for what a compliant response looks like.

5. Changes and contact

We update this policy when we add or remove a provider. The date at the top shows the current version. Questions: privacy@chatdrill.com.