Sharecut Studio keeps episode audio and project data on the machine that runs the editor unless you explicitly create a share link.
Raw recordings, transcripts, edit history, and exports live in your project folder and local cache. The app does not upload episode audio or project JSON to us automatically. First-run bootstrap may download FFmpeg and speech models from public CDNs or upstream mirrors you configure.
When you mint a review or record share, guests reach your session through a token URL. A hosted relay (optional) is a pass-through: it does not store episode audio or project files. While a share is active, audio and media for that share may transit the relay (review mix/proxy, record keepers, guest uploads, and other share routes — not an exhaustive list). The relay also carries session metadata, presence, and WebRTC signaling. If you configure Spaces, review mix/proxy are uploaded to a private object-storage bucket (durable while the share is active; not relay pass-through) and guests fetch from there instead of the tunnel. Live conversation audio is typically peer WebRTC via STUN; TURN is not shipped yet. You can revoke shares from the host. Detail: host-online relay docs.
Beta builds include no telemetry and no automatic crash reporting. Nothing is phoned home on errors. You may choose to attach a sanitized diagnostics zip when filing a bug.
Remote guests typically need the host online while recording. Expect the host machine to stay reachable for the duration of a live room; exact uptime targets for beta are still being documented.
Use
GitHub Issues
with the bug report template. Attach a diagnostics bundle from
Home → Help → Create diagnostics bundle or
podcast doctor --bundle if you have one — do not attach episode
audio or project files. Minted shares may transit the relay; that is not a
reason to attach episode files here.