Privacy

Who we are

Trackela provides website analytics and revenue-attribution tools for product teams. Customers install our first-party script on their sites; events are sent to Trackela’s servers and shown in the customer’s dashboard.

Roles (controller vs processor)

• Website owners (our customers) decide to run tracking and are typically the data controller for visitor analytics on their sites.
• Trackela processes that data on their behalf as a processor (subject to a DPA when required).
• For Trackela account data (email, login), Trackela is the controller.

What the tracker collects

Depending on configuration, events may include: page URL/path, referrer, UTM and ad click IDs, language, timezone, screen size, custom event names/properties you send, and optional identify fields (e.g. user id / email) when you call trackela.identify.

We do not store raw IP addresses with analytics events. Country may be inferred from edge geo headers when available.

Default mode (cookies)

The default script uses first-party cookies and localStorage (trackela_vid, trackela_sid, trackela_sat) so we can recognize returning visitors and attribute revenue across days.

In the EU/EEA/UK, this mode often requires a cookie banner / consent mechanism under ePrivacy / GDPR, depending on your use case. Customers are responsible for their consent UI and disclosures.

Cookieless mode

Add data-cookieless="true" on the script (or pick Cookieless on the Tracking page). Then:

• No Trackela analytics cookies are set.
• No localStorage visitor IDs — only short-lived sessionStorage for the current tab.
• Visitor IDs rotate about once per UTC day (weaker returning-visitor and long-term revenue attribution).
• Cross-domain URL identity params (_g_vid / _g_sid) are not used.

Cookieless mode is designed so you typically do not need a cookie banner specifically for Trackela cookies. You may still need disclosures or banners for other tools on your site. This is not a guarantee of full GDPR compliance.

Which mode should I use?

Opt-out & filtering

End users can set localStorage.setItem("trackela_ignore", "true") to stop the script. We also skip obvious bots and (by default) localhost / file:// / iframes.

Retention

Raw event retention is configured per website (default often 30 days on free plans). Aggregated dashboard stats may be retained longer. Account emails remain while the account exists.

Contact

Privacy questions: use the email on your Trackela account / support channel. For a Data Processing Agreement (DPA), contact us before processing EU personal data at scale.