Privacy & Data

The Trackelio widget captures contextual data alongside user submissions to help your team understand and reproduce issues. This page documents exactly what is collected and the safeguards in place.

Automatically captured data

Page metadata

Every submission includes metadata about the page the user was on:

Data	Description
URL	The full page URL at the time of submission.
Title	The document title.
Referrer	The referring URL, if available.
Viewport	The browser viewport dimensions (width and height).
Scroll position	How far down the page the user had scrolled.

Browser information

Data	Description
Browser name	e.g., Chrome, Firefox, Safari.
Browser version	The specific version number.
Operating system	e.g., Windows, macOS, Linux, iOS, Android.
User agent	The full user agent string.

Session token

A UUID is generated and stored in localStorage to maintain session continuity across page reloads and navigations. This token is not tied to any personal information unless the user is explicitly identified via the SDK identify() method.

Selected element data

If the user selects an element using Mark Mode, the submission includes the CSS selector, XPath, bounding rectangle, and click coordinates for that element. See Visual Feedback for details.

Console logs

The widget captures the last 50 console log entries at the time of submission.

Field	Description
Level	The log level (log, warn, error, info).
Message	The logged message content.
Timestamp	When the log entry was created.

Trackelio’s own internal console output is excluded from this capture.

Network logs

The widget captures the last 30 failed network requests (non-2xx responses) at the time of submission.

Field	Description
Method	HTTP method (GET, POST, etc.).
URL	The request URL.
Status	The HTTP status code returned.
Duration	How long the request took in milliseconds.

Requests made to Trackelio’s own API are excluded from this capture.

Privacy protections

Password field filtering

Password input fields (<input type="password">) are automatically excluded from screenshot captures. Their values are never read or transmitted.

data-sensitive attribute

Add the data-sensitive attribute to any HTML element to block it from being captured in screenshots:

<div data-sensitive>
  Sensitive content hidden from screenshots.
</div>

Widget exclusion

The widget’s own DOM subtree is excluded from screenshot captures so it does not appear in the image.

Shadow DOM isolation

The widget renders inside a Shadow DOM root. This provides CSS isolation between your site and the widget, preventing style conflicts in either direction.

Session reset

Users or your application can clear all stored session data at any time:

window.Trackelio.reset();

This removes the session token from localStorage, clears the identified user, and closes the widget panel.