Skip to main content

Cookies set by the Emporiqa widget

Last updated: November 18, 2026

If you’ve installed the Emporiqa chat widget on your store, it sets one cookie on your domain and keeps a few entries in the browser’s storage there. This page lists both and gives you ready-to-use text for your own cookie policy.

The cookie and the storage entries the chat itself needs are classified as strictly necessary under Article 5(3) of the ePrivacy Directive (in Germany, § 25 TDDDG): the chat the visitor asked for does not work without them. Consent is not required for those, but disclosure is. A few entries serve features beyond that chat: proactive messages, daily usage counts and recently viewed products. If your data protection officer wants none of them, add storage=essential to the embed code: on page load the chat then writes only what it needs, and proactive messages still show. If they want no contact with Emporiqa before the visitor opens the chat, load the chat only when the visitor clicks (both below).

The cookie

Name emporiqa_sid
Type First-party, strictly necessary
Purpose Maintains the shopper’s chat session across page loads and links a completed purchase back to the conversation that influenced it
Duration 1 hour, renewed while the chat is in use
Personal data Only a random conversation ID. It holds no name, email address or IP address, but it links this browser to its chat conversation and, when order linking is on, to the order, so it counts as pseudonymous personal data.
When it is not set When your store switches off linking orders to chats: the switch in the Emporiqa Shopware plugin, which then sends no orders to Emporiqa either, or attribution=off on the embed code.

Browser storage

Besides the cookie, the widget keeps state in localStorage and sessionStorage on your store’s domain. These are not cookies, but the same rule applies to them. None holds a name, email address or IP address. <id> is your store ID, followed by the customer’s ID when your store signs customers in to the chat.

In the default mode, the entries for proactive messages, usage counts, recently viewed products, the attention pulse and the open-tab check are written when a page loads, and so is the country where you limit the chat by country. The conversation, unread, open-panel, satisfaction and availability entries, and the emporiqa_sid cookie, are written only once the visitor has opened the chat.

With storage=essential added to the embed code, a page load writes only the open-tab check (emporiqaLeader_, emporiqaWasLeader_) and, where you limit the chat by country, the country. Proactive messages still show, but nothing about the visit is stored: every visitor counts as new, and a message limited to once per visit can show again on the next page. Recently viewed products, the attention pulse and the daily usage counts are off. Once the visitor opens the chat, the same entries are written as in the default mode. How to set it up

Entry Purpose Lifetime When loaded on click
emporiqaChatThreadId_<id>
localStorage
The conversation, so it carries on from page to page Until a new conversation, or until site data is cleared After the click
emporiqaChatOpened_<id>
localStorage
When the visitor last opened the chat, so later pages load it at once Used for 30 days after the last open; stays until site data is cleared Only in this mode
emporiqaHasUnread_, emporiqaLastMsgTime_, emporiqaOpenedThread_, emporiqaOpenedAt_, emporiqaNoSession_, emporiqaLastPoll_, emporiqaPollMs_
localStorage
The unread badge, and how often to check for a reply Overwritten as the chat is used After the click
emporiqaLeader_, emporiqaChatOpenAt_, emporiqaBroadcast_; emporiqaChatIsOpen_, emporiqaWasLeader_
localStorage; sessionStorage
Whether the chat panel is open, and which open tab checks for replies localStorage: refreshed while a tab is open; an entry left behind by a closed tab is ignored and stays until it is overwritten or site data is cleared. sessionStorage: until the tab closes After the click
emporiqaCsatPending_, emporiqaCsatAsked_
localStorage
The satisfaction question after a conversation, asked once (where it is on) Until the next conversation After the click
emporiqaUnavailable_<id>
localStorage
Your store cannot take a conversation right now, so the button is not shown 5 minutes (removed the next time a page reads it after that) After the click
emporiqa_country
localStorage
The visitor’s country code, where you limit the chat by country 30 days, or 15 minutes where the chat is not offered there After the click
emporiqaVisited_<id>
localStorage
The value 1, so proactive messages can treat new and returning visitors differently Until site data is cleared No
emporiqaVisit_<id>, emporiqaTriggerClaim_<id>
localStorage; sessionStorage
Pages seen in this visit and the proactive messages shown or closed, so none repeats A new visit starts after 30 minutes without a page view No
emporiqaReported_<id>
localStorage
The date and the chat events this browser already counted today Until the end of the day (UTC) No
emporiqaRecentlyViewed_<id>
localStorage
Up to 25 product pages the visitor opened, where page awareness is on Until site data is cleared No
emporiqaNudged
sessionStorage
The chat button’s attention pulse was shown Until the tab closes No

