Privacy Policy for Social Stream Ninja

Last Updated: April 11, 2026

Social Stream Ninja is open-source software for capturing, relaying, displaying, and automating live chat and related stream events. This policy applies to the Social Stream Ninja browser extension, the hosted Social Stream Ninja pages and overlays, and the standalone desktop app commonly referred to as SSAPP, which loads substantially the same Social Stream logic.

1. Scope and General Approach

Social Stream Ninja does not require a central user account to use the core software. However, depending on how you configure it, the software may access, process, store, and transmit information that may qualify as personal information under some laws.

In many cases, the software operates locally on your device and under your control. However, some features use third-party platforms, user-configured destinations, or hosted helper services, and those services may receive data needed to perform the requested feature.

2. Information the Software May Process

Depending on the features you enable, Social Stream Ninja may process the following categories of information:

• Authentication information: OAuth access tokens, refresh tokens, API keys, client IDs, client secrets, channel or room credentials, session tokens, passwords, and similar authorization data entered by the user or granted by a connected service.
• Personal communications: Chat messages, replies, chat commands, moderation actions, membership messages, donation messages, support messages, and other user-submitted communications received from connected platforms.
• Web history and page context: Supported page URLs, tab information, channel names, usernames, video IDs, room IDs, stream identifiers, and related page context needed to connect to or monitor a source.
• Website content: Chat DOM content, message content, event content, stream metadata, viewer counts, badges, emotes, profile images, and other content available on supported pages or APIs.
• Personally identifiable information and profile data: Usernames, display names, avatars, account or channel IDs, badges, name colors, membership status, follower/subscriber labels, and similar profile metadata.
• Configuration and local app data: Settings, connected sources, custom commands, blocklists, allowlists, local caches, file-handle information, and other data needed to keep the software working on your device.
• Optional media and file data: If you enable optional capture, export, ticker, logging, or file features, the software may process selected local files, exported files, tab/media capture data, or user-created backups.

3. How the Information Is Used

Social Stream Ninja may use that information to:

• Connect to supported chat, event, and stream sources.
• Display chat messages, overlays, dashboards, alerts, waitlists, polls, scoreboards, and related interfaces.
• Perform moderation, filtering, automation, relay, bot, TTS, AI, translation, or export features that the user enables.
• Authenticate with third-party platforms and maintain source sessions.
• Cache lookups and maintain local app state so the software continues working between sessions.
• Send data to destinations explicitly configured by the user, such as webhooks, local files, local websocket endpoints, third-party bots, or other services.

4. Local Storage and Device Storage

Social Stream Ninja stores a significant amount of working data locally on the user's device. Depending on the surface in use, this may include browser storage, localStorage, sessionStorage, IndexedDB, extension storage, Electron app storage, and optional files chosen by the user.

This local data may include settings, connected source details, cached channel or profile lookups, message history if the user enables it, and authentication/session data needed for enabled features.

The standalone desktop app may also keep local recovery backups of settings and source storage on the device. Those local backups may include OAuth tokens or other session state so the app can restore a previous working session after restart or failure.

5. When Data May Leave Your Device

Depending on how you use the software, information may be transmitted off-device in the following situations:

We do not sell user data.

Social Stream Ninja is not designed to transfer user data beyond the transmissions described in this policy, which may occur when you use connected platforms, user-enabled features, user-configured destinations, required helper or service providers, or when security or legal obligations require it.

• Connected platforms and APIs: When you connect YouTube, Twitch, Kick, Facebook, Discord, or other supported services, the software sends requests to those platforms and may receive or transmit chat, event, profile, and auth-related data.
• Hosted helper services: Some features use helper endpoints or hosted pages for auth, lookups, transport, chat, or fallback assets. Examples in current builds include Social Stream Ninja or related helper domains used for auth exchange, lookups, or hosted pages.
• User-configured destinations: If you enable webhooks, relays, bots, AI providers, TTS providers, streamer tools, websocket servers, or other integrations, the software may forward message content, usernames, avatars, event payloads, and related metadata to those destinations.
• Peer or transport services: If you use VDO.Ninja, WebRTC, TURN relays, hidden iframe bridges, or websocket-based transports, data may pass through those systems. Optional websocket transport may not be end-to-end encrypted.

