Privacy and data

Understand Callra's privacy-oriented defaults, what data is stored, and what public sharing exposes.

Callra is designed to be privacy-friendly by default, but you are still responsible for your own legal, policy, and disclosure requirements.

Privacy defaults

By default, Callra avoids common tracking behaviors many teams do not want:

no visitor ID cookie used as a cross-site identifier
no raw IP storage in analytics tables
no raw user-agent storage in analytics tables
no localStorage or sessionStorage identifier requirement
no URL fragment storage
no query-string storage by default

DNT and GPC

Each site can be configured to respect:

Do Not Track (DNT)
Global Privacy Control (GPC)

When enabled, Callra drops tracker bootstrap requests and collector requests that advertise these signals, and the shared snippet also renders with data-do-not-track="true" for that site.

What Callra does store

To make the dashboard useful, Callra stores normalized analytics dimensions such as:

path
route template when provided
page title
referrer domain and, in private dashboards, exact referrer URL where available
country code
device type
browser name
operating system name
environment label
UTM values
custom event names and flat event properties
site-scoped visitor and session hashes used for grouping

These values are intended for analytics, not personal identity.

Anti-abuse protection

Callra may set a short-lived HttpOnly cookie on the analytics origin to make replay abuse harder.

This is not designed as an advertising identifier or a cross-site tracking cookie.

Public share links expose aggregate metrics only.

They are intended for safe reporting, not for exposing raw browsing activity.

Private dashboard features such as settings and recent-event inspection stay behind authenticated access.

Your responsibility

If you run Callra for customers, employees, or the public, review your own:

consent policy
privacy policy
retention policy
internal access controls

Callra helps minimize unnecessary collection, but compliance decisions still belong to the operator.