Extension privacy

Recorder Extension Privacy Policy

How we handle data when you use the Steperly browser extension.

Last updated: October 24, 2026

This policy is specific to the recorder extension. For the main app policy, see Privacy Policy.

Summary

  • The extension captures data only while you run a Steperly recording or a Walk Live editing session that you started.
  • When you start a recording from the toolbar popup or with Steperly's Record button, the extension records the tab, window, or screen you choose itself and uploads it to your Steperly workspace while you record. When you stop, a Steperly tab opens with the result. Nothing is captured before you start.
  • Your microphone is recorded only if you turn it on, and your camera only if you turn on the Camera switch for a Video recording. Chrome asks for your permission the first time.
  • Recorded interaction metadata is used to align your screen recording, generate flow steps, and create reliable Walk Live targets.
  • Interaction metadata never includes passwords. It includes what you type or choose in form fields only on the demo app your workspace connected in Steperly (Settings → AI assistants), so Steperly can film that recording again there; on every other site it never includes typed text or form values. A recording does show whatever is visible in the tab, window, or screen you record, so close or hide anything you don't want in it.
  • The extension itself does not collect unrelated browsing history, advertising identifiers, or usage analytics. The page Chrome opens when you remove it is a Steperly web page (see User controls).

Data we collect

  • A short-lived capture token used to authorize the recording session. Recording tokens normally expire after 60 minutes and are always limited to 24 hours or less.
  • The video and audio of what you choose to record: with "This tab", the tab you're on; with "Window, follows your tabs", the window, tab, or whole screen you pick in Chrome's sharing dialog. Your microphone audio is recorded if it is on.
  • A screenshot of the tab you click in, for each click while you record: as you press the mouse button, the extension takes a screenshot of that tab's visible page, and those screenshots are uploaded with your recording to make its click-by-click steps. This happens on every recording, only while it records (not during the short "Go!", the camera's "Start recording" card, or a pause). A screenshot shows the page as it looks, like the video does.
  • Your camera video, only if the Camera switch is on for a Video recording. The camera is recorded as its own file and uploaded with your recording, so you can lay it out in Steperly afterwards (for example as a bubble, side by side, or camera only). Before that recording starts, your camera shows large on the page with "Start recording" so you can check how you look; it is removed before recording begins. If you turn on "Show camera bubble", the camera is a bubble on the page instead, so it is part of the screen video and its screenshots.
  • Your existing Steperly sign-in, used to upload your recordings, to show your workspaces and recent flows in the toolbar popup, and to check whether a flow or video you finished is ready.
  • Interaction events such as clicks, right-clicks, deliberate presses, input or form-submit occurrences, scrolling, supported keyboard shortcuts, and navigation paths.
  • Event timing, coordinates, viewport and window geometry, and target bounds used to align interactions with the video timeline.
  • Details of the control you interact with, such as tag, id, role, accessible label, title, placeholder, sanitized link path, a short redacted visible-text snippet, input type, non-password value length, and whether the page was in light or dark mode. Typed content (including text in rich editors such as email or document drafts) and passwords are never collected, with one exception: on the demo app your workspace connected in Steperly, the text typed or chosen in a form field is kept (up to 500 characters per field; never a password, hidden, file or private field, and never a rich editor's text), so Steperly can film the recording again with the same typing. Steperly also discards any typed text that arrives from another site.
  • For choices and dynamic Walk Live targets, bounded context can also include redacted nearby option labels, section or table headers, and short text from up to eight visible list or table items.
  • Common email addresses, phone numbers, card-like numbers, and token-like strings are automatically redacted. Because automatic detection cannot identify every kind of personal data, recording owners should mark sensitive regions with a supported private boundary before recording.
  • For Walk Live editing: a one-time handoff code, target origin, the flow draft returned by Steperly, a short-lived edit token, and the flow edits you choose to save. A target you pick is saved as details that find the element again (such as its selector, label, and page path), never what is typed in a field.
  • Temporary recorder and Walk Live continuation state held in browser session memory while the corresponding session is active.

How we use data

  • Validate that a recording or Walk Live edit was started by an authorized Steperly session.
  • Turn your recording into the flow, step screenshots, or video you asked for, and place your camera in it the way you choose.
  • Align interaction events with your screen recording and generate step markers, focus targets, and flow copy.
  • Film a recording made on your workspace's demo app again on that app, with the same clicks and typing, when a workspace owner or admin asks for it.
  • Show your recent flows and drafting progress in the toolbar popup, and notify you when a flow or video is ready.
  • Open a flow in the app it documents and save only the Walk Live edits you make.

Data storage and retention

  • Capture/edit tokens and active recorder or Walk Live continuation state are stored in chrome.storage.session, which is memory-backed for the browser session and restricted to trusted extension contexts.
  • Your popup choices (such as capture mode, microphone, and camera), the camera bubble size, the workspace you save to, and the Steperly app address are kept in chrome.storage.local so they are remembered. When you press Record in Steperly, the recording's title and up to 10 step texts are kept there too, so the popup can show them; they expire after 2 hours.
  • Until Steperly has your recording (or screenshots) and its clicks, a copy is kept on your computer in the extension's own browser storage (IndexedDB), so one that couldn't be saved can be retried or downloaded from the popup. It is deleted once Steperly has it; one that was never saved is deleted after a day, the next time the extension starts or records. The separate camera file is uploaded when you finish and is not kept in that copy: if it can't be uploaded, the video is saved without it and you are told.
  • The local interaction buffer is capped and excludes continuous mouse-movement tracking. Active session data is cleared when recording ends.
  • If the final Stop response is interrupted, one recovery copy may remain in service-worker memory for up to five minutes, or until a new recording starts.
  • After interaction data is returned to the Steperly app, any data you submit for analysis or flow creation is handled under the main Steperly Privacy Policy and workspace retention controls.

Data transfers and sharing

  • The extension contacts Steperly endpoints over HTTPS to validate capture tokens, to redeem or save Walk Live edit sessions, to check which recorder versions Steperly accepts, and, with your Steperly sign-in, to list your workspaces and recent flows and check drafting progress.
  • The extension uploads your recordings (screen video, microphone audio, the separate camera file when there is one, or screenshots) to your Steperly workspace over HTTPS, with your Steperly sign-in. Contracted hosting and AI-processing providers may process them solely to create the flow or video you requested.
  • Recorded interaction events are sent only to Steperly, with the recording they belong to, or to the Steperly admin panel that started the authorized session.
  • When you analyze a recording or create a flow, the app sends a minimized, bounded subset of interaction metadata to Steperly infrastructure. Contracted hosting and AI-processing providers may process it solely to provide the feature.
  • We do not sell extension data or use it for advertising, credit, insurance, or unrelated profiling.

Security

  • Capture and edit tokens are cryptographically random, time-limited, and verified before privileged actions begin.
  • Only the live steperly.com dashboard origins listed in the extension manifest can initiate external extension messages, and Walk Live API calls are restricted to Steperly endpoints.
  • Production network communication uses HTTPS, and recorded URLs are minimized to origins and paths before storage.

User controls

  • Start, pause, finish, or delete a recording at any time from the toolbar popup, with Alt+Shift+P (pause) and Alt+Shift+F (finish), from Steperly, or from the browser's screen-sharing controls. Delete discards the recording and its screenshots; it is never added to your workspace.
  • Choose what is recorded: "This tab", or "Window, follows your tabs", where Chrome's sharing dialog lets you pick a window, a tab, or your whole screen.
  • Turn your microphone and camera on or off in the popup, and hide the camera at any time from the popup, with Alt+Shift+C, or with the button on the bubble.
  • Mark sensitive application regions with data-stpwise-private, data-stepwise-private, data-private="true", or data-sensitive="true" so targets inside them are captured structurally without visible labels or identifiers. This applies to interaction details; the video and screenshots still show what is on screen.
  • Remove the extension to clear its browser-managed session data. Chrome then opens a Steperly page asking why you removed it; the extension tells that page only its version. Like the rest of steperly.com, the page uses anonymous product analytics to count removals and, if you choose to answer, to record your reason.

Permissions

  • scripting: inject the recorder listeners, the short "Go!" before recording, the camera bubble or "Start recording" card, or the Walk Live editor only after you start the corresponding Steperly feature.
  • storage: keep active tokens, recorder/Walk Live session state, and the bounded event buffer in browser session memory, and your popup choices, camera bubble size, and a pending recording title and step texts from Steperly in local storage.
  • tabCapture: record the tab you chose to record, only after you start the recording.
  • activeTab: Chrome lets the extension capture only a tab where you clicked the Steperly icon, and only that tab.
  • offscreen: record your screen, microphone, and camera (when it's on) while you record, upload the recording, and show your camera in the bubble.
  • notifications and alarms: tell you when a flow or video you finished is ready, and keep checking its progress while Chrome pauses the extension in the background.
  • Access to all websites: run the recorder on the website you choose to document, take a screenshot of the tab you're on for each click (Chrome only allows screenshots with this access), and open Walk Live editing in that app. When you start a recording, just before Chrome's sharing dialog opens, the extension also marks your open web pages so it can tell which one you picked; it reads nothing from them and removes the mark afterwards. The recorder runs only while you record or edit.
  • The published extension does not request tabs or browsing-history permissions, and it never runs on local files.

Changes to this policy

  • We may update this policy as the extension evolves. Material changes will be reflected here with a new effective date.

Contact

If you have questions, contact support@steperly.com.

For legal notice, visit /impressum.