Skip to main content
The SDK records what your app did, not what your users typed. Its defaults are deny-first: it keeps as little as possible, and scrubs what it does keep before anything leaves the browser.

What is captured

  • Page views and route changes, with the page title and the redacted URL
  • Clicks, with the element’s tag, role, and label (data-hinto-label, then aria-label, then title)
  • How far the customer scrolled
  • Console warnings and errors, with their redacted arguments
  • Script errors and unhandled promise rejections, with their message and stack
  • Each fetch and XHR request’s method, redacted URL, status, and duration, including requests to other services
  • Journey events and custom track events
Clicks, scrolls, console messages, and requests can each be turned off. See the options in Install the browser SDK.

What is never captured

  • Form values and keystrokes
  • Request and response bodies
  • Headers and cookies
  • Full query strings, which are stripped by default from every captured URL

What redaction covers

Every captured URL, including its path segments, and every payload string passes through redaction patterns before it leaves the browser. The built-in patterns scrub email addresses, bearer tokens, sensitive query parameters such as token, secret, password, API keys and suffixed forms like reset_token, OAuth code values, and long opaque strings such as hex ids and API tokens.

Journeys

Journey events carry only tokens: the journey key, the action, and a failure category. They never carry free text such as an error message. Their optional metadata allows at most 8 keys per event, with scalar values only: strings of 200 characters or fewer, finite numbers, and booleans. Metadata strings pass through the same redaction patterns before validation. An event with a key that looks like a secret, such as password, token, or api_key, keeps its step and drops all of its metadata, and an event larger than 2 KiB drops its metadata. Send tokens such as a plan name, never customer data.

Tuning

Two config knobs let you adjust this:
allowUrlSearchParams is an allowlist of query parameter names. The redaction patterns still run over whatever survives, so a parameter named like a secret is scrubbed even when allowlisted. Allowlist a parameter only if you are comfortable capturing its values. redactPatterns replaces the default list for URLs and payloads rather than extending it (click labels always use the built-in patterns), so include the built-in shapes you still want alongside your own (for example, a custom pattern for short path tokens like /reset/AbC123 that the defaults do not catch). Before production, review what your app prints with console.warn and console.error, since Signal records those by default, or set captureConsoleLevels: []. Treat captured sessions with the same care as your own logs, and check that your privacy policy covers session recording.

In a React Native app

The React Native SDK records the same kinds of events, with three differences. A screen is named by its templated route, such as book/[id], never with its params. A tap records the control’s hintoLabel, accessibilityLabel or testID, never the text on screen. Leaving and returning to the app are recorded with the time away. It also records the app’s version and build, the device model, the OS and its version, the locale and the time zone. Until they are sent, queued events, the support draft, a pending message and journey state sit unencrypted in AsyncStorage, which Android Auto Backup can include. They are small and short-lived, and a sign-out erases the queued events of the person who signed out.

Declare it to the app stores

You declare what the SDK collects, because it runs in your app. With capture tied to the signed-in account and used for your own support, this is the usual mapping: Mark the data as linked to the user and used for App Functionality, which covers support. Hinto does not use it for tracking or advertising, so the SDK needs no App Tracking Transparency prompt.