Cookie and local storage policy
Stay in control of your preferences
Cookies are small files stored by your browser. Local storage and technical identifiers can also remember information on your device. This page explains their uses on the Wavize website and in its assistant.
Updated 6 September 2026
1. Accept, refuse or change your choice
On the public wavize.com website, statistics and marketing categories are off before you choose. You can accept, refuse or customise them. Use “Cookie preferences” to change your choices at any time.
On wavize.com, the Wavize widget loads directly with the page, independently of your statistics and marketing cookie choices. These choices do not disable the widget or erase its conversation storage. The data and ways to request erasure are described in the privacy policy.
2. What may be stored
| Item | Purpose and duration |
|---|---|
| wavize_cookie_consent | Records your choices by category, notice version and date. First-party cookie, 180 days for both acceptance and refusal. |
| Website session and form protection | Authentication and security, including the Laravel session cookie and XSRF-TOKEN when these functions are used. Duration follows the configured session; these are not advertising trackers. |
| Assistant local storage | Identifiers such as chatbot_session_token_*, chatbot_session_id_*, session_start_time_*, active_session_* and conversation keys. These resume sessions and history according to enabled features. Browsers impose no automatic expiry on local storage: it may remain until deleted, replaced by widget session controls or cleared in browser site settings. |
| Optional statistics and marketing | These categories are not preselected. This version’s consent manager adds no advertising or external audience measurement tool. Any later addition must respect your choice and be documented. |
| Requested services | A payment, login, security feature or integration may require its provider’s cookies when used. Read the information displayed by that service as well. |
3. On a WordPress site or store
Each website operator is responsible for notices and permissions on their own site. The Wavize connector can defer widget loading according to its consent setting and the site’s consent manager. Choices on wavize.com do not provide consent on customers’ sites, or vice versa.
WooCommerce API keys enable secure server-to-server connections; they are not visitor cookies. The data accessed through this connection is described in the privacy policy.