Developer pages

Privacy model

What HumanBehavior stores from the browser, what you must configure, and GDPR-minded checklist.

Model

HumanBehavior records product analytics and session replays from the browser SDK. Privacy is a shared responsibility:

  1. The SDK defaults toward masking inputs (privacy-first redaction).
  2. You configure redaction for your UI and avoid sending secrets in events/logs.
  3. You meet your own legal obligations (notices, DPA, retention, region) — this page does not give legal advice.

What can contain sensitive data

ChannelRiskControls
Session replay (DOM / inputs)Typed values, on-screen PIIredactionStrategy, password always masked — Replay privacy
Console warn/errorTokens printed via console.warn / console.error (console.log is not ingested)enableConsoleTracking: false or stop logging secrets on those levels
Network errorsURLs, optional bodiesKeep captureRequestBodies false unless needed; bodies are redacted when on
Custom eventsAnything you put in propertiesDo not send passwords / raw cards / secrets
Identify traitsEmail, name, planSend only what you need for product analytics
Error reportsStacks, breadcrumbs, URLsSource maps may reveal original paths; still avoid secrets in messages

SDK defaults that matter

OptionDefaultPrivacy note
redactionStrategy.modeprivacy-firstMask inputs unless unredacted
recordCanvasfalseOpt-in visual capture of canvas
enableConsoleTrackingtrueOpt-out
enableNetworkTrackingtrueOpt-out; failures/long loads
captureRequestBodiesfalseOpt-in
enableErrorTrackingtrueOpt-out

Password fields cannot be unredacted. Visibility-first still forces password masking and supports [data-hb-redact="true"].

Product surfaces that can show data

  • Replay viewport + activity tabs (Console / Network / Custom)
  • Insights → Logs
  • Issue breadcrumbs, stacks, request context
  • Visitors traits you chose to send via identify

Checklist before production

  1. Choose privacy-first or an explicit visibility-first + redactFields list.
  2. Record a staging session covering login, checkout, and any PII forms — inspect the replay.
  3. Audit console.* in sensitive flows.
  4. Confirm custom events and identify payloads.
  5. Call tracker.logout() on app sign-out so shared devices do not merge identities.
  6. Document retention / access for your org (product retention policy details beyond schema are unknown here — confirm with your team).

Modes recap

ModeInputsSelectors
privacy-firstMasked by defaultunredactFields to show
visibility-firstVisible by defaultredactFields / data-hb-redact to hide; passwords always hidden