Shoyu records the screen you pick, and anything on it is in the video. Beside the video, it notes which apps, pages, and files were open. Your team’s owners and admins choose which of those notes it keeps.
The video, then mostly the names of what was open, so playback and search work.
Your screen
The display, window, or portion you pick. Everything visible there is in the video.
Your microphone
Off until you turn it on. An instant recording started from your editor turns on your first microphone and system audio.
System audio and your camera
Off until you turn them on.
Where you click
Always, to highlight clicks in playback.
Where your pointer moves
Always, so playback can redraw the cursor.
App name and window title
A window title can hold whatever the app puts there, such as an email subject.
Browser page title and address
With the browser extension. Shoyu drops the query string and #fragment unless your organization keeps full addresses. Linear, Figma, and Notion links keep theirs.
Repo, file, branch, and line range
From the IDE extension in VS Code-family editors. File paths start at the repo.
Terminal output
Only in shells you record with shoyu terminal record. The replay keeps each command and what it prints. Shoyu masks likely secrets such as tokens and keys, but it can miss one.
Figma, Linear, and Notion titles and links
Read from their local app data on your Mac. Never the document itself.
Shoyu does not read or store these beside the video, whatever the settings, except where noted. If one is on screen while you record, the video shows it like anything else.
Page contents
The text, images, and form fields on a web page.
Selected or visible code
The IDE extension sends line numbers, not code.
Messages
A window title can still include a subject or a sender, if the app puts it there.
Request or response bodies
Even with Deep Context.
Browser cookies or storage
Even with Deep Context.
Anything inside a file
Except what a terminal you record prints.
What you type
Except in a terminal you record, which shows the commands you type. Start it with --capture-input and it keeps every keystroke, passwords included.
These are off until the person recording turns them on. When they are on, Shoyu shows it.
Console error markers and network request metadata for one tab in one recording. Addresses lose their query string, and only four basic headers are kept.
Shoyu collects Deep Context only while the tab shows “Shoyu Capturing”.
Shortcuts like ⌘C, and keys like Return, Delete, and the arrows, shown in playback. Never the letters you type. Off until you turn it on, then remembered. The Recording Island shows a keyboard while it is on.
Our hosting provider stores and delivers the video and files such as terminal replays. Transcripts, context, and comments live in Shoyu’s database. Notification emails go through our email provider and can include a recording’s title and comment text.
Transcription runs on your Mac, and Ask runs in the viewer’s browser. A hosted AI service suggests titles, and it is the only AI service that sees recording content.
To suggest a title, Shoyu sends that service parts of a recording’s transcript and chapters, its context titles, links, and summaries, and the terminal commands it ran. Shoyu masks likely secrets first. Organizations start with this on. Owners and admins can turn it off when they create the organization or in Settings › Policy. Shoyu then sends it nothing, and titles stay as Shoyu named them until someone renames them.
Providers can change as Shoyu grows. Need to know which services we use? Get in touch.
Owners and admins set one policy for the team in Settings › Policy, and it applies to every new recording. Members can read it but not change it. Shoyu does not change it for you. A setting added later starts at the default this page lists.
Owners and admins turn each context layer on or off for the team: App Identity, Browser, IDE, Terminal, and Keyboard shortcuts. Shoyu leaves a layer that is off out of the team’s new recordings.
A recording can be private, so only you and the owners and admins of your organization can watch it; shared with your organization, so your teammates can watch it; or public, so anyone with the link can watch it.
Team organizations start with external links off. While they are off, no one in the team can make a recording Public. If they are turned off later, a Public default becomes Organization, and existing public links stop opening for people outside the team.
Members can connect two recordings they can already watch. Owners and admins can limit this to owners, admins, and each recording’s creator.
Try the controls. Changes here are not saved.
Default visibility
New recordings start here
External links
Public links only work when this is on
Allow members to manage Recording relationships
Link recordings they can already watch
Members can modify recording tags
Add and remove tags on recordings they can watch
Context layers
Hover over a mark, or press and hold it, for the details.
| Ability | Owner | Admin | Member |
|---|---|---|---|
| Record and share inside the policy | |||
| Read the policy at any time | |||
| Set the policy | |||
| Manage members and domains | |||
| Archive the organization |