Information Streamwright collects
- Kick account identity and OAuth authorization needed to connect your channel.
- Signed Kick events such as chat activity, follows, support events, stream status, title, and category.
- Creator settings, saved moments, reports, content drafts, finished clips, and feedback you submit.
- A stream recording only when you deliberately select it for private clip creation.
- Email address and channel details when you request private beta access.
- For invited testers: an invite label, hashed invite-code digest, expiry, revocation status, redemption count, and last redemption time. The full generated code is not stored.
How Streamwright uses information
Streamwright uses connected information to operate live coaching, organize stream history, generate private reports and content drafts, maintain account security, respond to feedback, and manage beta access. Streamwright does not sell personal information.
Microphone and audio
The Live Voice Coach measures microphone level, silence, speaking activity, and a rolling energy baseline inside your browser. Raw microphone audio and the continuous energy history are not recorded, uploaded, or stored. When a relative energy spike becomes a saved moment, Streamwright stores only the timestamp, relative spike measurement, and generated marker text. A recording you deliberately select in the Clip Engine is different—it is uploaded to Streamwright for clip rendering. Optional live transcription will require separate notice and consent before it is introduced.
Clip processing
When you choose a recording, Streamwright transfers it in resumable encrypted web requests to private server storage. Streamwright deletes temporary recording chunks after the render attempt finishes. The finished MP4 and its metadata remain in account-scoped storage so you can preview or download the clip. Streamwright does not publish clips to social platforms automatically.
Storage and account separation
Creator records and finished clips are stored server-side and separated by the authenticated Kick broadcaster ID. Every private read and download is checked against that connected creator account. Kick access and refresh tokens are encrypted at rest. Streamwright’s private beta runs as a single production service with encrypted transport, persistent storage, and restricted operational access.
Sharing and service providers
Streamwright uses hosting, persistent storage, and monitoring providers only to operate and protect the service. Those providers process data on Streamwright’s behalf under their own security and data-protection terms. Streamwright does not give stream or clip data to advertisers. Information may also be disclosed when required by law or needed to protect creators and the service.
Retention and deletion
Beta requests, feedback, stream history, creator settings, and finished clips are kept while needed to operate the beta. Temporary source recording chunks are removed after clip rendering. While connected, a creator can request account data export, correction, or deletion through the in-app feedback control; Streamwright will verify the request against the connected account before removing server-side creator records and clips. Disconnecting Kick revokes Streamwright’s current access but is not, by itself, a full deletion request.
Your choices
- Disconnect Kick at any time from the Streamwright dashboard.
- Stop microphone monitoring at any time; closing the page releases microphone access.
- Choose what coaching preferences Streamwright stores.
- Request access, correction, export, or deletion through the in-app feedback control.
Security and changes
Streamwright limits creator data access to the connected account, encrypts browser traffic in production, verifies signed Kick webhooks, and monitors service health. No system is risk-free. Material policy changes will be identified in the product and the effective date will be updated before broader release.