Privacy
Events describe features, not people.
Stagewright needs to know which features people use and where they stop. It doesn't need to know what they typed. This page says what we collect, from whom, and what we never collect.
This is a plain-language summary of how the product is built, not a legal policy. The formal privacy policy and terms will be published before the private beta opens to more teams.
In your product: events about features
When you send usage data (through Segment, a PostHog import, our player, or the browser SDK), Stagewright keeps what it needs to describe features:
- Which feature, which step, when. Events are mapped to features from your routes, test ids and event names.
- Hashed ids. People and accounts are identified by hashed ids. Accounts, not individuals, are the default view.
- Allow-listed properties only. Anything not on the list is dropped on arrival.
What we never collect: keystrokes, form values, or session replay. Stagewright isn’t a session-replay or people-tracking tool.
From your support tools
When Intercom, Zendesk or Productlane is connected, conversations are read to learn which features people ask about. Conversation bodies stay in memory while they’re processed. What’s kept is redacted question clusters, counts and thread ids, so you can see support load per feature without Stagewright storing your customers’ messages.
From meeting notes
Notion, Fireflies, Granola and Zoom can be connected as read-only sources for how your team explains the product: its terms and tone. Transcripts are read when needed and discarded. Nothing from a meeting is quoted in a video.
Recordings
Walkthroughs record your product with the accounts and data you give them, so we recommend a demo account with seeded data. Secrets are referred to by name in walkthrough files; their values stay write-only in the dashboard or your CI, are never written into recordings or still labels, and are released to a local or self-hosted runner only when you opt in, with each release written to the audit log. A runner you host keeps the browser on your network.
The CLI
The CLI sends four anonymous milestones, once per install, so we can measure how long it takes to get to a first video: an install id the CLI made up, the time, CLI and Node versions, the OS family, whether it’s CI, and a salted hash of the project path. Never code, paths, URLs or anything from a walkthrough. It’s off in CI. Turn it off anywhere with DO_NOT_TRACK=1, STAGEWRIGHT_TELEMETRY=0, or stagewright telemetry disable.
This website
This site sets no cookies and runs no analytics or third-party scripts. Fonts are served from our own domain. Joining the waitlist happens in the app at app.stagewright.ai, where our sign-in provider, Clerk, keeps your email address; we use it only to contact you about the beta.
Questions: support@stagewright.ai.
Try it on your own product
Record a first walkthrough on your machine with no account. PR checks, approvals and publishing are in private beta: join the waitlist and we'll set you up by hand.