This policy explains the cookies and browser storage that JIVIQ (“JIVIQ”, “we”, “us”, “our”) uses, what each item does, how long it lasts, and how you can control it. It covers our marketing website (jiviq.com), our admin application (app.jiviq.com), our public forms (forms.jiviq.com), our public booking pages (book.jiviq.com), our hosted chat, call and meeting pages (chat.jiviq.com and talkto.page), and the embedded chat widget that businesses paste onto their own websites. It sits alongside our Privacy Policy; if anything here is unclear, write to support@jiviq.com. The service is operated by Stratus Labs (registered address: C4 602, Edenn Towers CHS, Pune 411057, India).
What changed in v1.2 (2026-09-25). Withdrawing your analytics consent on jiviq.com now reaches every jiviq.com tab open in that browser, not only the tab where you withdraw, and it also removes Clarity’s
_cltktab marker, which the earlier version said stayed until you closed the tab. Sections 4, 6 and 7 now say so.
What changed in v1.1 (2026-09-24). This version corrects the earlier one. The earlier text said that jiviq.com used no third-party analytics: no Google Analytics and no analytics cookies. That was not true. From August 2026 our marketing website loaded Google Analytics and Microsoft Clarity on every page, and they set their cookies, without asking first. jiviq.com now asks first: the two tools load only after you click Accept in its cookie banner, and you can withdraw at any time. This version names them and the cookies and storage they use (Sections 3.4 and 4) and says how to withdraw (Sections 6 and 7). It also lists storage our product already used that the earlier table missed, including the storage used by calls and meetings.
Summary of key points
- Our product — the admin app, forms, booking pages, hosted chat, calls, meetings and the chat widget — uses no third-party advertising cookies and runs no third-party web-analytics product. Our marketing website, jiviq.com, is the exception: with your consent it uses Google Analytics and Microsoft Clarity (Section 3.4).
- We use cookies and browser storage for four things: signing you in, remembering your preferences and drafts, audience analytics through the chat widget, and — on jiviq.com, only if you accept — website analytics.
- Most of what our product uses is not a traditional HTTP cookie at all but browser storage (localStorage, sessionStorage, IndexedDB) held on your own device.
- The chat widget’s visitor identifier (
talkto_anon_id) is minted up front when a page loads. We classify it honestly as a functional / tracking identifier — it is not strictly necessary. - On jiviq.com a cookie banner asks for your consent before the Google Analytics and Microsoft Clarity cookies are set, and the “Cookie settings” link at the foot of every page lets you change your choice. Our product surfaces show no banner; Section 7 explains why.
1. Our approach
We try to keep this simple and honest. We run no advertising, and we set no advertising cookies ourselves. Our product — the admin app, forms, booking pages, hosted chat, calls, meetings and the chat widget — uses no third-party advertising cookies and runs no third-party web-analytics product. Our marketing website, jiviq.com, is the exception: with your consent it uses Google Analytics and Microsoft Clarity (Section 3.4). Those two tools run only on jiviq.com, and only after you agree; when they run, they set cookies on jiviq.com, and Clarity causes Microsoft to set its own cookies on its domains clarity.ms and bing.com, which Microsoft says it also uses for advertising (Sections 3.4 and 4).
What we do use falls into four buckets: storage that is strictly necessary to sign you in and keep the product working; functional storage that remembers your preferences and unsent drafts; on websites where the chat widget is installed, a visitor identifier that powers audience analytics; and, on jiviq.com only and only with your consent, analytics cookies. Section 4 lists every item, key by key.
2. What cookies and browser storage are
A cookie is a small piece of data a website asks your browser to keep and send back on later requests. Browser storage — localStorage, sessionStorage, and IndexedDB — is similar but stays on your device and is read by the page’s own code rather than sent automatically with every request. Our product relies almost entirely on browser storage rather than cookies; the cookies our marketing website sets are listed in Section 4.
- localStorage persists until it is cleared (by you, or by the app).
- sessionStorage is wiped when you close the browser tab.
- IndexedDB is a small on-device database; we use it (via Firebase) to keep account holders signed in.
3. The categories we use
3.1 Strictly necessary
These are required for the service to function — chiefly to authenticate you and keep you signed in. They
cannot be switched off without breaking sign-in. This includes the admin app’s Firebase authentication
session, the chat widget’s visitor session credential, the items that keep a call or a meeting
connected (the call pass, the call device identifiers and the meeting session), and, on jiviq.com, the
cookieyes-consent cookie that remembers your cookie-banner choice.
3.2 Functional
These remember your choices and unsent work — your light/dark theme, UI preferences, cached chrome, and in-progress drafts (including a form’s autosaved answers, which can hold personal data the respondent has typed but not yet submitted). They improve the experience but are not strictly essential.
3.3 The chat-widget visitor identifier
When the chat widget is installed on a website, it stores a persistent identifier,
talkto_anon_id, in that browser’s localStorage. It is a random value — not your
name or email — used to recognise repeat visits and stitch together a visitor’s journey for
audience analytics. To be clear and honest: this is a functional / tracking identifier, and it
is minted up front when the page loads — it is not strictly necessary for you to read a page or
send a message. You can object to this analytics processing (Section 5) and clear it at any time
(Section 6).
3.4 Analytics on our marketing website
Our marketing website, jiviq.com, uses two analytics tools, and only if you agree. Google Analytics (Google LLC) measures visits to jiviq.com: how many people visit, which pages they view and where they came from. Microsoft Clarity (Microsoft Corporation) records how visitors use its pages — clicks, scrolling and a replay of the visit — so we can improve them. Neither tool loads until you click Accept in the cookie banner (Section 7). Until then, Google’s consent mode is set to “denied” and neither Google Analytics nor Clarity is contacted. If you accept, Google Analytics sends its data to Google at the google-analytics.com and google.com domains, and Clarity sends its data to Microsoft at the clarity.ms domain. Both providers receive this data and may process it outside India, including in the United States. We do not use either tool for advertising: Google’s advertising storage stays “denied” even after you accept, and we tell Clarity the same. But Microsoft’s cookies on clarity.ms and bing.com (Section 4) are also used by Microsoft for its own purposes, which Microsoft says include advertising.
The cookie banner is run by CookieYes, a consent-management service. It stores your choice in the
cookieyes-consent cookie (Section 4), and showing the banner and recording your choice contact
CookieYes’s servers (cdn-cookieyes.com and log.cookieyes.com).
What loads before you choose. Besides the banner, two things load on every page of jiviq.com before you make any choice, because the site needs them: our typefaces, from Google Fonts (fonts.googleapis.com and fonts.gstatic.com, run by Google LLC), which sets no cookie but, like any web server, receives your IP address with each request; and our own chat widget, whose items are listed in Section 4 and described in Sections 3.3 and 5.
4. Full inventory
The table below lists every cookie and browser-storage key JIVIQ uses, where it is set, its category, its
purpose, and how long it lasts. Not every key appears for every person — what you have depends on which
surfaces you use (marketing site, admin app, forms, booking pages, hosted chat, calls and meetings, or
the chat widget). A key written with {…} or * stands for a family of keys, one per conversation,
form, business or meeting.
| Key | Where | Type | Purpose | Duration |
|---|---|---|---|---|
talkto_anon_id | Chat widget, on the website where it is installed (a business’s site, or our own) | localStorage — Functional / tracking | Persistent visitor-correlation / journey identifier (a random value, not name or email), minted up front on page load. Not strictly necessary. | Until cleared |
talkto.jwt.*, talkto.exp.* | Chat widget and hosted chat pages | localStorage (sessionStorage in session-only mode) — Strictly necessary | Visitor session credential that keeps a chat session signed in. | 30-day sliding (session-only mode: until the tab is closed) |
talkto.ctx.* | Chat widget and hosted chat pages | localStorage — Functional | Remembers the business’s name, branding and chat settings for your conversation, so it appears straight away on your next visit. | Until cleared |
talkto.widget.chime-muted, talkto.composer.enterToSend | Chat widget and hosted chat pages | localStorage — Functional | Remembers your notification-sound and Enter-to-send preferences. | Until cleared |
talkto.widget.brand.{business}, talkto.widget.watermark.{thread}, talkto.staffBanner.dismissed.* | Chat widget and hosted chat pages | sessionStorage — Functional | Shows the business’s branding before the page has loaded, remembers which messages you have already seen, and remembers that you dismissed a notice. | Session (until tab closed) |
jiviq.form.{key}.responses, jiviq.form.{key}.token | Forms renderer (forms.jiviq.com) | local/sessionStorage — Functional | Autosaves in-progress answers so they are not lost, with the token that stops one submission being recorded twice. Holds whatever personal data the respondent has typed. | 30 days, or cleared on submit |
jiviq.form.beacon.{submission} | Forms renderer (forms.jiviq.com) | sessionStorage — Functional | Notes that this tab has already reported that you started the form, so a reload is not counted twice. | Session (until tab closed) |
jiviq.visitor.jwt | Forms renderer (forms.jiviq.com) | localStorage — Functional | A visitor credential issued when you submit a form. No current feature uses it. | Until cleared; the credential itself expires after 72 hours |
talkto.widget.draft.{thread} | Chat widget and hosted chat pages | sessionStorage — Functional | Remembers an unsent message draft in the composer. | Session (until tab closed) |
jiviq.calls.pass.v1 | sessionStorage, chat.jiviq.com | Strictly necessary | Lets the call window you opened join that one call | Per tab and browser session; removed when the call ends |
jiviq.calls.visitor_device_id | localStorage, chat.jiviq.com, talkto.page | Strictly necessary | Keeps your device recognisable to the call service, so a reconnect is the same participant | Until cleared |
jiviq.calls.mixer | localStorage, chat.jiviq.com, talkto.page, app.jiviq.com | Functional | Remembers your call volume levels | Until cleared |
jiviq.meet.session.{link} | Video meetings (talkto.page) | localStorage — Strictly necessary | Keeps you in a meeting you joined from its link, so a reload does not ask you to join again. | Until cleared; not used once the meeting session has expired |
jiviq.meet.device | Video meetings (talkto.page) | sessionStorage — Strictly necessary | Keeps this tab recognisable to the meeting service, so a second tab joins as a second device instead of replacing the first. | Session (until tab closed) |
booking_session_token | Booking pages (book.jiviq.com) | sessionStorage — Strictly necessary | Keeps you signed in while you make a booking. | Session (until tab closed) |
agent_kernel_echo_state | Booking pages (book.jiviq.com) | sessionStorage — Functional | Keeps the booking assistant’s session details (for example the name you gave it) across a reload of the same tab. | Session (until tab closed) |
jiviq.bookingTz.{business} | Booking pages (book.jiviq.com) | localStorage — Functional | Remembers the time zone you chose for viewing appointment times. | Until cleared |
jiviq.booking.viewed.{business} | Booking pages (book.jiviq.com) | sessionStorage — Functional | Notes that this tab has already counted your visit, so a reload is not counted twice. | Session (until tab closed) |
firebase:authUser:*, firebaseLocalStorageDb | Admin app | localStorage / IndexedDB — Strictly necessary | Account-holder authentication session (managed by Firebase). | Firebase default |
jiviq-theme | Marketing site (jiviq.com) | localStorage — Functional | Remembers your light / dark theme preference. | Until cleared |
cookieyes-consent | Marketing site (jiviq.com), set by CookieYes | Cookie — Strictly necessary | Remembers your cookie-banner choice, or that you have not made one yet, with a random consent identifier. Set when you first open a page. | 1 year |
_ga, _ga_8HYP3Z51GZ | Marketing site (jiviq.com, on .jiviq.com), set by Google Analytics, only after you accept | Cookie — Analytics (with your consent) | Distinguishes visitors and visits for Google Analytics’ visit statistics. | 400 days |
_clck | Marketing site (jiviq.com, on .jiviq.com), set by Microsoft Clarity, only after you accept | Cookie — Analytics (with your consent) | Recognises a returning visitor in Clarity’s reports and replays. | 1 year |
_clsk | Marketing site (jiviq.com, on .jiviq.com), set by Microsoft Clarity, only after you accept | Cookie — Analytics (with your consent) | Links the page views of one visit together in Clarity’s reports and replays. | 1 day |
_cltk | Marketing site (jiviq.com), set by Microsoft Clarity, only after you accept | sessionStorage — Analytics (with your consent) | Identifies this browser tab to Clarity, so one visit’s recordings stay together. | Session (until tab closed); removed from each open jiviq.com tab when you withdraw, at the times in Section 6 |
MUID, SRM_B, CLID, MR, ANONCHK, SM | clarity.ms and bing.com (Microsoft’s own domains, third-party), set by Microsoft when Clarity loads on jiviq.com, only after you accept | Cookie — Analytics, third-party | Microsoft’s cookies for Clarity. MUID is an identifier with the same value on clarity.ms and bing.com, which links Clarity to Microsoft’s Bing identifier. Microsoft also uses these cookies for its own purposes. We cannot delete them (Section 6). | MUID and SRM_B: 390 days; CLID: 1 year; MR: 7 days; ANONCHK: 10 minutes; SM: until you close the browser |
jiviq.calls.device_id | Admin app | localStorage — Strictly necessary | Keeps a team member’s device recognisable to the call service, so a reload rejoins as the same participant and answering on a second device does not disconnect the first. | Until cleared |
admin-me-cache-v2, jiviq.active-workspace.v1, jiviq.all-ws-coachmark.v1, jiviq.proactive.last-workspace.v1, jiviq.chats.chime-muted, jiviq.chats.chime-lock, composer.enterToSend, conversations.draft.{id}.reply, conversations.draft.{id}.internal, jiviq.kb.destination.gap, jiviq.kb.destination.teach-at-close, jiviq.push.subscription.v1, jiviq.pwa.install-dismissed, jiviq.pendingSignup.{uid}, forms.list.view, triage:view, triage:sort:list, triage:sort:board, triage:board:swimlane | Admin app | localStorage — Functional | UI preferences, cached chrome, and saved drafts (e.g. active workspace, sound mute, Enter-to-send, reply and internal-note drafts, list view/sort, push-notification registration, dismissed tips). | Until cleared |
jiviq.kb.team-hint.dismissed.{thread} | Admin app | sessionStorage — Functional | Remembers that you dismissed a knowledge-base tip on a conversation. | Session (until tab closed) |
Note: where the chat widget has optional bot protection enabled (off by default), submitting a message or form may invoke Google reCAPTCHA, which can set its own storage as a fraud-prevention signal. This is conditional, and it is the only third-party item that can appear on our product surfaces. The third-party items on our marketing website are the ones set by CookieYes, Google Analytics and Microsoft Clarity, listed above.
5. The chat widget on tenant websites
The chat-widget items above (talkto_anon_id, the visitor session credential, the composer
draft and the widget’s other items) are stored in the visitor’s browser for the website where
the widget is installed — the visitor identifier in that website’s own storage, and the others in
the storage of the widget’s frame (widget.jiviq.com, or widget.talkto.page on older installations),
which most browsers keep separate for each website. For data captured through the widget on a
business’s site, that business is the controller and JIVIQ acts as its processor — so the
business’s own privacy notice governs how it is used, and the business is responsible for disclosing
the widget and its analytics to its visitors. On our own website (jiviq.com), where we run the widget
for our own support, JIVIQ is the controller.
A visitor can object to analytics processing at any time. We honour an objection under Article 21 GDPR by adding the visitor to a suppression list so that future page views are not analytics-stamped: email support@jiviq.com and we will record the suppression preference, confirming within 30 days. The chat widget uses no third-party advertising or cross-site tracking network.
Video calls from the chat widget. When a business calls you and you answer from
the chat widget on its website, the call opens in a separate window on
chat.jiviq.com. That window keeps a short-lived call pass in that browser tab’s
sessionStorage, removed when the call ends, and the call items that window uses
(jiviq.calls.pass.v1, jiviq.calls.visitor_device_id and jiviq.calls.mixer) live in chat.jiviq.com’s storage. The browser remembers the camera and microphone permission you grant for chat.jiviq.com.
You can revoke that permission in your browser’s site settings. On our servers, the
one-time link that opened the call window is kept as pseudonymous identifiers — no name,
email or message. It stops being needed within five hours of being used (within minutes if
it is never used), and it is removed the next time anyone taps Join on a call from that
business’s chat widget, or opens a call window from one; until then it can stay. Asking us
to erase your data, or the business’s account being deleted, also removes it.
6. How to control or clear these items
- Cookie settings on jiviq.com — the “Cookie settings” link at the foot of every page of jiviq.com reopens the cookie banner, where you can accept or refuse analytics at any time. If you withdraw, Google Analytics and Microsoft Clarity stop in every jiviq.com tab open in that browser, and we erase their cookies on jiviq.com (
_ga,_ga_8HYP3Z51GZ,_clckand_clsk) and Clarity’s_cltktab marker: at once in any tab that is running, and, in a tab your browser has paused in the background or in a browser too old to pass the message between tabs, as soon as that tab is shown again or opens another page; Microsoft’s own cookies on clarity.ms and bing.com sit on Microsoft’s domains, so you clear those in your browser. - Browser settings — every major browser lets you view and delete cookies and site storage, and block them per-site. Doing so for JIVIQ’s surfaces will sign you out and reset your preferences and drafts.
- Clear site storage — clearing storage for a site removes its localStorage, sessionStorage, and IndexedDB entries, including the chat-widget identifier on a tenant site.
- Analytics suppression list — to stop your activity being analytics-stamped, email support@jiviq.com and we will add you to the suppression list (Section 5). This is separate from clearing storage, because a cleared identifier is simply re-minted on your next visit.
Because almost everything we use is functional or strictly necessary, blocking it does not remove advertising (we run none) — it mainly affects sign-in, saved preferences, and unsent drafts. Refusing analytics on jiviq.com does not change how the site works.
7. Consent posture
On jiviq.com, a cookie banner asks for your consent before the Google Analytics and Microsoft
Clarity cookies are set. Until you click Accept, neither tool is loaded, and Google’s consent mode
starts at “denied”; if you refuse, or never choose, they never load. You can change your choice at
any time from the “Cookie settings” link at the foot of every page, which reopens the banner.
Withdrawing stops both tools and erases their cookies on jiviq.com and Clarity’s _cltk tab marker, in
every jiviq.com tab open in that browser, at the times Section 6 sets out; Microsoft’s cookies on its own
domains stay until you clear them in your browser (Section 6). The banner covers analytics only: the
cookie that records your choice, our fonts and our own chat widget load without it (Section 3.4).
Our product surfaces show no banner, because the storage they use is strictly necessary or
functional. The one item that is neither — the chat widget’s talkto_anon_id visitor identifier —
is honestly classified as functional / tracking above, and we offer an objection / suppression route
(Section 5) rather than relying on a banner. That is also true of the chat widget on jiviq.com: the
cookie banner does not control it.
Where the widget runs on a tenant’s website, the tenant is the controller and is responsible for any consent mechanism its own jurisdiction requires before that storage is set. We keep this posture under review and will introduce a consent mechanism if the law applicable to a surface requires one.
8. Changes to this policy
We may update this Cookies & Local-Storage Policy as the product evolves — for example, if we add or remove a stored item or change a sub-processor. Material changes will be announced by email or in-product notice, and the “last updated” date below the title will reflect the most recent version.
9. Contact
This service is operated by Stratus Labs (registered address: C4 602, Edenn Towers CHS, Pune 411057, India). For questions about this policy, to object to analytics processing, or to reach our Data Protection Officer, email support@jiviq.com.