Cookies Policy

This page explains how we use cookies and similar technologies.

Last updated: 2026-01-08

1. What We Use

We use cookies and local storage to keep the Service working and to understand how it is used. We currently use session replay analytics (OpenReplay) to improve user experience.

In our current OpenReplay integration (SDK v17.0.0), the tracker primarily uses browser storage (sessionStorage/localStorage) rather than first-party cookies.

2. Categories

  • Essential: required for basic functionality and security.
  • Analytics: session replay and usage data to improve performance and content.

3. Your Controls

You can control cookies through your browser settings. Blocking cookies may affect some features of the Service. For more details on data usage, see the privacy policy.

4. OpenReplay storage keys

OpenReplay may store the following keys in your browser:

sessionStorage

  • _openreplay_token — session token (cleared when the browsing session ends). Some installations may use __openreplay_token.
  • _openreplay_pageno — page counter within a session. Some installations may use __openreplay_pageno.
  • _openreplay_reset — internal flag for session resets. Some installations may use __openreplay_reset.
  • _openreplay_tabid — tab identifier. Some installations may use __openreplay_tabid.
  • __or__watched_tags__ — internal tag tracking for analytics.

localStorage

  • _openreplay_uuid — anonymous device/user identifier (persists until you clear site data). Some installations may use __openreplay_uuid.
  • or_buffer_1 — temporary offline buffer used by the tracker (may persist until uploaded/cleared).

You can inspect or clear these items in your browser DevTools → Application/Storage (Local Storage / Session Storage) for this site.