Storage, cookies and privacy
One cookie on your domain, and its copy
The SDK sets one cookie per project on your domain, orka_session_<project id>, with a copy under the same name in the localStorage of your page. It writes nothing else on your domain.
| Cookie | Content | Lifetime |
|---|---|---|
orka_session_<project id> |
Visitor ID, conversation ID, access token and its expiry | 1 year (Safari: 7 days after the last visit) |
It is a first-party cookie set by the SDK script (SameSite=Lax, Secure on HTTPS), on the widest domain your browser accepts: example.com for a page on www.example.com, so that www.example.com and app.example.com share the session. On a domain where that is not possible (your-shop.myshopify.com), it is set on the hostname only.
The cookie goes first. The copy, kept for each hostname, brings the session back when the cookie is gone, and the cookie is then written again.
The widget iframe (widget.orka.chat) keeps the state of the window in its own localStorage, which browsers keep separate for each site:
| Key | Content |
|---|---|
orka_window_<project id> |
Chat open or closed, draft message, notifications dismissed |
orka_userdata_<project id> |
The last identity and attributes sent with update(), to avoid sending them again |
orka_last_page_<project id> |
The last page sent, to avoid duplicates |
Consequences:
- A session belongs to your domain in one browser: the subdomains of your domain share it, another domain starts another session. Session continuity joins them for logged-in users.
- Clearing the data of your site (cookies and storage), or a private window, starts a new visitor. With the storage of your site blocked, every page starts a new visitor.
- If your consent tool manages the cookies and the storage of the page, declare
orka_session_*as a functional item of the chat. To store nothing before consent, load the SDK only once accepted (see below). Orka.reset()removes the cookie, its copy and the keys of the iframe.
What is collected
When the widget loads, and before any message is sent:
- IP address, and the city-level location derived from it
- Browser, operating system, device type
- Browser language and timezone
- The pages viewed (URL and title), five are kept
- What you send with
ORKA_SESSIONandOrka.update()
Never send secrets, passwords or payment data as custom attributes: your whole team can read them.
Ask for consent first
If your cookie policy requires consent before any of this, load the SDK without starting it:
window.ORKA_LOAD = false;
Nothing is collected and no session is created until you call:
onConsentAccepted(function () {
window.Orka.load();
});
Delete the data of a person
From your back end, with DELETE /contacts/{id} of the REST API: it deletes the contact with their conversations, messages, notes and events. DELETE /conversations/{id} deletes one conversation only.