Recorder Extension Privacy Policy

• The extension captures interaction metadata only while you run a Steperly recording or a Walk Live editing session.
• Recorded interaction metadata is used to align your screen recording, generate guide steps, and create reliable Walk Live targets.
• The extension does not collect unrelated browsing history, typed text, passwords, form values, advertising identifiers, or extension usage analytics.
• Screen video and audio are captured by the Steperly web app through the browser's screen-sharing controls, not by the extension itself.

• 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.
• 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 visible-text snippet, input type, and non-password value length. Typed content and passwords are never collected.
• For choices and dynamic Walk Live targets, bounded context can also include nearby option labels, section or table headers, and short text from up to eight visible list or table items.
• If the recorded app displays personal information inside a control, nearby option, list item, table row, or URL path, the captured context can include that displayed information or identifier.
• For Walk Live editing: a one-time handoff code, target origin, the guide draft returned by Steperly, a short-lived edit token, and the guide edits you choose to save.
• Temporary recorder state held in browser session memory while a recording is active.

• Validate that a recording or Walk Live edit was started by an authorized Steperly session.
• Align interaction events with your screen recording and generate step markers, focus targets, and guide copy.
• Open a guide in the app it documents and save only the Walk Live edits you make.

• Capture tokens and active recorder state are stored in chrome.storage.session, which is memory-backed for the browser session and restricted to trusted extension contexts.
• 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 guide creation is handled under the main Steperly Privacy Policy and workspace retention controls.

• The extension contacts Steperly endpoints over HTTPS to validate capture tokens and to redeem or save Walk Live edit sessions.
• Recorded interaction events are returned only to the Steperly admin panel that initiated the authorized session.
• When you analyze a recording or create a guide, 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.

• 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.

• Start or stop capture at any time from Steperly or the browser's screen-sharing controls.
• Choose the tab, window, or screen shared with the Steperly web app.
• Record video without extension interaction tracking when that option is available.
• Remove the extension to clear its browser-managed session data.

• scripting: inject the recorder listeners or Walk Live editor only after you start the corresponding Steperly feature.
• storage: keep the active token, recorder state, and bounded event buffer in browser session memory.
• HTTPS host access: run the recorder on the website you choose to document and open Walk Live editing in that app.
• The published extension does not request tabs, activeTab, browsing-history, file URL, or general HTTP permissions.

• 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 info@stpwise.com.

For legal notice, visit /impressum.