Privacy policy for StreamStitch
StreamStitch by Jonah Kowall
Privacy policy for StreamStitch
StreamStitch does not collect or transmit personal data, browsing history, media URLs, credentials, usage analytics, diagnostics, or telemetry outside the local browser.
Local data
- Captured media candidates and request credentials are held in browser session storage.
- Active public-session jobs may retain source URLs in local storage only while recovery is possible. The URL and request-context reference are removed after completion.
- Private-window candidates, jobs, and temporary state use session storage and are not written to seven-day history.
- OPFS stores temporary manifests, fetched byte ranges, checkpoint journals, and muxed output. These files remain local to the extension origin.
- Seven-day history contains only title, format, output size, status, filename, and completion time. It never contains URLs, cookies, or headers.
- Settings are stored locally in the browser.
Browser APIs
Cookies and selected request headers are read solely to replay the source page's authenticated media session for the selected job. Replay is scoped to the manager tab and approved media domains, then removed when the job stops.
Deletion
Users can clear candidates from the popup and clear local history in Settings. Removing StreamStitch causes the browser to remove extension storage, including OPFS, subject to browser behavior.
External services
There are no StreamStitch servers, accounts, analytics providers, advertising SDKs, or payment services. Browser extension stores may process installation data under their own policies.