Cookie policy — what we store in your browser, and why

1. What cookies are, and what this policy covers

A cookie is a small text file a website places in your browser so it can recognise you on the next page or the next visit. “Browser storage” (localStorage) does a similar job without being sent to the server with every request. This policy uses “cookies” for both, and it lists every one that comver.io and the Comver workspace set.

It covers comver.io (including its Polish version) and the Comver workspace on the Comver domain, both operated by Comver sp. z o.o., Złota 59, 00-011 Warsaw, Poland. It also explains, in section 5, what happens on a merchant’s storefront that uses Comver widgets — those run inside the merchant’s own site and are governed by that store’s cookie notice, with Comver acting as the store’s processor. How we use personal data more generally is described in our Privacy policy.

2. How we use cookies

The consent panel on comver.io offers three categories. Only the first is on without your say-so.

• Essential — required for the site to work: remembering your consent choice so the banner does not ask again, and — inside the workspace — keeping you signed in and protecting forms. These cannot be switched off; without them the site or the workspace would not function. Legal basis: strictly necessary (ePrivacy Article 5(3)) and our legitimate interest in running a secure site.
• Analytics — helps us understand which pages and features matter to commerce teams (which pages are read, where visitors come from, what they click). Loaded only after you accept, never before. Legal basis: your consent.
• Marketing — lets us measure our own campaigns, for example which page a demo request or sign-up came from. It is off by default and, if you enable it, is limited to first-party measurement: Comver sets no third-party advertising, retargeting or cross-site tracking cookies and does not share your data with ad networks. Legal basis: your consent.

3. The cookies and storage we use

This is the complete list as of 16 August 2026. We will update it before any new cookie or script goes live.

3.1 comver.io

Locale routing (English unprefixed, Polish under /pl) is done from the URL and sets no cookie.

3.2 The Comver workspace

The workspace loads no analytics or marketing cookies. Usage that Comver needs to run the product (for example that a scan finished) is recorded server-side against your account, as described in the Privacy policy, not through cookies.

4. Your consent and how long it lasts

• The first time you visit comver.io the consent panel appears. Accept all enables Analytics and Marketing; Essential only keeps both off; Cookie settings lets you choose per category. Closing the panel without choosing sets nothing except that no non-essential cookie is loaded.
• Your choice is stored for 180 days in comver_consent. After that the panel asks again. If you clear your browser data it will also ask again.
• You can change or withdraw your consent at any time with the Manage cookies button in section 6 or in the site footer. Withdrawing consent stops the relevant scripts from loading on your next page view; cookies they already set can be removed from your browser settings.
• Non-essential scripts respect your choice technically, not just on paper: they are not injected into the page until the stored consent says they may be.

5. Storefronts that use Comver

When a merchant installs Comver, our widgets — the revenue modules, Callio’s chat and order-by-phone entry points, and the Behaviour tracking embed — render inside that store’s own theme through one Shopify app embed. Storage those widgets use is first-party to the merchant’s domain and is there to make the widget work: to remember which cart the offer belonged to, which reward step a shopper reached, or that a session is the same session across pages so a funnel can be counted.

your-store.com/products/… Theme app embed

Comver Bundling & Upsells

Comver Trust AI · Comver Callio Chat

First-party to the store Never the raw IP Form interactions, no input values

• The store, not Comver, is the controller for that storage and for the behaviour data it produces; the store’s cookie notice and consent tool govern it, and Comver’s embed can be gated behind the store’s consent settings.
• The Behaviour embed never stores the raw IP address, records form interactions but not the values typed, and masks text inputs in session replays. It does not follow a shopper to other websites, and Comver does not use storefront data for advertising.
• The Customer Dashboard served through the Shopify App Proxy uses the store’s own customer login; Comver sets no additional identity cookie there.

Questions about a specific store’s use of Comver should go to that store first. If you cannot reach them, write to privacy@comver.io and we will pass your request on.

6. Manage cookies

Open the consent panel to review or change your choice for comver.io. Your current settings are shown, and saving writes a fresh comver_consent for another 180 days.

6.1 In your browser

You can also block or delete cookies in your browser. Every major browser lets you see which cookies are set, delete them, and block cookies from particular sites or all sites: look for “Cookies and site data” (Chrome, Edge), “Privacy & Security” (Firefox) or “Privacy” (Safari) in the settings. Blocking essential cookies will stop the consent panel from remembering your choice and will sign you out of the workspace.

7. Changes and contact

We will update this policy before we add, remove or change a cookie or a script that sets one, and the date at the top will change with it. Adding a new analytics or marketing cookie never turns it on for you: it stays off until you consent to that category.

Cookie and privacy questions

privacy@comver.io

Post

Comver sp. z o.o., Złota 59, 00-011 Warsaw, Poland

Privacy policy

How Comver handles data

Terms of service

The agreement between you and Comver

comver.io and the Comver workspace Storefront widgets: the store’s notice governs Last updated 16 August 2026