Browser Monitoring
Privacy
Publishable keys only, exact origin allowlists, scrubbed URLs, and click capture off by default. Design for consent before enabling DOM collection.
Origins
Browser apps require an exact HTTP(S) origin allowlist. Empty lists and wildcard origins are denied at ingest. Configure allowed origins in authenticated Browser app settings before installing the SDK on a production site.
Keys
Ingest accepts publishable keys only (pk_live_…, pk_test_…, legacy pk_…). Workspace REST secrets (mydle_…) must never appear in browser bundles.
URL scrubbing
Client-side scrubClientUrl strips query parameters whose keys or values match sensitive patterns (password, token, secret, api key, auth, session, cookie, jwt, bearer, and similar). Stacks and exception context apply the same family of redactions before queueing.
Clicks
Automatic click capture defaults to off (clicks: false). Enable only after reviewing consent and privacy requirements:
mydle.init({ projectKey: "pk_live_…", clicks: true });Inputs, textareas, selects, contenteditable regions, and elements marked data-sensitive or data-private are excluded. Labels use tag / id / aria — never visible DOM text or form values. Manual track() is unaffected.
What is never collected
- Session video / DOM replay
- Request or response bodies
- Cookies, passwords, or form field values
- Account identity — only opaque anonymous / session ids
Limitations
- Scrubbing is heuristic — do not put secrets in path segments or custom track properties.
- IP handling / masking is a server ingest concern; configure in the product where available.
- You remain responsible for notice and consent in your jurisdictions when enabling clicks or custom events.