Privacy policy
What this policy covers
This policy applies to tempestmainframe.com and its hosted routes, Tempest Streaming Studio, the Tempest Signal relay, the free Tempest Streaming Studio Twitch Extension, the Bits-enabled Tempest Streaming Twitch Extension, Discord Guests, supported Kick integrations, Storm Horizon Radio playback and downloads, and optional third-party integrations enabled inside a Tempest product.
Local-first Studio data
Studio keeps configurations, Browser Sources, alert media, playback history, guest profiles, and backups on the user's computer unless the user deliberately exports, uploads, or shares them. Studio does not include advertising trackers or automatic crash-report uploads. Local data stays under the computer owner's control and is not automatically removed when Studio is uninstalled.
Connected platforms and optional providers
Network requests occur only when a user opens the website or uses an online feature, such as connecting Twitch, Discord, or Kick; pairing a Twitch Extension; checking for updates; playing or downloading music; or enabling an optional provider. Optional providers can include GIPHY, the National Weather Service, AzuraCast, 7TV, BetterTTV, and FrankerFaceZ. Each provider receives the request and identifiers needed to perform the feature selected by the user and applies its own privacy terms.
Tempest Signal and Twitch Extensions
Tempest Signal validates broadcaster authorization and relays selected Extension interactions to a paired Studio installation. It stores the Twitch channel ID and login, a random installation ID, a one-way hash of the relay credential, timestamps, a viewer-safe interaction catalog, and the channel's chosen panel text, colors, and layout. It does not receive local media, local file paths, or Studio application secrets.
Twitch-signed viewer tokens, opaque viewer identifiers, request identifiers, and—when a Bits interaction is used—transaction receipt fields are processed to authenticate, rate-limit, deduplicate, and route the interaction. Tempest Mainframe does not receive payment-card, bank-account, billing-address, Twitch-password, or Bits-balance information.
Discord Guests
Discord Guests uses Discord's official OAuth2 and local RPC connection so Studio can identify the current voice session and present selected guests on stream. Studio can read the Discord user and voice information needed for that display, such as user IDs, usernames, display names, avatar URLs, voice-channel details, and voice membership events. It does not request the messages.read scope, read message contents, or operate a self-bot.
Tempest Signal forwards the one-time authorization code or refresh request to Discord because the desktop application must not contain the Discord client secret. Signal returns the result to Studio and does not retain the Discord access or refresh token. Studio protects the token with Windows encryption. Saved guest profiles remain local unless the user puts them in an exported backup. See the Discord Guests explanation.
Music playback, human verification, and download limits
Public music playback does not require a Tempest account and does not use the download allowance. Cloudflare Turnstile performs an anonymous bot check only when a listener requests a permanent download. Tempest does not create an account or collect a name, email address, or password for that process. A short-lived signed browser pass expires after 24 hours. To enforce the daily allowance and protect hosting costs, the download service temporarily stores salted one-way hashes of the anonymous pass and source network address, the requested asset ID and type, and a timestamp. These download events are deleted after 48 hours. Raw pass identifiers and raw IP addresses are not written to the download-events database.
Service providers, logs, and disclosure
Tempest Mainframe does not sell personal information or use product activity for targeted advertising. Cloudflare, Railway, GitHub, Twitch, Discord, Kick, radio hosting, and other infrastructure or platform providers may process network details, request headers, security logs, and platform identifiers as needed to deliver and protect their services. Information may also be disclosed when required by law or reasonably necessary to investigate fraud, abuse, a security incident, or a threat to users or the service.
Your choices, retention, and deletion
Users can disconnect platform accounts in Studio, forget saved Discord guests, revoke an app in the relevant platform's authorization settings, stop using an Extension, or delete local Studio data and backups. Hosted installation records are kept only while needed to operate and secure the connected feature. Requests about access or deletion can be made through the support page.
Changes and questions
Material changes appear here with a new effective date. The existing combined legal record remains available at /legal. Questions about this policy, an authorization, or a deletion request can be sent through the verified contact routes listed on /support.