Privacy policy

Effective and last updated: August 21, 2026

Overview

StreamDecky is a free and open-source Windows desktop application maintained by BenjiButten. It does not require an account, contain advertising or analytics, or send telemetry or crash reports to the maintainer. Profiles and user-entered content remain on the user's computer unless the user deliberately copies, types, exports, or shares them.

Information stored locally

StreamDecky may store the following information under %LOCALAPPDATA%\StreamDecky:

• profiles, layouts, button actions, hotkeys, quick text, sticky notes, and application settings;
• form templates, form submissions, counters, and autocomplete history;
• profile backups and migration backups;
• cached overlay images and references to local files selected by the user;
• the DeepSeek and Brave Search API keys, model, thinking levels, search mode, and the spell-fix and answer prompts for the optional text helper widget, in app-settings.json. The key is protected with Windows DPAPI for the current user account and is deliberately kept out of profile exports;
• the time of the most recent update check; and
• diagnostic logs containing operational messages, local paths, and error details.

Form history is limited by the application to 300 submissions per profile and 50 values per autocomplete field. Diagnostic logs remain until the user deletes them. StreamDecky does not automatically upload local data. A user may choose to provide a profile or log when asking for support. Local data can be removed by closing StreamDecky and deleting %LOCALAPPDATA%\StreamDecky. Profiles or form history that should be retained must be exported or backed up first.

Clipboard, input, and local integration

At the user's direction, StreamDecky can place configured text on the Windows clipboard or simulate keyboard input into the previously active application. Apart from the optional text helper widget described under Network communication, StreamDecky does not transmit that content over the Internet, but the receiving application may process or transmit it under its own privacy policy. The optional MicMixer integration uses a same-user local named pipe and does not expose the data as an Internet service.

Network communication

• Release builds contact the GitHub API when the main window is open to check for updates, at most once every 12 hours. The request identifies itself as the StreamDecky updater. GitHub receives normal connection information such as the user's IP address and request metadata.
• If the user accepts an offered update, StreamDecky downloads the release archive and checksum from GitHub, verifies the SHA-256 checksum, and installs the update.
• The text helper widget is off until the user enables it and enters a DeepSeek API key. When the user presses Fix spelling (or Ctrl+Enter in the widget), StreamDecky sends the text currently in the widget, together with the configured correction prompt, to DeepSeek's chat completions endpoint at api.deepseek.com using that key, and replaces the text with the answer. The Test Key button in Settings sends a fixed sample sentence built into the application instead, never the user's own text. No other StreamDecky content is sent, and nothing is sent while the widget is merely open. Text sent this way is processed by DeepSeek under the DeepSeek Privacy Policy and the terms of the user's own DeepSeek account.
• The same widget's Ask button (or Ctrl+Shift+Enter) sends the question in the widget, together with the configured answer prompt and the current date, to the same DeepSeek endpoint. Nothing is sent unless the user presses it.
• If the user has also entered a Brave Search API key, Ask may additionally send a search query to Brave's web search endpoint at api.search.brave.com using that key, and the results are sent on to DeepSeek so the answer can be written from them. The query is either the user's question or a rephrasing of it produced by the model. Whether a search happens at all is controlled by the When to Search setting, which can be set to Never search to stop StreamDecky contacting Brave entirely; with no Brave key, no search is ever made. The Test Key button for Brave searches a fixed built-in term, never the user's own question. Queries sent this way are processed by Brave under the Brave Privacy Policy and the terms of the user's own Brave Search API account.
• Links opened by the user, including project and release links, are handled by the user's default browser and the destination site's privacy policy.

GitHub processes connection information under the GitHub Privacy Statement.

Data received by the maintainer

The maintainer receives no personal data directly from normal application use. Information voluntarily submitted through GitHub issues, support conversations, exported profiles, or log files is handled through the service where the user submits it and is used to answer the request.

Changes and contact

Material changes to this policy will be published in the source repository and on this page. Questions or privacy requests can be submitted through StreamDecky's GitHub issue tracker.