How we use error tracking and session replay
What we capture to fix bugs, what we mask, where it lives, and how long we keep it.
Northpoint uses Sentry to catch errors and understand problems quickly. When something breaks we want to fix it before you have to report it twice — and when you do send feedback, we want enough context to act on it. Here's exactly what that involves, and the lengths we go to so your clients' information stays private.
What we capture
- Errors — when the app throws an error, we record the technical details (the stack trace, the page, the browser) so we can reproduce and fix it.
- Performance traces — a small sample of page loads, to find slow screens.
- Session replay — on the app (never the marketing site), a sampled, masked reconstruction of what happened on screen before an error or a piece of feedback. Think of it as a wireframe of your clicks, not a video of your data.
What we mask — and never capture
Session replay hides content by default rather than opting into hiding it:
- All text is masked. Names, addresses, emails, phone numbers, and notes are replaced with blocks before anything leaves your browser.
- All form inputs are masked — anything you type.
- All images and media are blocked.
- Financial details are blocked entirely. Commission ledgers, deal compensation, and deal prices aren't just masked — those components are removed from the replay altogether.
The result is a replay that shows the shape of what someone did — which buttons, which screens, in what order — without exposing client PII or deal financials.
Where it runs
Replay runs only on the authenticated app. The public marketing site and knowledge center are never recorded. Error reports are routed through our own domain, so ad blockers don't silently drop them.
How long we keep it
Errors and replays are retained for a limited window (up to 90 days) and then deleted automatically. We use them to fix problems, not to build profiles.
Coming soon: the formal privacy policy
A full privacy policy is on the way. It will spell out our use of error tracking and session replay, the retention period, and how to opt out. Until then, this article is the canonical description of what we collect and why.