Page text and images, too, unless you choose to show them.
Private by default. Typed values never show.
Replay is off until you turn it on, page text stays masked unless you show it, and customers choose what they share.
Seeing what broke shouldn’t mean seeing everything. Typed values never leave the page, replay stays off until you turn it on, and customers choose what they send.
Nothing private in the report. And nothing sent until they choose.
Capture stays in the browser until a person sends a report or a packet. What leaves it is masked first.
Replay is off until you turn it on, and every replay is gone within 30 days.
A replay is their call, offered only when they try it again, and sent only if they pick it.
Works with
GitHub
Linear
Jira
Asana
Slackand any MCP client
How it works. Three steps, nothing to build.
01It stays in the browser
Recent activity is kept in the browser’s memory, and nothing leaves it until someone sends a report or a packet.
02Typed values are masked
Everything typed shows as dots. Passwords, one-time codes, card and phone fields are never captured.
03They choose what to send
Before sending, customers can untick parts of the capture and black out the screenshot.
Plans from $69 a month, with unlimited websites and teammates.
See pricingQuestions, answered.
No. The widget talks to Rebase to load and check its settings, but what it captures stays in the browser until a report or packet is sent.