Trust & Safety
Privacy & Data Safety
WhatzBug is designed with privacy controls built in. Decide what data is collected, how it is processed, and where it goes.
Privacy Controls
Automatic PII Redaction
Pattern-based redaction strips emails, phone numbers, credit cards, and custom patterns from network data before capture.
Feature-Level Opt-Out
Disable any individual SDK capability: replay, network, crashes, performance, or journey recording.
Local-Only Debug Data
When debug mode is enabled (debug: true), all data streams locally via WebSocket. Nothing goes to the cloud.
Replay Privacy Masking
Session replay supports view-level masking and exclusion to protect sensitive UI elements.
URL Filtering
Exclude specific API endpoints from network monitoring via configurable URL patterns.
No-Throw Safety
The SDK uses noThrow() wrappers on all public methods — it will never crash your app.
FAQ
What data does the SDK collect?
The SDK can collect console logs, network requests (intercepted XHR/fetch), performance metrics, crash reports, session replay screenshots, user events, and device metadata. Each feature can be individually disabled.
Does debug data leave my machine?
No. When debug mode is enabled (debug: true in init), all data streams directly from the mobile app to the Desktop App over your local network via WebSocket. No data goes to the cloud during debug sessions.
How does PII redaction work?
The SDK includes automatic pattern-based PII redaction for network request/response bodies. Patterns match common PII formats (emails, phone numbers, credit cards, etc.) and replace them before data is captured.
Can I disable specific features?
Yes. Each SDK capability (replay, network, crashes, performance, journey) can be independently enabled or disabled via the features config object.