6. YouTube and Other OAuth-Based Features

When you use YouTube API Services or other OAuth-based integrations, Social Stream Ninja may request authorization tokens and related account access needed for the feature you choose to use.

• YouTube: The software may access YouTube live chat messages, message metadata, channel information, avatar information, stream status, moderation endpoints, and viewer or subscriber statistics, depending on which YouTube features you enable.
• Hosted auth helpers: In some builds and modes, OAuth code exchange or token refresh may be handled through a hosted helper service instead of entirely on-device. If you use that mode, auth codes, refresh tokens, and related token request data may pass through that helper to complete sign-in.
• Local token storage: Depending on the feature and sign-in flow in use, tokens may be stored locally on the user's device and may also be sent to helper services if remote exchange or refresh is required.
• Google policy: Your use of YouTube features is also subject to the Google Privacy Policy. You can revoke Google access through your Google account permissions settings.

7. Desktop App Error Reporting

The standalone desktop app includes an optional error-reporting feature that is disabled unless the user enables it.

• If enabled, the desktop app may send error messages, stack traces, app version, a random install ID, context, and sanitized settings to the developer's error-reporting endpoint.
• At the time of writing, the desktop app's in-app disclosure states that OAuth tokens, session data, and backup credentials are excluded from those reports.
• At the time of writing, the desktop app's in-app disclosure states that these reports are sent through a Cloudflare Worker endpoint and retained for 30 days. Users should review the current in-app disclosure before enabling this feature.

8. Third-Party Services and User-Configured Integrations

Social Stream Ninja can interact with a wide range of third-party platforms and user-selected services. Their privacy policies, terms, security controls, and retention practices are separate from this policy and may differ materially.

If you configure the software to send data to third-party services, you are responsible for reviewing those services and deciding whether you are permitted to send that data there.

9. Retention, Deletion, and User Control

Because much of Social Stream Ninja operates locally, retention usually depends on the user's device and configuration.

• Local settings, caches, tokens, and backups may remain on the device until the user clears storage, removes sources, resets the app, deletes exported files, revokes tokens, or uninstalls the software.
• User-configured third-party destinations may keep copies of forwarded data under their own policies.
• Hosted helper services or APIs may log or retain technical request data according to their own practices. This policy does not guarantee any specific retention period for third-party services.

10. Security and Risk

• No absolute security guarantee: No software or networked service is perfectly secure. Use of Social Stream Ninja is at your own risk.
• Session and source credentials: If a stream ID, room ID, token, password, or relay link becomes known to others, those parties may be able to view or inject data depending on your configuration.
• Transport risk: WebRTC, TURN, websocket, webhook, relay, and third-party API traffic may expose information to the services needed to carry that traffic.

11. User Responsibility

The user decides which sites, accounts, chats, and services to connect to Social Stream Ninja; what data to capture; what overlays to display; what files to save; and what external services to relay data to.

• You are responsible for ensuring you have the right and lawful basis to collect, process, display, store, export, or forward any data you handle with the software.
• You are responsible for compliance with the terms of service, privacy terms, and local laws that apply to the services and individuals whose data you process.
• You should treat tokens, passwords, room IDs, stream IDs, and exported data as sensitive.

12. Indemnification and No Warranty

Social Stream Ninja is provided "as is" and "as available," without warranties of any kind, express or implied, including implied warranties of merchantability, fitness for a particular purpose, and non-infringement.

By using the software, you agree that the author, contributors, and service providers are not responsible for claims, damages, liabilities, or losses arising from your configuration or use of the software, including claims related to third-party content, data collection, data forwarding, or legal compliance.

13. Changes to This Policy

This Privacy Policy may be updated from time to time. Continued use of the software after a policy change means you accept the revised policy.

14. Contact Information

For privacy-related inquiries, please contact:

Steve Seguin
Email: [email protected]