Help CenterInsightsWhat Information Vyro Insights Captures
Back to Insights

What Information Vyro Insights Captures

Last updated March 12, 2026

Overview

Vyro Insights helps you understand how visitors interact with your showroom — which vehicles they view, what they click on, and how they navigate your site. This article explains what information is collected and how it is handled, so you can share this with your privacy or legal team if needed.

Where Your Data Lives

Vyro operates data centres in multiple regions, so you can choose a location that suits your compliance requirements:

Region Location
Europe Frankfurt, Germany
Asia Pacific Sydney, Australia
United States Oregon, USA

If your business operates under GDPR and you want data to stay within Europe, you can select the EU region.

What Vyro Insights Tracks

Insights collects three types of records:

  • Visitor — an anonymous identifier for a browser (not a named person)
  • Session — a single visit, linked to a visitor
  • Event — an action taken during a session (e.g. viewing a page, clicking a button)

Passwords, payment details, and sensitive personal data are never collected.

Information Collected During a Visit

Device and Browser Details

When someone starts a session, Insights records basic technical context about their device:

  • Browser type and version
  • Preferred language
  • Screen size
  • Timezone
  • IP address (captured server-side)

Page Views

Each time a visitor loads a page, Insights records:

  • The URL of the page
  • The page title
  • The referring page (where they came from, if available)

Clicks

Clicks are only tracked on interactive elements such as links, buttons, and form fields. For each click, Insights records:

  • The URL of the page
  • The type of element clicked (e.g. button, link)
  • The text on the element
  • Where on the screen the click occurred

Conversions and Engagement

If your showroom has specific goals set up (such as a finance enquiry or a test drive booking), Insights can record when those goals are completed. These events include:

  • The name of the goal
  • The URL where it occurred
  • Any additional context your team has configured

Browser Storage

Insights stores two anonymous tokens in the visitor's browser to link visits together over time. These are not linked to a person's name or identity — they are random identifiers used only to connect sessions.

  • A visitor token that persists for up to 6 months
  • A session token that expires after the visit ends (within 1 hour)

Privacy Safeguards

Consent Controls

Insights supports consent gating. If you have a consent banner configured, tracking will not start until the visitor has accepted. All consent conditions must be met before any data is collected.

Anonymous by Default

Visitors are tracked using random identifiers, not names or email addresses. Personal identity is only linked if your platform explicitly connects a signed-in user's account to their visit history.

Your Showroom Only

Insights validates that data is coming from your registered showroom domain before accepting it. Data from unknown or unregistered domains is rejected.

Sensitive Pages Are Excluded

Certain pages related to authentication (such as login callbacks and logout pages) are automatically excluded from tracking.

Short-Term Raw Data Retention

Raw visit data is held for 14 days before it is processed into your analytics reports. After processing, the raw records are removed.

What Is Not Collected

Vyro Insights does not collect:

  • Passwords or login credentials
  • Payment card details
  • Government-issued ID numbers
  • Any special-category personal data under GDPR

Important: If your team configures custom goal tracking with additional metadata, take care not to include personal information in those fields unless you have a documented legal basis for doing so.

Summary for Privacy and Legal Teams

Vyro Insights can be described as:

  • Behavioural analytics — focused on how people use your showroom, not who they are
  • Anonymous by default — visitors are identified by random tokens, not personal details
  • Consent-aware — can be configured to only run after explicit visitor consent
  • Region-flexible — data can be kept within the EU, APAC, or US depending on your requirements

For clients with GDPR obligations, we recommend selecting the EU data region and enabling consent gating as a baseline configuration.

Was this article helpful?