Storage and data destinations
Know where local and connected session data goes.
The destination depends on how you use Recorder. Local recording keeps its session in the browser until you download files; connected workflows can send content to your project’s configured services.
Local session data
Section titled “Local session data”Recorder holds session state in browser session storage and attachments in a local image store. Local session state can include original sensitive values used by privacy review, even where the viewer shows a mask. Treat this as working evidence, not a durable archive. Download what you need before resetting or ending your browser session.
New recording clears the previous local session, its attachments, and open local viewers. It does not delete files already downloaded or evidence already sent elsewhere.
Downloads
Section titled “Downloads”The viewer’s Download, or Download report in the account-free side panel, writes artifacts to your computer. The files are then governed by your device, backup, and sharing practices. Local download does not create an issue or store a report on Fairlead’s Data Plane.
Save the result in the description and download session.md with any notes.md. Download session artifacts explains their contents and conditional files.
Connected destinations
Section titled “Connected destinations”| Operation | Destination |
|---|---|
| Sign in and load assigned project configuration | Fairlead Control Plane |
| Send correlation identifiers during connected recording | Request destinations reached by the recorded tab, including third-party origins; capture domain rules do not limit header injection |
| Search, create, or update an issue | The project’s Bridge service and selected tracker |
| Attach screenshots to an issue | The configured tracker attachment path through Bridge |
| Store a session report | The project’s Data Plane destination |
| Request report enhancement | The configured Data Plane enhancement service |
| Generate reproduction steps from Description | The configured Data Plane step-generation service |
Connected recordings send x-fairlead-reproduction-id; x-fairlead-issue-id and x-fairlead-correlation-id depend on their settings. This happens during capture, before report submission. Account-free recordings do not send these headers. See backend correlation.
In the local viewer, Description → Add → Steps to reproduce sends a reduced report to the Data Plane; Steps written by AI sends the full report. Neither is offline. Recorded actions and Notes insertion work locally. The description editor is unavailable for stored sessions. See Generate user steps for the fields sent by each mode.
Projects can use local, private, or cloud Data Plane configuration. Ask your administrator which endpoint and retention policy apply to your project.
When report storage is disabled
Section titled “When report storage is disabled”The project setting Save recorded data in Data Plane disables report-bearing Data Plane operations, including enhancement and reproduction-step generation, when turned off. Issue commands and screenshot attachment submission may still send data.
Check the actual operation you are about to perform. Disabling report storage does not mean all connected data transfers are disabled.
Review and retention
Section titled “Review and retention”Automatic redaction does not cover every payload, console message, note, or image. Inspect content before sharing. Resetting a local session cannot recall external copies; use the destination’s own retention and deletion process.
The Fairlead Recorder privacy policy explains local use without sign-in. The platform Privacy Policy covers accounts and connected services.