Cookies
Policy.

About this policy

This Cookies Policy explains cookies and similar storage used by the TruCom website, application and website chat tools. TruCom is provided by Truvenda Cloud Technologies. The storage involved depends on the page you visit, the features you use and the configuration of the business operating a chat widget.

Information that can identify a person is also handled under our Privacy Policy. This page explains browser storage; it does not replace that policy or provide consent for an activity that needs your separate permission.

What cookies and similar technologies do

A cookie is a small value stored by your browser and sent with relevant requests to a website. It can connect requests to the same session or retain a preference. A cookie does not give a website unrestricted access to the files on your device.

Local storage holds values for a website or embedded origin between visits. Session storage usually lasts for the page session in a browser tab. Unlike a cookie, these values are read by the relevant website code rather than automatically attached to every request. Browser restrictions, restoration settings and private browsing can affect how long they remain.

An installed web app can also cache selected public assets for an offline screen and store notification permissions or subscription details. These serve different purposes from an advertising tracker, even though they also involve information on a device.

Why we use browser storage

We use storage for the specific function it supports. A preference or chat feature should not be treated as permission to add an unrelated tracking purpose. Whether a use requires consent or meets an exception depends on its purpose and the law that applies.

Access and request security

Session information and request-verification values help recognise an authenticated session and protect forms and account actions.

Blocking these can prevent sign-in or cause a form submission to fail.

Interface preferences

Theme and device-layout values help show the light or dark theme and the appropriate native layout.

Clearing them can reset your preferences or cause the layout to be selected again.

Chat continuity

Browser and conversation references help a widget recognise a returning browser, resume an authorised chat and manage pending messages.

The business using the widget controls relevant chat settings and must explain its use to its visitors.

Installation and offline use

Public asset caches and installation-prompt preferences support the installed app and avoid repeatedly showing the same prompt.

Clearing them can remove offline assets or cause an introduction or prompt to appear again.

Website and account storage

The following entries describe the first-party storage used by the relevant TruCom pages. Some names and session lifetimes depend on the deployment. A lifetime describes browser or session behaviour, not the retention period for every server record.

Session cookie

A deployment-specific cookie, typically trucom-session, links requests to the server session and account state.

Its lifetime follows the configured session settings. Activity can renew it, and server access can expire or be revoked before a browser value disappears.

XSRF-TOKEN

A request-security cookie can support verification of forms or application requests. It is not an advertising identifier.

Its availability and lifetime follow the session and request-security configuration.

trucom_device_experience

A cookie stores whether to use the desktop or mobile experience.

The public layout sets a 30-day lifetime and refreshes the value when it is selected again.

trucom-theme

Local storage remembers the light or dark theme you choose.

It has no automatic time-based expiry in the theme code; it can be replaced by a new choice or removed by clearing site data or browser cleanup.

trucom-device-shell-reload

Session storage helps avoid repeated reloads while the browser selects a device layout.

It is removed when the layout settles, or ends with the browser page session, subject to browser restoration behaviour.

Storage used by website chat

Where a website uses TruCom chat, storage can exist on that website and on the origin serving the embedded chat. Names containing a widget or conversation identifier distinguish the business or conversation involved. Storage access can vary when a browser blocks embedded-site storage.

Conversation references and pending messages can relate to a person. Keep access to a shared device secure, and do not copy or send stored token values to someone asking for a password, recovery code or chat credential.

trucom-browser-id

A local-storage browser reference helps recognise visits from the same browser.

It has no built-in browser expiry and can remain until cleared or removed by the browser. The associated server records have separate retention rules.

trucom-widget-session:<widget>

A conversation-access reference is kept in local storage or session storage according to the widget’s remember-conversation setting. A related :visit value may be removed when session state changes.

A persistent value can remain until cleared or reset. Server session-validity limits apply separately, so retaining a value does not guarantee continued access.

trucom-widget-outbox:<widget>

Pending chat messages can be stored on the device so the widget can retry delivery after a connection problem.

