Check what the extension can read

Exactly what each recording captures, what is masked and what it never reads.

In short

The extension reads nothing until you start a recording, and then only the calls or steps that recording approved. Secrets are masked before anything leaves your browser, but everything else is kept as typed - so record with test data.

Before you start

• Who: anyone who records.
• Plan: none.
• First: a test account and test data, not real customers.

Before you record

1. Use a test account and test data, not real customers or your own passwords.
2. Approve only the addresses the recording needs: the site and its own API. Tick extra addresses only when you need them.
3. Close tabs that show private information; the recorder screenshots what is visible in the tab you use.
4. Start the recording from {{brand}} with "Start recording", and press "Stop & review" as soon as the task is done.

What it reads

Good to know

• Only secrets are masked. Names, emails and addresses are kept exactly as typed, and screenshots show whatever is on screen.
• Request bodies over 32 KB, and bodies that are not JSON or a form, are left out.
• Everything goes only to the {{brand}} you trusted, and {{brand}} checks again before it stores anything.

If something goes wrong

• You recorded real personal data by mistake: delete the recorded session or the track's steps, then record again with test data.
• A call you expected is missing: it went to an address the recording did not approve, or its body was over 32 KB or not JSON. Add the address and record again.

Related

• /help/settings/browser-extension
• /help/settings/browser-sync-recording
• /help/settings/record-a-ui-track