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, our public forms (forms.jiviq.com), 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).
- We use no third-party advertising cookies, and we run no third-party web-analytics products — specifically, we do not use Google Analytics (no GA, gtag), nor Plausible, PostHog, Mixpanel, Segment, or Hotjar.
- We use cookies and browser storage for three things only: signing you in, remembering your preferences and drafts, and — through the chat widget — audience analytics.
- Most of what we use 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. - We do not currently show a consent banner; Section 7 explains this plainly.
1. Our approach
We try to keep this simple and honest. JIVIQ does not load advertising networks, and it does not embed any third-party web-analytics product. In particular, we do not use Google Analytics (no gtag or GA tags), and we do not use Plausible, PostHog, Mixpanel, Segment, or Hotjar. There are also no HTTP cookies set for analytics.
What we do use falls into three buckets: storage that is strictly necessary to sign you in and keep the product working; functional storage that remembers your preferences and unsent drafts; and, on websites where the chat widget is installed, a visitor identifier that powers audience analytics. 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. JIVIQ relies almost entirely on browser storage rather than cookies.
- 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 and the chat widget's visitor session credential.
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).
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, or the chat widget).
| Key | Where | Type | Purpose | Duration |
|---|---|---|---|---|
talkto_anon_id | Chat widget (on tenant sites) | 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.*, jiviq.visitor.jwt | Chat widget | localStorage — Strictly necessary | Visitor session credential that keeps a chat session signed in. | 30-day sliding |
jiviq.form.{key}.responses | Forms renderer (forms.jiviq.com) | local/sessionStorage — Functional | Autosaves in-progress answers so they are not lost. Holds whatever personal data the respondent has typed. | 30 days, or cleared on submit |
talkto.widget.draft.{thread} | Chat widget | sessionStorage — Functional | Remembers an unsent message draft in the composer. | 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 & admin app | localStorage — Functional | Remembers your light / dark theme preference. | Until cleared |
admin-me-cache-v1, jiviq.active-workspace.v1, jiviq.chats.chime-muted, jiviq.chats.chime-lock, composer.enterToSend, conversations.draft.{id}.reply, jiviq.pendingSignup.{uid}, triage:view, triage:sort | Admin app | localStorage — Functional | UI preferences, cached chrome, and saved drafts (e.g. active workspace, sound mute, Enter-to-send, reply drafts, list view/sort). | Until cleared |
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 is the only third-party item that can appear.
5. The chat widget on tenant websites
The chat-widget items above (talkto_anon_id, the visitor session credential, and the
composer draft) are stored in the visitor's browser on the tenant's own website, not on
jiviq.com. 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.
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. We do not use any third-party advertising or cross-site tracking network.
6. How to control or clear these items
- 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.
7. Consent posture
We want to be straightforward about this: JIVIQ does not currently display a cookie consent
banner. We take that posture because we use no advertising or third-party analytics trackers,
and the storage we do use is either 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.
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.