Skip to content
Log in

Cookie policy

Last updated

This policy explains how OpenLiveChat uses cookies and browser storage, including in the dashboard and chat widget, and how you can manage them.

About browser storage

OpenLiveChat is operated by Uprounded, KvK 90374894, at Sint Elisabethstraat 12, 5261 VM Vught, the Netherlands. Contact privacy@openlivechat.com with questions about cookies, storage or privacy.

Cookies are small values stored by your browser and sent with relevant requests. Local storage remembers values on your device between visits. Session storage normally lasts for the browser tab or session. These technologies can support sign-in, remember settings or measure use; their purpose matters, not just their name.

A chat widget embedded on another organisation’s website is part of that website’s visitor experience. That organisation is responsible for explaining its use and collecting any consent required for its deployment. Clearing your browser storage does not delete messages held by that organisation in its workspace.

Account and interface storage

The dashboard uses authentication cookies to keep you signed in. Authentication tokens have a seven-day lifetime; signing in or refreshing a session can issue a new token. Signing out ends your active sign-in session.

Interface preferences, such as the selected theme, navigation widths and the last workspace used, are stored locally where those features are used. They remain until changed, removed by the service or cleared by you or your browser. They are used to remember the interface rather than to target advertising.

Chat widget storage

The widget uses workspace-specific storage. In the names below, “<workspace>” stands for the identifier of the workspace whose widget you are using. Essential chat-session and interface entries remain until removed or cleared by the browser. Optional storage has the separate limits below.

  • openlivechat:visitor-session:<workspace> — local storage used to recognise the visitor’s chat session and request access to their conversations. Keeping a stored token does not override server-side access or session validity.
  • openlivechat:active-room:<workspace> — local storage remembering the conversation selected in the widget.
  • openlivechat:hidden-history:<workspace> — local storage remembering which conversations have been hidden from the widget’s history on that browser. Hiding history does not erase the workspace’s records.
  • openlivechat:viewed-pages:<workspace> — optional session storage for page addresses, titles, view times and counts, used as chat context only after permission for page history. The browser-side list holds up to 100 pages. URL credentials, query strings and fragments are removed. Withdrawal clears this browser-side list. Page information already sent with a conversation may remain in that workspace after the browser session ends.
  • olc:analytics:<workspace> — optional local storage holding a random identifier for widget traffic and conversion measurement, separate from the chat session. It expires 24 hours after creation; reads do not extend that lifetime. Expired values are replaced or removed when the widget next runs. The server stores a workspace-scoped pseudonymous identifier and counts visits per day, without storing the raw browser identifier, page URL or IP in those measurement records. These server-side visit records are scheduled for removal after 25 months; workspace deletion can remove them sooner.

Visit statistics and page history are off by default and have separate opt-in choices. The website operator must connect its consent controls to the widget and pass your current decision on each page and whenever it changes. Loading the widget, starting a chat or having an old stored identifier does not grant permission. The widget does not supply a consent banner for the host website.

An affirmative choice applies to the current page for up to 24 hours. Withdrawing it stops new optional collection, aborts pending visit-measurement requests and clears the corresponding optional browser storage. Essential chat continues to work. A request already received by the server and records already collected are not automatically erased by withdrawal.

Both optional features remain off when your browser signals Do Not Track or Global Privacy Control. Visit statistics are also skipped if local storage is unavailable. These signals do not replace the host website’s consent process. Contact the website operator about its privacy choices or previously stored chat context.

Google Analytics and third-party services

Google Analytics is not currently enabled. It is planned only for our public marketing website, not the dashboard. Before introducing optional analytics, we will update this policy with the active storage details and provide consent choices where required. Customer messages, account content and personal information from forms are not intended for marketing analytics.

Stripe may use its own cookies and similar technologies when you visit its hosted payment or billing pages, including for payment processing and fraud prevention. Its privacy and cookie notices explain those uses and durations. A service you choose to connect may likewise use storage on its own sign-in or authorisation pages. Such storage is separate from the OpenLiveChat entries described here.

Your choices

The Cookie settings link in our website footer explains the storage currently in use. Optional website analytics is off, so we do not ask you to accept it. If we introduce optional analytics, we will provide a choice before it loads and an equally accessible way to withdraw permission.

You can inspect, block or clear cookies and site data in your browser’s privacy settings. Clearing data may sign you out, reset preferences or stop a widget from restoring a conversation. Browser settings and protections can also remove local storage automatically.

For a widget on another organisation’s website, use that website’s available privacy controls or contact its operator. To request access to or deletion of stored conversation data, contact the organisation you chatted with; clearing your device does not delete server records. For OpenLiveChat’s own processing, contact privacy@openlivechat.com.