StreamSavantBack to the website

Your information

Privacy Policy

Updated October 31, 2026

StreamSavant is a desktop streaming control app. This page explains the information used by the app, this website and the services that support licensing and payments.

For privacy questions or a request concerning information held by StreamSavant, contact [email protected].

Streaming accounts and YouTube

You choose which accounts to connect. StreamSavant uses YouTube API Services to find your channel and active or upcoming broadcasts, obtain the streaming server and key, display live chat, and update a stream title or description when you request it. The Google permission includes broader video-management capabilities; StreamSavant does not use this connection to create or delete broadcasts or videos.

Google sign-in takes place in your browser. The app receives authorization tokens, not your Google password. Tokens, selected broadcast information and imported stream credentials are saved on your computer. Requests for Google data go directly from the desktop app to Google. This data is not sent to StreamSavant’s licensing or payment services.

The Google connection uses data for these visible streaming and chat features. The desktop app does not send Google data to advertising services, data brokers or general-purpose model-training services. Its use of Google data is limited to the features you choose, in accordance with the Google API Services User Data Policy and its Limited Use requirements. Google’s own handling of information is described in the Google Privacy Policy.

Twitch and Kick connections similarly use account authorization and platform APIs to connect your channel, obtain available stream settings and support chat and channel controls. For Kick connections made through StreamSavant’s sign-in service, authorization codes and tokens pass through a Supabase-hosted exchange service to communicate with Kick; that service does not write them to a database. Abuse-prevention counters use HMAC-derived identifiers rather than storing raw IP addresses. They expire after the rate-limit window plus two hours; expired rows are removed when later requests run cleanup. Manually configured developer-app connections exchange tokens directly with the platform. The resulting account tokens are stored locally.

Chat, media and local controls

The chat feed uses message text, display names, message identifiers, timestamps, and available badge or emote information. Its recent-message buffer is kept in app memory. If you enable overlays, notifications, text-to-speech or streaming output, that content may be displayed or heard in OBS and your broadcast. Streaming platforms, viewers and recordings can retain what you broadcast.

Microphone features use on-device Whisper transcription for commands, dictation and subtitles. Model files are downloaded when needed. Text can be placed on the clipboard, sent to another application or shown in a stream when you enable those actions. Text-to-speech uses system voices; its history and settings are saved locally. Diagnostic output can contain chat or transcription text, so review logs before sharing them with support.

Settings such as OBS connection details, stream keys, layouts, local media references and device preferences are stored on your computer. Protect access to your device and backups: local configuration files can contain sensitive credentials.

Licenses, trials and payments

Trial and license checks send a machine identifier, and for license activation a license key and device name, to our Supabase service. Licensing records include activation and check dates, plan/status information, and the purchase email. Trial records are used to recognize an existing trial after the app is reinstalled.

Stripe handles checkout and payment details. StreamSavant receives purchase email, customer/subscription/checkout identifiers and payment-status events to issue or update a license. License email is delivered through Resend. Service diagnostics can include purchase and license identifiers. Deactivating a device or deleting local files does not delete these server-side purchase or trial records. Contact support about access, correction or deletion of those records; Stripe also controls the payment records it processes.

Website and service providers

Visiting the website, checking for app updates, downloading models or emotes, and using payment or sign-in services sends ordinary request information, such as your IP address and browser or app headers, to the relevant hosting or service provider. The homepage loads fonts from Google Fonts and animation code from a public CDN. Stripe and other linked services apply their own privacy policies and may use their own cookies or storage.

Information you choose to send by email or through the community is handled by the corresponding email or community provider. Please do not send passwords, stream keys or authorization tokens.

Disconnecting and removing data

  1. YouTube: stop streaming, open the YouTube connection and choose Sign out. The app requests revocation at Google, removes its local OAuth tokens and chat selection, clears the YouTube feed, and removes unchanged stream connections recorded as imported by the automatic setup. If Google cannot confirm revocation, the app tells you.
  2. Google account access: you can independently revoke StreamSavant in Google Account permissions. While the app is running, it periodically checks authorization. When Google reports that the authorization is no longer valid, the app clears its tokens and queues removal of the related imported connection and OAuth chat data. You can also choose Remove saved YouTube data in the app. Cleanup waits until streaming has stopped so it does not interrupt a live output.
  3. Manual or older saved keys: independent manual settings, custom destinations and connections from versions that did not record their origin may remain. Use Manual setup → Remove stream key for those entries. Remove any separate copies in OBS, other applications or backups, and rotate the key on the platform if you need to invalidate it.
  4. Chat and device data: Clear Chat removes the app’s recent-message feed. Closing the app clears its in-memory chat. To remove all local app configuration, close the app and remove its .stream-savant folder in your home directory and its stream-savant application-data folder. On Windows the latter is normally under %APPDATA%; on macOS it is under ~/Library/Application Support. This also removes other saved settings and local license information. Separately remove downloaded models or exported files you no longer want.

Imported YouTube stream connections and OAuth chat selections carry a freshness date. While the app is running, it rechecks aging connections before thirty days and keeps them when Google confirms the same broadcast, server and key. Successful chat reads keep the current chat selection fresh. Saved values that cannot be confirmed are removed after thirty days; you can use automatic setup to obtain current values. Removal is deferred while a stream is active. A closed app cannot check authorization or erase files, and an offline app cannot verify Google access; you can still remove local data yourself. Deleting app data does not delete your channel, videos or data held by YouTube.

Other local settings and histories remain until removed or replaced; the recent chat buffer is limited in size. Server-side licensing and trial records do not have an automatic expiry in the current service. Requests to remove information held by StreamSavant should be sent to support. Copies held by streaming platforms, payment providers, email providers, viewers or your backups are outside the app’s local deletion controls.

Changes and contact

This page will be updated when the described data handling changes. Review the date above. Contact [email protected] with questions or requests.