Privacy defaults
You get all of this without any configuration:Opt users out
If your app has a cookie consent banner or privacy settings page, useoptOut() to stop all tracking when a user declines:
optOut() does two things immediately:
- Stops all event capture — no more data is sent
- Persists the opt-out preference in
localStorage
Opt users back in
optIn() clears the opt-out flag. Tracking resumes on the next page load.
Check opt-out status
Use this to show or hide consent UI based on whether the user has already opted out:Full consent flow example
Block elements from replay
If there are specific elements on your page that should never appear in session recordings, add thetl-block class:
Destroy the tracker
Calldestroy() to completely remove Tracelit from the page — all event listeners are removed, all monkey-patched globals are restored, all timers are cancelled, and any buffered events are flushed:
optOut() which persists across page loads).
GDPR summary
How do I handle user deletion requests?
How do I handle user deletion requests?
Delete the user’s sessions and data via the Tracelit dashboard. Also call
reset() on the client when the user logs out so no future sessions are linked to them on that device.Can I use Tracelit without identify() and stay fully anonymous?
Can I use Tracelit without identify() and stay fully anonymous?
Yes. If you never call
identify(), all sessions are anonymous. Tracelit still tracks sessions using a random ID stored in localStorage — but there’s no way to link that ID to a real person unless you call identify().Is the session replay data processed in the EU?
Is the session replay data processed in the EU?
Check the Tracelit dashboard or contact support at hey@tracelit.io for current data residency options.