The chat window itself runs on Emporiqa’s domain. Current versions of Chrome, Edge, Firefox and Safari keep its storage separate for each shop; in a browser that does not, it is shared by every shop that uses Emporiqa. It holds the conversation and the time of its last message, which signed-in customer a recent conversation belongs to, how often the satisfaction question was shown, and, where voice is on, whether the visitor confirmed the voice notice and whether spoken replies are muted. The conversation and its last-message time are deleted the next time the chat loads 30 days or more after the last message. The mute setting lasts until the tab is closed. The other entries stay until the visitor clears them.

On Magento, the Emporiqa module also uses Magento’s own form_key cookie to protect cart requests made from the chat, and creates it only when the page has none. It also adds a signed-in yes/no flag to the customer data Magento keeps in the browser’s localStorage. Neither holds a name, email address or customer ID.

Loading the chat only when the visitor clicks

With the snippet under Settings > Integration > Load the chat only when the visitor clicks, or the switch of the same name in the Emporiqa Shopware plugin, your page draws the chat button itself. Until the visitor clicks it, the browser makes no request to Emporiqa and nothing is written to the cookie or to storage. The button reads one entry, emporiqaChatOpened_<id>: if the visitor opened the chat in the last 30 days, the chat loads at once, so a conversation carries on from page to page.

After the click, only the entries marked in the last column are written. Proactive messages, the daily usage counts and recently viewed products are off in this mode. The emporiqa_sid cookie is still set after the click unless your store also switches off linking orders to chats. How to set it up

Copy-paste for your cookie policy

Drop this into the "Strictly necessary cookies" section of your cookie policy. Adjust the wording to match your house style. The facts are what matter.

Short version

emporiqa_sid (strictly necessary, first-party, 1 hour, renewed while the chat is in use). Set by the Emporiqa chat assistant on this site to keep the shopper’s chat session continuous across page loads and to attribute purchases to the conversation that influenced them. Holds only a random conversation ID, no name, email or IP address; consent not required.

Long version (recommended for EU stores)

Our store uses an AI chat assistant provided by Emporiqa (Rosel Group LTD., Bulgaria). When you interact with the chat, a first-party cookie named "emporiqa_sid" is stored on your device. This cookie keeps your chat session continuous when you navigate between pages and lets us link a completed order back to the chat conversation that helped you find the product. The cookie holds only a randomly generated identifier. It holds no name, email or IP address, but it links your browser to your chat conversation, so it is pseudonymous personal data. The cookie expires 1 hour after the chat was last used. Under Article 5(3) of the ePrivacy Directive, this cookie is classified as strictly necessary and does not require your consent, but we disclose it here for transparency.

What we don’t set

For completeness, the Emporiqa widget does not set:

  • Tracking cookies, advertising cookies, or third-party cookies of any kind
  • Analytics cookies. Aggregate metrics use a server-side, daily-rotated anonymous fingerprint; no identifier reaches the shopper’s browser.
  • Device fingerprints, advertising identifiers, or cross-site identifiers. The one lasting identifier is a random conversation ID (emporiqaChatThreadId_<id>, also copied into the conversation entries above). It is created when the visitor first opens the chat, kept until a new conversation starts or site data is cleared, and sent to Emporiqa to check for replies while that conversation is still open on our side.

Who’s responsible for what

When the widget runs on your store, you are the data controller for the visit and Emporiqa acts as your data processor. The emporiqa_sid cookie is set in your first-party context. It appears under your store’s domain in browser dev tools and belongs in your cookie policy, not ours.

Our own processing of chat conversation data is covered in our Privacy Policy and the third parties we engage are listed in our Subprocessors page.

Changes

If we ever introduce a new cookie or storage entry, we’ll update this page first and email the address on file before the change goes live. The current list is exactly one cookie and the storage entries above, plus, on Magento stores, the two Magento items described above.

Questions

If a regulator asks you about this cookie or you want to verify anything on this page, email support@emporiqa.com.