Cookie Policy

Overview

This Cookie Policy explains how UserTrail uses cookies and similar technologies on the UserTrail website, dashboard, and tracking script.

Dashboard cookies and storage

• UserTrail does not currently set first-party cookies in the dashboard source code we audited. The dashboard uses browser localStorage for authentication and preferences.
• usertrail_auth_token: localStorage; essential; stores the dashboard authentication token; kept until logout, account deletion flow, or browser storage clearing.
• usertrail_user_email: localStorage; essential/account display; stores the signed-in user's email for dashboard display and cached bootstrap state; kept until logout, account deletion flow, or browser storage clearing.
• usertrail_timezone: localStorage; functional preference; stores the user's timezone for dashboard reporting; kept until logout, account deletion flow, or browser storage clearing.
• usertrail_sidebar_collapsed: localStorage; functional preference; remembers whether the dashboard sidebar is collapsed; kept until changed or browser storage clearing.
• usertrail_open_add_site_modal: localStorage; functional routing flag; temporarily opens the add-site modal after navigation; removed after use.

Tracker storage audit

• _hm_session_id: sessionStorage; analytics/session identifier; identifies one browser session for analytics and replay correlation; kept for the browser session.
• _hm_visitor_id: localStorage; analytics/visitor identifier; recognises a returning visitor on the same browser; kept until browser storage clearing.
• _hm_should_record_{siteId}: sessionStorage; analytics/replay sampling; remembers whether the current session should be recorded for a specific site; kept for the browser session.
• _ut_survey_{surveyId}_{id}: localStorage or sessionStorage depending on the customer's survey persistence setting; functional/survey persistence; prevents repeatedly showing the same survey; kept for the browser session when persistence is per visit, or until browser storage clearing when persistence is per user.

Customer website tracking

Customers control whether and when the UserTrail tracking script is loaded on their own websites. If consent is required, customers should not load tracker.js until consent has been granted. Customers can implement this by dynamically adding tracker.js after their consent management platform or custom consent flow confirms permission.

Analytics and behaviour data

• The tracker may collect behaviour signals such as page views, clicks, scroll depth, movement samples, session identifiers, device metadata, and timestamps.
• Customers are responsible for explaining this tracking in their own privacy and cookie notices.
• Customers are responsible for obtaining consent before non-essential analytics or behavioural tracking where applicable.

Strictly necessary cookies

Some storage is necessary for authentication, security, service delivery, and dashboard functionality. These may be used without consent where permitted by law. Tracker analytics storage should only be created on customer websites after the customer has loaded tracker.js in accordance with their consent obligations.

Managing cookies

Dashboard users can control browser cookies through browser settings. Customer website visitors should use the cookie preferences provided by the customer website or browser-level controls.

Contact

For cookie questions, contact info@usertrail.io.