Trust & Data Security
Cookie consent and CMPs
August 2026
Quick answers
- Does Engage RevEngine work with CookieFirst or other consent managers?
Yes. Engage RevEngine does not ship a CookieFirst plugin. Engage loads from a single script tag you already control, so CookieFirst and similar consent managers can categorize that script and hold it until the visitor accepts. Until the script loads, the launcher does not appear.
Also asked as: CookieFirst; OneTrust; Cookiebot; CMP chatbot.
- Does Engage RevEngine set tracking cookies on my domain?
No. Engage RevEngine does not set cookies on your domain. Engage uses sessionStorage so a chat can continue if the visitor reloads the tab, and a small amount of localStorage for greeting cooldown, panel-close cooldown, and a returning-visitor hint.
Also asked as: Engage cookies; tracking cookies chatbot; session storage chatbot.
- Where does Engage RevEngine store conversation text?
Engage RevEngine stores conversation text on Scale2Rev servers when chat persistence is enabled in Engage settings. Operators can disable persistence so new conversations are not stored on our servers. Visitors can clear their session with Forget me.
Also asked as: chat persistence; Forget me; is chat stored.
- Who is the controller for Engage RevEngine visitor data?
You remain the controller. Scale2Rev processes Engage RevEngine visitor data as your processor under the Data Processing Addendum at /legal/data-processing-addendum. Disclose the chatbot in your privacy notice.
Also asked as: Engage DPA; GDPR processor; privacy notice chatbot.
Related searches: CookieFirst Engage · does Engage comply with cookie consent · CMP chatbot · OneTrust Engage widget · cookie consent chatbot · does Engage set tracking cookies · GDPR chatbot widget
Engage RevEngine does not ship a CookieFirst (or other CMP) plugin. It does not need one. Engage loads from a single script tag you already control, so it works with CookieFirst the same way other third-party functional scripts do: you categorize the script in CookieFirst, and CookieFirst can hold it until the visitor accepts that category. Operators often place that script in the Functional category. Counsel can instead hold it until consent.
The same pattern applies to other consent managers that gate scripts by URL. WordPress and Shopify installs inject that same widget.js tag.
Browser storage
On the visitor’s browser, Engage does not set cookies on your domain.
- sessionStorage holds a session id so a chat can continue if the visitor reloads the tab.
- localStorage holds a small amount of AutoGreet state: greeting cooldown, panel-close cooldown, and a returning-visitor hint so Engage does not greet the same person on every page.
Until the script loads, none of that storage is written. If counsel wants the widget fully dark until consent, the CMP can block the script; the launcher simply does not appear until they accept.
Conversation storage
Conversation text is stored on Scale2Rev servers only when chat persistence is enabled in Engage settings. Operators can turn persistence off for new sessions. Visitors can clear their session with Forget me, which deletes the conversation on our side when it was stored and wipes the widget’s session and AutoGreet keys in the browser.
Related: Chat persistence and Forget me
Roles and notices
Scale2Rev processes that visitor data as your processor under the Data Processing Addendum. You remain the controller. Disclose the chatbot in your privacy notice.