OPERATIONAL DRAFT · UPDATED 2026-08-13

Cookie and Tracking Notice

The current Ring2 site does not install third-party advertising or general-purpose analytics tags. It records limited first-party attribution across the account, demo and partner conversion paths.

Current first-party signals

• UTM source, medium, campaign, term and content.
• Referrer, landing path, random visitor ID and random session ID.
• Page view, conversion CTA click, demo play, form start, form submission and confirmed booking.
• Country or region, conversion path, role, source, target scenario, expected call volume and engagement type after the visitor provides them.
• Server-side account, demo and partner request records and authorized lifecycle or follow-up changes.

Purpose

These signals connect an initial visit to a later Lead ID, show which sources produce registrations or assisted conversations, and support follow-up from lead capture through payment. A button click is not recorded as a booking unless a connected booking system confirms it.

Local browser storage

Ring2 stores a random visitor ID in local storage and a random session ID plus a one-page-view marker in session storage. The protected lead database stores the current administrator authorization value in session storage after sign-in. The Brand Plan separately stores its local review checklist. The current site does not use these values for third-party advertising or cross-site tracking.

Future analytics

Before adding analytics, advertising pixels, session replay or cross-site tracking, Ring2 must update this notice, define retention and lawful basis, and add a consent mechanism where required.

Contact

The final privacy contact will be inserted before production launch.