The outbox filters out pending items older than seven days when it is loaded; delivered items are removed through normal processing. A browser entry can remain until processed or cleared.

trucom-widget-config:<widget>

Local storage can cache public widget configuration to support a usable launcher when a connection is interrupted.

Cached configuration older than 24 hours is discarded when read. This check does not itself make a browser erase an unused entry at the 24-hour mark.

Widget interaction preferences

Keys beginning trucom-widget-opened:, trucom-widget-active-conversation: and trucom-widget-feedback-skipped: remember relevant interaction state.

Local values persist until the feature clears or replaces them, you clear site data or the browser removes them. An active-conversation flag is removed when that state ends.

trucom-widget-trigger-shown:<widget>

Session storage records that a chat prompt has already been shown.

It normally lasts for the tab’s page session, subject to browser restoration behaviour.

Installed app and notification storage

When the web app is used, trucom-pwa-install-dismissed-at can remember dismissal of the installation prompt. The prompt checks whether dismissal was within the previous day. trucom-pwa-intro-until records a seven-day introduction period. Those checks control what is shown; stored values may remain until updated, removed or cleared.

The service worker caches selected public brand assets, the web manifest and an offline screen in a versioned browser cache. Cached assets can remain until replaced by an update, evicted by the browser or removed through site-data settings. This asset cache is separate from customer support records held by a workspace.

Browser notifications require the relevant permission and subscription. You can change notification permission in your browser or device settings. Removing permission or an installed app does not by itself close a TruCom account or delete server records.

Connected providers and other websites

Google sign-in, a configured Cloudflare Turnstile challenge or a payment page can involve storage or device checks controlled by the relevant provider. The provider’s own notice explains the purposes, duration and choices for information it controls. The exact entries depend on which service is used and its current settings.

A business that installs TruCom chat remains responsible for the other cookies, analytics, advertising or embedded services on its own website. This policy describes TruCom’s tools and does not describe every technology that business may use.

Following a link to another service takes you to a separate website or application with its own storage practices. Your choices for that service may need to be made there.

Consent and your choices

Where applicable law requires consent for a storage purpose, that consent must be obtained before the activity begins. A notice about a cookie, agreement to our Terms or continued browsing is not a substitute for a valid choice.

Storage needed for a requested service or a permitted exception must be assessed for that specific purpose. If optional measurement or advertising is introduced, the relevant information and choices must cover that activity. A saved theme or conversation preference does not grant permission for an unrelated purpose.

You can change a browser permission, clear stored information or contact us about a privacy concern. Where a separate consent control is provided for a particular activity, use that control to change the choice as well. Clearing a value alone may not communicate a withdrawal to every organisation involved.

How to manage or remove stored information

Open your browser’s privacy or site-settings controls, find the relevant website and review its cookies, stored data, permissions and cache. For embedded chat, you may need to review both the business website and the origin serving the widget. Browser menus vary by device and version.

You can remove an individual website’s data, block specified storage or clear wider browsing data. On a shared device, sign out before leaving it and check saved credentials and permissions. Private browsing and automatic cleanup can reduce persistence, but do not guarantee that no server record is created.

To change theme, use TruCom’s theme control. To stop notifications, change the browser or device permission. To remove installed-app assets, use the browser’s site-data or installed-app controls. You can choose the particular setting you want to change rather than clearing unrelated websites.

What changes when you clear storage

You may be signed out, lose a saved theme, see an installation prompt again or lose the device reference used to return to a previous chat. Clearing a pending outbox before delivery can remove an unsent message, so check that an important message was delivered first.

Clearing browser data does not delete messages already delivered to a business, invoices, audit records or other server-held information. A separate privacy or account-deletion request addresses those records and the organisation responsible for them.

Changes to this policy

We review this policy when storage purposes, relevant features or legal requirements change. The effective date and version identify the published notice. A new purpose requiring consent must be addressed through the relevant choice; publishing a revised policy does not supply that consent.