Platform
Privacy & security
What is stored, what is not, and how to get it out or remove it.
No cookies
The tracker never touches document.cookie. It does use browser storage: a visitor ID in localStorage, so a returning visitor is recognised, and sessionStorage for per-tab state such as funnel progress.
Storage is not the same as “no consent needed”
localStorage is generally treated like a cookie under ePrivacy and the GDPR, even though it is not one. “Seentics sets no cookies” is accurate and worth saying. Whether your site still needs a consent notice is a question for your own legal advice, not something these docs can answer.What is not collected
- No IP storage. Country is resolved at ingest; the address is not kept with the event.
- No typed input. Form fields and rich-text editors (anything
contenteditable) are masked in recordings, always — it is not a setting that can be turned off. - No cross-site tracking. A visitor ID is per site. There is no shared identity graph between the sites you track, or between customers.
What a recording does include
A recording is more than the DOM. Alongside the replay itself, Seentics stores the annotations that make one worth watching — and it is worth knowing what those are before you enable recording on a page that handles personal data.
- Console output. Calls to
console.log/info/warn/error/debug, up to ten arguments each, truncated at 1,000 characters. - Network requests. Method, URL, status and duration for every
fetchandXMLHttpRequest. Request and response bodies are never read. - JavaScript errors. Message, stack, file and line for uncaught errors and unhandled rejections.
All three are scrubbed before they leave the browser. URL credentials and fragments are dropped; query values under keys that look sensitive (token, password, api_key, email, otp, and similar) are replaced with redacted; and anything shaped like an email address or a bearer token is removed from console arguments, error messages and stack traces wherever it appears.
Scrubbing is a safety net, not a guarantee
?ref= parameter identifies a person, or that a log line prints a customer record. If a page handles data you would not want a teammate reading back, turn the sidecars off for the site or exclude the page.Both sidecars can be switched off on the tracker script tag, in which case the override is never installed at all — console and fetch are left untouched:
data-capture-console="off"— no console capture.data-capture-network="off"— no request capture.
Keeping things out of recordings
Beyond input masking, mark elements you do not want captured. All three attributes are read from the DOM by the recorder:
data-seentics-block— replaced by a placeholder; contents never captured.data-seentics-mask— the element still renders and animates, but its text is replaced with asterisks. Use it where the layout matters and the words do not.data-seentics-ignore— captured once, then changes inside it are not tracked.
See the tracker reference for examples.
Turning features off
Session recording and heatmaps are off until enabled per site in Settings → Features. While recording is off the recorder file is never downloaded, so nothing about a visitor's session is captured at all.
Data subject requests
Per-visitor export and erasure are not available yet. The /api/v1/privacy/* paths are reserved and currently answer 501 Not Implemented. This page previously described them as working; they were never wired up, and the endpoints returned empty success responses.
What you can do today: deleting a website from Settings removes its analytics events, session recordings, heatmap points, funnels and automations. Retention also runs automatically and drops data past your plan's cutoff — see below.
If you need to answer a data subject request before per-visitor tooling ships, contact support and we will run the erasure directly.
Retention
How long data is kept depends on your plan; the figure is on the pricing page. Older data is removed automatically once it passes that window.
Self-hosting
The strongest privacy answer is that the data never leaves your infrastructure. Point the tracker at your own host with data-api-host and no third party is involved at all.