Cookie policy
This website sets no cookies. It loads no analytics, no advertising tags, no heatmaps and no session recording, and it makes no request to any third party. That is why you were not asked to dismiss anything on your way in.
The chat in the corner of every page is TalkTill itself, embedded exactly as our customers embed it, from our own API. It sets no cookies either. If you open it, it keeps the state in the table below in your browser, and nothing else.
We measure how the site is doing from server-side request logs, which are aggregated and hold no identifier that would let us follow one person between pages.
The one exception, and it is opt-in
The demo scheduler on the demo page is hosted by a third party and may set a cookie. It is not loaded until you press a button that says so, and the page names the host it will contact before you press it. If you never press it, nothing third-party is requested.
What the widget stores on your site
A different question, and worth separating. When one of our customers embeds the assistant on their site, it keeps a small amount of state in the visitor's browser so a conversation survives a page change. None of it is a cookie:
| What | Where | Why | Life |
|---|---|---|---|
| The conversation, with its session token | localStorage | Continues the same chat across pages and tabs of one visit | Deleted when the chat ends; ignored after 30 minutes idle |
| Browsing id | sessionStorage | Keeps a saved chat to this visit, so the next person on a shared device does not see it | Until the tab closes |
| Language chosen | localStorage | Answers in the language the visitor picked | Until cleared |
| Help prompt shown | sessionStorage | Not showing the "need help?" prompt twice in a visit | Until the tab closes |
| Cart token | Held server-side against the conversation | Keeps a basket built in chat available to the store's checkout | With the conversation |
None of these is used for advertising or cross-site tracking, and none identifies a visitor across different customers' sites. Under both the GDPR and India's DPDP rules, storage strictly necessary to provide a service the user has asked for does not require consent, but a deployer whose own cookie notice lists everything on their site should list these too.
If we ever add analytics that needs consent
We would rather not, and the position above is deliberate. Were that to change, we commit that: nothing non-essential would load before consent; Accept and Reject would carry equal visual weight; the choice would be remembered for 12 months; and the preference would remain reachable from the footer permanently. A Reject button harder to find than Accept is not consent, and we would not ship one.
Related
The privacy policy covers everything else we collect, and the sub-processor list names every third party involved.