YOUR ACTION
You start the recording.
Start a recording when you’re ready to reproduce a bug. Pause or stop it from the extension as you move through the workflow.
SECURITY & PRIVACY
Know what’s recorded. Choose how it’s shared.
Useful bug reports need context. Understand what a recording contains, what input masking protects, and how access works before you share it.
billing.example / renewal
TEAM PLANSeat renewal
Account email01
••••••••••••
Renewal summary02
3 seats $65 / yearThe quote still uses 2 seats.
Sample recording00:12
01
Input value maskedForm values are hidden in the replay.
02
Page content visibleText outside inputs still needs review.
01 / RECORDING & MASKING
Keep the steps. Know what stays.
Input masking is one safeguard. The rest starts with the page you record and the context you pass along.
A good first recording
Use a test account with sample data. Replay the result and check the attached context before sharing.
BY DEFAULT
Input values are masked.
The replay recorder masks form values. Text elsewhere on the page, including a value shown outside an input, can still appear.
REVIEW BEFORE SHARING
Page context can still be captured.
Recordings and element captures can include URLs, visible text, element attributes, screenshots, and browser and viewport details. Check them for sensitive information.
ARTIFACT EXPORTS
Entered values stay out of exported steps.
Fill and select values are redacted from artifact export steps. This applies to those step values; review the other content in an export before sending it on.
02 / SHARING & ACCESS
The right context. The right audience.
A private recording stays behind project access. A public link makes it available to anyone who has the link. Pick the access that fits the handoff.
- 01Review the recording.
Check page content, URLs, screenshots, and notes.
- 02Check who can open it.
Use project access for private team work.
- 03Revoke a public link when it’s done.
Return the recording to private to end public access.
Renewal quote mismatchSample recording · 00:12
WHO CAN OPEN IT
Your project team.
Private replay content requires sign-in and project ownership or membership.
Knowing the URL doesn’t grant private access.
Example only. This does not change a real recording.
03 / A FEW PRACTICAL DETAILS
Before you press record.
Storage, links, and the choices that matter after a recording ends.
Read the Privacy Policy01Why does Chrome ask for website access?
Website access lets the extension inspect page elements and record a browser workflow. You still start each recording yourself. Review or change site access in Chrome’s extension settings using Chrome’s site-access guide.
02Where are my recordings stored?
Local recordings are kept on your device for 30 days. Saving a recording to your account uploads it to Samelogic. Pending local recordings can also sync when you sign in. For cloud retention and backup details, contact us before recording a sensitive workflow.
03Can I revoke a public recording link?
Yes. A project member can return the recording to private, removing public access through its link. This does not recall screenshots, downloads, or other copies someone may already have made.
04Can I delete a saved recording?
You can delete a saved replay from its project. For account deletion, retention requirements, or questions about backup handling, email hi@samelogic.com.
05Where can I review your data and cookie policies?
Our Privacy Policy covers information collected across the extension, web app, and website, including cookies and analytics. Website privacy preferences are available in the footer. Those choices are separate from the recordings you create with the extension.
FOR YOUR TEAM’S EVALUATION
Have a security question? Let’s get specific.
Ask about deployment, subprocessors, retention, deletion, or the assurance details your team needs to evaluate Samelogic.
Contact us about securityFound a vulnerability?
Email a clear description and safe reproduction steps. Leave out credentials, secrets, and customer data.
Report an issuePUT IT INTO PRACTICE
Start with a bug. Use sample data.
Try recording, replaying, and inspecting a workflow in desktop Chrome.