Skip to main content

Privacy Policy

Last updated: January 15, 2026

This Privacy Policy explains how Smart Streamer ("the Service") collects, uses, and protects information. By using the Service, You agree to the practices described in this Policy.

1. Information We Do Not Collect

The Company (Smart Streamer developers) does not collect or receive the following information:

  • Home Assistant access tokens (in any form, encrypted or unencrypted)
  • Home Assistant device data
  • Your Home Assistant configuration
  • Your Streamlabs Ultra subscription details
  • Smart home device states or history

Important: Home Assistant access tokens are encrypted and stored in Your Streamlabs user settings (transmitted to Streamlabs for storage). However:

  • The encrypted token is never sent to the Company
  • Streamlabs cannot decrypt the token without Your Streamlabs JWT token and optional PIN (which is never transmitted)
  • The Company has no access to Your encrypted tokens or decryption keys

2. Information We Collect

The Service collects only the minimum information necessary to operate and diagnose issues.

2.1 Telemetry and Error Reports

When an error occurs, the Service may send diagnostic information ("Telemetry Data") to our error‑tracking and performance monitoring provider (currently Bugsnag). This may include:

  • Technical details about the error
  • Application state at the time of the error
  • Your Streamlabs user identifiers (user ID, username, display name) from your connected streaming platform (Twitch, YouTube, Mixer, or Facebook), if provided by Streamlabs)
  • Operating system and environment details
  • Non‑sensitive configuration metadata
  • Performance metrics (page load times, API response times)

The Service is designed to exclude Home Assistant access tokens and other sensitive credentials from Telemetry Data.

2.2 Data Stored in Streamlabs User Settings

The following data is stored in Your Streamlabs user settings (transmitted to Streamlabs for storage):

  • App Configuration: Chat commands, keyboard shortcuts (hotkeys), and event triggers You configure
  • Activity Logs: Local history of automation executions (activity type, automation names, timestamps, success/failure status, and optional details such as command names or error messages) - limited to the most recent 100 entries


This data is stored unencrypted in Streamlabs user settings, but does not contain sensitive credentials or personal information. The Company does not have access to this data.

2.3 No Personal Profile Data

We do not collect personal profile information beyond what is included in error reports. We do not track usage behavior, automation history, or streaming activity beyond the local activity logs stored in Your Streamlabs settings.

3. How We Use Information

Telemetry Data is used solely for:

  • Diagnosing and fixing bugs
  • Improving stability and performance
  • Ensuring compatibility with Streamlabs and Home Assistant

We do not use Telemetry Data for analytics, advertising, or user profiling.

4. How We Store and Protect Information

4.1 Encryption of Home Assistant Tokens

Home Assistant access tokens are encrypted before being stored in Your Streamlabs user settings. The encryption uses:

  • AES-GCM encryption algorithm (256-bit key)
  • Key derivation: A key derived from Your Streamlabs JWT token using PBKDF2 (100,000 iterations)
  • Optional PIN-based encryption: You may choose to add an additional PIN for extra security. When enabled, the encryption key is derived from both Your Streamlabs JWT token and Your PIN, requiring both to decrypt the token.

4.2 PIN Storage

If You choose to use a PIN for additional encryption:

  • The PIN is stored temporarily in Your browser's sessionStorage
  • The PIN is automatically cleared when Streamlabs closes
  • The PIN is never transmitted to the Company or stored in Streamlabs user settings
  • The PIN is required each time You open the Service to decrypt Your Home Assistant token

4.3 Storage Location

Streamlabs User Settings:

  • Encrypted Home Assistant tokens are stored in Your Streamlabs user settings (transmitted to Streamlabs for storage). The Company does not have access to Your encrypted tokens or the decryption keys (JWT token or PIN). Streamlabs stores the encrypted token but cannot decrypt it without Your JWT token and optional PIN, which are never transmitted.
  • App configuration (chat commands, hotkeys, event triggers) and activity logs are also stored in Your Streamlabs user settings. This data is stored unencrypted but does not contain sensitive credentials. The Service includes security measures that automatically prevent sensitive data (such as tokens, passwords, or API keys) from being saved to Streamlabs user settings.

Telemetry Data: Telemetry Data is processed and stored by our error‑tracking and performance monitoring provider (Bugsnag) under industry‑standard security practices. The Company does not store Home Assistant credentials or device data.

Access to Telemetry Data is restricted to the Company for debugging and maintenance purposes only.

5. Sharing of Information

We do not sell, rent, or share Your information with third parties except:

  • Our error‑tracking provider (Bugsnag), for processing Telemetry Data
  • When required by law or legal process

6. Third‑Party Services

The Service integrates with Home Assistant, Streamlabs, and streaming platforms. These services are governed by their own privacy policies. We are not responsible for their data handling practices.

Home Assistant API Calls: The Service uses Your Home Assistant access token to authenticate API calls to Your Home Assistant instance. The token is sent in the Authorization header of API requests. The Service reads data from Your Home Assistant instance (entity states, automations list, services list) and subscribes to WebSocket events for event-driven scene switching. The Service also triggers automations and calls services that You configure. No personal information about You is sent to Home Assistant—only the data necessary to operate the Service (automation triggers, service calls, and data queries). All communication with Home Assistant occurs directly between Your browser and Your Home Assistant instance; the Company does not intercept or store these communications.

7. Data Retention

  • Telemetry Data: May be retained for as long as necessary to diagnose issues and improve the Service. You may request deletion of Telemetry Data associated with Your Streamlabs username.
  • Activity Logs: Stored locally in Your Streamlabs user settings, limited to the most recent 100 entries. Older entries are automatically removed.
  • App Configuration: Stored in Your Streamlabs user settings until You delete or modify it.
  • Encrypted Tokens: Stored in Your Streamlabs user settings until You delete Your configuration or clear all app data.

8. Your Rights

Depending on Your location, You may have rights to:

  • Access the Telemetry Data associated with You
  • Request correction or deletion
  • Request that no further Telemetry Data be collected

To exercise these rights, contact us at hello@howlingcoder.com.

9. Children's Privacy

The Service is not intended for individuals under 18. We do not knowingly collect information from children.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated at least 30 days in advance. Continued use of the Service after changes constitutes acceptance.

11. Contact

For questions about this Privacy Policy, contact us at: hello@howlingcoder.com