Data & privacy
Understand what is captured, where it goes, and what you can filter.
Review the data you send
SDKs can capture stack traces, request context, breadcrumbs, and performance data. The Browser SDK can add masked session replay. Your deployment determines where payloads are received and stored. Review these inputs using representative staging events before enabling production capture.
Use masking and filtering
Replay masks input values and page text by default. SDK scrubbing removes common secret formats and sensitive fields. Add scrubPatterns and, where supported, redactedFields for application-specific values. Use beforeSend to discard or adjust a scrubbed error event.
Filters cannot reliably recognize every sensitive value. Avoid putting secrets in URLs, logs, error messages, or custom breadcrumbs. Do not reinsert sensitive values in beforeSend.
Reelay.init({ endpoint: "https://api.usereelay.com", nodeId: "<your-node-id>", ingestKey: "<your-ingest-key>", redactedFields: ["customerSecret"], scrubPatterns: [/merchant-secret-[a-z0-9]+/gi], beforeSend(event) { return event; // Return null to discard this error event. },});Enterprise data boundaries
With Enterprise Agent execution, source files, full error payloads, scan findings, and analysis results are processed and stored in your infrastructure. The Reelay control plane receives identifiers, job state, heartbeats, authorization checks, and operational metadata.
The agent sends the inputs needed for a job to GitHub and the model provider you configure. Using your own model credential does not by itself keep analysis inputs inside your network.
Retention and access
Use the current workspace plan and billing settings to check retention and usage limits. For customer-managed storage, your team operates backups, access control, and retention. Review who can access the workspace and the supporting data services.