Redaction

You decide what leaves your app. Rasputin always hides common authentication secrets. Set scrubPII: true to also redact personal data. Skip files, or hide extra fields, when you need to.

What we redact automatically

Values whose names are the secret itself are redacted at ingest before grouping, secret classification, or persistence, including password, cookie, authorization, secret, and similar. The SDK sends bounded raw values; it does not match process environment secrets locally. Remaining secret-shaped strings are still classified at ingest. This is independent of scrubPII.

Hide extra fields

The browser SDK does not take a custom redactKeys list. Sensitive names above are still redacted. Skip a file with @rasputin-ignore-file, and set scrubPII: true when you need personal-data redaction.

RasputinInit({
  // ...required options
  scrubPII: true,
});

Skip files and functions

Put // @rasputin-ignore-file at the top of a file to skip instrumentation. Nothing in that file is recorded.

// @rasputin-ignore-file

export const readDatabaseUrl = () => process.env.DATABASE_URL;

Personal data

scrubPII on RasputinInit defaults to false. Set it to true when ingest should also redact personal data such as names, emails, and phone numbers. Authentication secrets are always redacted.