polyshThe original is never modified
Every edit and export works from your recording without changing it.
How Polysh handles your recordings
Your recordings often show real product screens, customer names, and internal tools. Here is what we do with them, who can see them, and which providers process them.
What we commit to today
No training on your content
Recordings, scripts, and voices aren't used to train AI models.
You approve the script
A person on your team edits it before anything is voiced.
Private data in guides is blurred
Flagged screenshots stay blurred until your team chooses to show them.
Your original stays as you recorded it
Trims, skips, zooms, the new voice, and translations are saved as edits and applied only when you export.
- 1
Capture
The Polysh recorder for Chrome logs each click's position and time. Text typed into fields is redacted.
- 2
Upload
Stored in your workspace, and only its members can open it.
- 3
Edit
Saved separately from the recording, so any change can be undone.
- 4
Export
Each export creates new files (MP4, SRT, VTT) and leaves earlier ones as they were.
- 5
Share
A link points to one export or guide, never your whole workspace.
AI processing and subprocessors
Some steps send your content to specialist providers. Each one receives only what its step needs.
| Category | What it receives | What it's used for |
|---|---|---|
| Speech-to-text | The recording's audio | A transcript with word timings |
| Language model | The transcript, script, team word list, and guide screenshots | Rewriting, translating, planning guide steps, and checking screenshots |
| Text-to-speech | The approved script | The voiceover in each language |
| Sign-in | Names, email addresses, and workspace roles | Sign-in, SSO, and invitations |
| Email delivery | Email addresses and sign-in codes | Share-link codes and invitations |
| Hosting and storage | Recordings, exports, and workspace data | Storing files and running jobs |
Who can see your workspace
Removing a person or changing their role takes effect immediately, even on pages they already have open.
Invitation-only workspaces
Nobody joins without an email invitation, and only the newest invitation link for an address works.
Admin and member roles
Admins create projects and invite people. Members work on existing projects.
SSO
Access follows your own offboarding.
Separate workspaces
Projects, credits, and jobs never cross workspaces.
People outside your company
Guests reach only the one video or guide they were invited to, and never get a Polysh account.
Early access
How agents work with Polysh safely
Polysh for agents is in early access. The Video agent drives a browser on your own computer with your own test account, and you stay in charge of what it can touch and spend.
Destructive actions are labelled
Tools that delete something are marked, so your agent asks before using them.
Credit use needs your approval
The agent checks the estimate and asks before it spends credits.
Compliance and attestations
We'll publish attestations here as they're completed. If your team needs answers for a security review today, write to us and we'll help.
Report a security issue
Tell us what you found and the steps to reproduce it, using the contact options in your workspace. If you don't have a workspace, request early access and say it's a security report.
Please give us time to fix the issue before you share it publicly.