engageSPARK Cookie Policy
Last Updated: August 13, 2026
At a Glance
A plain-language summary of how engageSPARK uses cookies. This summary is for convenience; the full policy below is the operative document.
What we use. A small number of cookies that keep you logged in, run our chat support (ClearFeed), and protect our Public Website and App against abuse (Cloudflare).
What we don’t use. No advertising or cross-site tracking pixels, and no third-party web-analytics tools. Our only usage insight comes from the aggregate security and traffic data Cloudflare provides; it does not profile you.
Your choice. Necessary cookies are always on. On the Public Website, the cookies behind ClearFeed chat support load only with your consent; in the App, ClearFeed is part of the service, so you cannot opt out of it. You can change or withdraw consent at any time.
Questions? Your rights and our contact details are in our Privacy Policy.
1. Introduction
This Cookie Policy explains how engageSPARK, Inc. (“we”, “us”) uses cookies and similar technologies on our website at https://www.engagespark.com ( “Public Website”) and in our logged-in web application at https://app.engagespark.com (“App”). It is incorporated into, and forms part of, our Privacy Policy, which explains your rights and how we handle personal data more generally.
It applies to both the Public Website and the App. Most cookies work the same way on each; where a cookie is used or treated differently depending on which one you are using, we say so.
2. What are cookies?
A cookie is a small text file that a website places on your browser or device. Cookies let a site remember your actions and preferences (such as staying logged in) over a period of time. “Similar technologies” include things like local storage and pixels; for simplicity we refer to all of them as “cookies” in this policy.
We do not use tracking or advertising pixels (web beacons), and we do not use third-party web-analytics cookies. The only insight we have into how our Public Website and App are used is the aggregate traffic and security information our content-delivery and security provider, Cloudflare, generates as part of protecting them.
3. Categories of cookies we use
We group our cookies into two categories:
- Necessary (the law calls this “strictly necessary”): cookies that are required for the Public Website, App, and your account to work (for example, to keep you logged in or to protect against abuse). These are placed without consent because our Public Website and App cannot function without them.
- Functional: cookies that power optional features on the Public Website, chiefly ClearFeed chat support. The Public Website works without them, but the feature itself will not load, i.e., the chat window will not appear. On the Public Website, these cookies load only with your consent. In the App, these same ClearFeed cookies are strictly necessary (see Section 4.2).
We do not use cookies to build advertising profiles or to track you across other websites. A few cookies fall into different categories depending on whether you use the Public Website or the App; where that happens, we explain it below.
4. Cookies we place
The cookies below are grouped by the service that sets them and listed alphabetically. “Persistent” and “Temporary” mark items stored in local storage, the former of which stay until you clear them in your browser.
4.1 engageSPARK (first-party)
Set by us to run your account.
| Cookie name | Purpose | Expiry | Category |
|---|---|---|---|
| authToken | Keeps you logged in to your engageSPARK account. | 1 week |
Public Website: N/A App: Necessary |
| authTokenExpiresAt | Records when your login session expires so we can log you out automatically at the right time. | 1 week |
Public Website: N/A App: Necessary |
| es_first_page_load | Records whether the current page is the first one you visited this session. | Session |
Public Website: N/A App: Necessary |
| logout | Ends your session when you sign out. | Session |
Public Website: N/A App: Necessary |
| otpToken | Supports the one-time-password step of the login process. | Session |
Public Website: N/A App: Necessary |
| trialMode | Stores information about your current subscription or trial. | Session |
Public Website: N/A App: Necessary |
4.2 ClearFeed
We use ClearFeed for customer messaging. On the Public Website, it provides optional chat support, which means these items are functional and load only with your consent. In the App, ClearFeed does more than chat: we also use it to deliver essential service notifications and product updates that you cannot opt out of – for example, changes to how the platform works. Because these communications are part of the service itself, the same items are Necessary in the App and load without separate consent. For more information, see the ClearFeed Compliance and Security page.
| Cookie name | Purpose | Expiry | Category |
|---|---|---|---|
| firebase-heartbeat-database | IndexedDB database created by the ClearFeed Web Chat Firebase SDK. Stores limited SDK platform and daily heartbeat metadata used for service reliability. | Persistent |
Public Website: Functional App: Necessary |
| firebaseLocalStorageDb | IndexedDB database used by ClearFeed Web Chat to maintain the visitor’s authenticated chat session and provide access to previous conversations. | Persistent |
Public Website: Functional App: Necessary |
| firebase:authUser:*:cf-chat-widget | Firebase authentication record stored within browser storage. It can contain a user identifier, authentication tokens and token-expiration information required for ClearFeed chat continuity. | Persistent |
Public Website: Functional App: Necessary |
| draggable-position | Local-storage entry that remembers where the visitor positioned the ClearFeed chat button. It is used only when dragging is enabled. | Persistent |
Public Website: Functional App: Necessary |
| firebase:previous_websocket_failure | Local-storage entry used by Firebase to recover from unsuccessful realtime WebSocket connections and select a working connection method. | Temporary |
Public Website: Functional App: Necessary |
| firebase:host:clrf-prod.firebaseio.com | Local-storage entry that may cache the Firebase Realtime Database host used to deliver ClearFeed chat messages. | Persistent |
Public Website: Functional App: Necessary |
4.3 Cloudflare
Cloudflare sits in front of our Public Website and App to provide security, bot protection and content delivery. These cookies are Necessary and do not profile you, so they cannot be switched off individually; you can only block them through your browser (see Section 5). For more information, see the Cloudflare Privacy Policy and Cloudflare’s description of the cookies it sets.
| Cookie name | Purpose | Expiry | Category |
|---|---|---|---|
| __cf_bm | Cloudflare bot-management; tells human and automated traffic apart. | 30 minutes |
Public Website: Necessary App: Necessary |
| _cfuvid | Distinguishes visitors for security and rate-limiting (no user profiling). | Session |
Public Website: Necessary App: Necessary |
| cf_chl_rc_i, cf_chl_rc_ni, cf_chl_rc_m | Set by Cloudflare’s Challenge Platform only while a challenge is being solved; used internally to detect issues with the challenge process. | Transient |
Public Website: Necessary App: Necessary |
| cf_clearance | Verifies your browser and provides bot protection. | 1 year |
Public Website: Necessary App: Necessary |
4.4 CookieYes
CookieYes (CookieYes Limited) is our consent-management provider: it powers the cookie banner and stores the choices you make there. This cookie is Necessary because it is what lets us honour and keep a record of your consent. For more information, see the CookieYes Privacy Policy.
| Cookie name | Purpose | Expiry | Category |
|---|---|---|---|
| cookieyes-consent | Remembers your cookie-consent choices so the banner is not shown on every visit, and stores a consent ID as a record of your consent. | 1 year |
Public Website: Necessary App: N/A |
4.5 Google reCAPTCHA
We use Google reCAPTCHA on our forms to protect them against spam and automated abuse. It is required for these forms to work. reCAPTCHA may set the items below; it may also place session items (such as rc::b and rc::c) that are cleared when you close your browser. For more information, see the Google Privacy Policy.
| Cookie name | Purpose | Expiry | Category |
|---|---|---|---|
| _GRECAPTCHA | Set by Google reCAPTCHA to run its risk analysis and tell human visitors apart from bots, protecting our forms from spam and abuse. | 6 months |
Public Website: N/A App: Necessary |
| rc::a | Local-storage item used by Google reCAPTCHA to distinguish humans from bots. | Persistent |
Public Website: N/A App: Necessary |
| rc::f | Local-storage item used by Google reCAPTCHA to distinguish humans from bots. | Persistent |
Public Website: N/A App: Necessary |
5. Your consent and how to manage cookies
When you first visit the Public Website, we ask for your consent before placing any functional cookies. Necessary cookies do not require consent and are always active. In the App, ClearFeed also delivers essential service notifications and product updates that are part of the service, so it is treated as Necessary there and is not subject to separate consent.
You can change or withdraw your consent at any time by reopening the cookie banner on the Public Website and updating your choice. Withdrawing consent does not affect cookies that were already placed before you withdrew it, and does not affect Necessary cookies.
You can also manage or delete cookies through your browser settings, including blocking them or asking to be notified each time a cookie is set. If you disable Necessary cookies, parts of our Public Website and App – including login – may stop working. Browsers vary; see the Help section of your browser for instructions.
6. Your rights and contact
Cookies can involve the processing of personal data. The legal bases we rely on, how long we retain data, international transfers, your rights – including how to exercise them and how to lodge a complaint with a supervisory authority – and how to reach our Data Protection Officer are all set out in our Privacy Policy.
Thank you for taking the time to read engageSPARK’s Cookie Policy.