Privacy & redaction
What the SDKs capture, what they redact before it leaves the process, and how to keep sensitive data out.
Defaults that protect you
| Product | Default |
|---|---|
| Session replay (Flutter) | Every text field is masked (replayMaskTextFields: true). |
| Session replay (web) | All input values are masked (replayMaskAllInputs: true). |
| Telescope | Passwords, tokens, secrets, cookies and Authorization headers are redacted in your process, before anything is sent. |
| ASP.NET Core middleware | Query strings are not recorded. |
Masking replay
NexusMask(child: CreditCardForm()); // never appears in framesRedacting Telescope payloads
Telescope redacts by key name, recursively — in request and response bodies, headers and job payloads — before anything leaves your process, and the backend applies the same list again on arrival. Add your own keys in the console under Telescope → Settings; the SDKs pick the list up from the response to their next delivery, without a deploy.
What you send is what is stored
Events, logs, error context and traits are stored as you send them. Don't put secrets or unnecessary personal data in properties; if you need a reference, send an id, not the value.
Retention
Each project has a retention window after which telemetry is no longer returned. Telescope journeys are deleted after their own window (48 hours by default, up to 14 days).