Widget Cookie and Storage
What the Widget stores on a visitor's device, why, how long, and which consent bucket it falls in. Functional storage makes the Widget work and is set on first interaction. Marketing storage is deny-by-default and set only where a valid consent signal permits it.
| Name | Type | Purpose | Duration | Bucket |
|---|---|---|---|---|
| sa_vid | First-party cookie (server-set, HttpOnly) | Stable visitor identifier so a conversation and its outcome can be attributed and de-duplicated | Up to ~400 days | Functional for operation; Marketing when used for attribution |
| Visitor context | localStorage | Remembers the current session spine so the experience is continuous | Until cleared | Functional |
| Consent state | localStorage | Remembers your consent choices so they are respected and not re-asked | Until cleared or changed | Functional (strictly necessary) |
| Attribution parameters | localStorage | Holds campaign parameters and click identifiers for conversion measurement | Short-lived; only when Marketing consent is granted | Marketing |
| Widget UI state | localStorage | Remembers open/closed and theme preferences | Until cleared | Functional |
Strictly-necessary storage is set without prior consent, as permitted by e-privacy rules. Marketing storage is not set until a valid consent signal permits it, and is cleared on withdrawal or on a recognised opt-out such as the Global Privacy Control. The sa_vid cookie is first-party to the installing business's domain and is not a cross-site tracking cookie. The visitor "Your data" panel lets you clear this storage.