Legal and privacy

Local-first by design

Tempest Streaming Studio keeps its control service, Browser Sources, alert media, configurations, playback history, and backups on the user's computer unless the user chooses to export or share a file. Studio does not include analytics, advertising tracking, or automatic crash-report uploads.

When Studio connects to the internet

Network requests occur when a user connects Twitch or Discord, pairs a public Twitch Extension, uses a Tempest Streaming interaction, checks for software updates, or enables an optional provider. Optional providers can include GIPHY, the National Weather Service, AzuraCast, 7TV, BetterTTV, and FrankerFaceZ. Those services receive only the information needed for the feature the user selected.

Tempest Signal and the Twitch Extensions

The free Tempest Streaming Studio Extension and the separate Bits-enabled Extension named Tempest Streaming connect through Tempest Signal. Pairing either Extension is optional. Tempest Signal validates the broadcaster's Twitch authorization, then discards the access token used for that validation. The service 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 selected panel appearance. The panel appearance contains display text, colors, and layout choices—not local media, file paths, OAuth tokens, or application secrets.

Twitch-signed viewer tokens, opaque viewer identifiers, and request identifiers are processed to authenticate, rate-limit, and deduplicate interactions. They are held only for the active request or replay window and are not written to the installation database. The free Studio Extension does not contain a Bits flow.

Tempest Streaming and Bits

Tempest Streaming lets an eligible, signed-in Twitch viewer use Bits for a specific Extension-defined interaction. Twitch presents and confirms the Bits exchange. Tempest Mainframe does not collect payment-card, bank-account, billing-address, or Bits-balance information and cannot access the viewer's Twitch password.

After confirmation, Tempest Signal receives a Twitch-signed transaction receipt containing the viewer's numeric Twitch user ID, product SKU, Bits amount, transaction ID, and timestamp. Tempest Signal uses those fields to verify the receipt, prevent duplicate delivery, confirm that the product maps to an interaction published by the channel's connected Studio, and route that interaction. Receipt data is retained only in bounded service memory for the active request and replay window and is not written to the installation database. Twitch maintains the viewer's Bits balance and Twitch-side transaction history under Twitch's policies.

Service providers and disclosures

Tempest Mainframe does not sell personal information or use Extension activity for targeted advertising. Twitch processes identity and Bits activity needed to operate its platform. Cloudflare, Railway, and other infrastructure providers may process network information such as IP addresses, request headers, and security logs as needed to deliver and protect the website and Tempest Signal. Information may also be disclosed when required by law or reasonably necessary to investigate fraud, abuse, or a threat to the service or its users.

Discord authorization and guest profiles

Tempest Signal forwards one-time Discord authorization codes and refresh requests to Discord's OAuth service because the desktop application must not contain the Discord client secret. It returns the resulting token to Studio and does not retain that token. Studio protects Discord tokens with Windows encryption.

The local Discord guest library can store user IDs, usernames, display names, Discord avatar URLs, last-seen voice-channel details, and streamer-assigned image and layout settings. Discord messages are not read or stored. Saved guest profiles remain local and are included only in a backup the streamer creates.

Control and deletion

Disconnecting an account removes its locally protected authorization. Forgetting a Discord guest removes that saved local profile. Revoking a public Twitch Extension installation deletes its hosted installation record, appearance, and catalog. Viewers can stop using either Extension at any time; Twitch controls Twitch-side identity and transaction records. Uninstalling Studio does not automatically remove the local data directory, allowing a user to preserve their settings for a later installation. Privacy and deletion questions can be submitted through the contact methods at the end of this page.

Website and external links

The Tempest Mainframe website does not operate a user account system. Links to Twitch, Discord, GitHub, radio hosting, and other third-party services are governed by those services' own privacy practices.

Scope

These terms apply to the Tempest Mainframe website, Tempest Signal, the free Tempest Streaming Studio Extension, and the separate Bits-enabled Extension named Tempest Streaming. Tempest Streaming Studio's source code and executable distribution are licensed separately under GNU GPLv3 as described below.

Acceptable use

Do not use the website or hosted services to break applicable law, interfere with other users, probe or bypass security controls, send abusive automated traffic, impersonate another person, replay or falsify a transaction receipt, manipulate an Extension product, or trigger content you are not authorized to control. Do not use Tempest Streaming for wagering, betting, contests of chance, items with monetary value, or an interaction prohibited by Twitch. Access may be rate-limited or suspended when necessary to protect the service or its users.

Tempest Streaming and Bits exchanges

Tempest Streaming offers predefined interactive stream experiences in exchange for the Bits amount shown by Twitch. A Bits exchange is not a donation, a financial service, or a wager. Twitch operates the confirmation interface, manages Bits balances and account eligibility, and determines any revenue distribution to the broadcaster and Extension developer. Twitch's terms, sale terms, and Bits policies also apply.

Tempest Streaming checks whether the broadcaster's Studio is connected before enabling a Bits interaction, but network, Twitch, hosting, or broadcaster-system failures can still interrupt delivery. Tempest Mainframe cannot change a viewer's Bits balance or Twitch transaction record. Questions about a Twitch account or Bits record must be directed to Twitch; reports about a Tempest interaction that did not run can be submitted through the contact methods below.

Your content and configuration

Streamers remain responsible for the media, custom code, commands, names, and other content they import or display. Only use content you have permission to use. Alert Packs can contain HTML, CSS, JavaScript, and media and should be imported only from trusted creators. A broadcaster who activates Tempest Streaming is also responsible for keeping mapped interactions safe, accurately described, and compliant with Twitch rules. Bits products may not be mapped to a specific musical track or audiovisual work, free-form viewer request, or other prohibited experience.

Third-party platforms

Twitch, Discord, GitHub, Cloudflare, Railway, and optional media providers are independent services. Their availability and rules may change, and use of those platforms remains subject to their own terms. Twitch may restrict a viewer's or broadcaster's eligibility to use Bits or Extensions. Tempest Mainframe is not endorsed by or affiliated with those providers.

Availability and warranties

The website and hosted services are provided on an “as available” basis. Features may change, experience interruptions, or be discontinued. To the fullest extent permitted by applicable law, no warranty is made that the services will be uninterrupted, error-free, or suitable for a particular purpose. The GNU GPLv3 warranty and liability terms apply to the licensed software.

Suspension and termination

Tempest Mainframe may limit, suspend, or revoke access to Tempest Signal or an Extension installation when reasonably necessary to address security risks, fraudulent or abusive activity, Twitch policy violations, legal requirements, or material harm to the service or its users. A broadcaster can revoke an installation from Studio, and Twitch users can remove or stop using an Extension through Twitch.

Changes

Material changes will be reflected by a new effective date on this page. Continuing to use the hosted services after a change means the updated terms apply to later use.

Software license

Tempest Streaming Studio is distributed under the GNU General Public License version 3. The GPLv3—not a separate proprietary EULA—grants the rights to run, inspect, modify, and redistribute the covered software under its terms. The installer presents this license and includes a copy with the application.

Read GNU GPLv3 ↗Third-party notices ↗Trademark policy ↗

Questions

Privacy, licensing, or service questions can be submitted through the public Studio issue tracker or through a verified Tempest Mainframe social channel.

Studio issue tracker ↗Verified social channels