Legal

Privacy Policy

Last updated: 13 October 2026 · Effective for streamifyexpress.com, the StreamifyExpress Windows desktop application, bots and OBS widgets.

1. Who we are

StreamifyExpress (“we”, “the service”) provides tools for live-stream creators, including stream notifications, a multi-platform chat, moderation, event history, OBS overlays and configurable widgets. Operator: Brykov Nikita Vyacheslavovich. INN: 262312550889. Contact: notification@streamifyexpress.com.

2. Data we collect

• Account and authentication data: email, display name, password hash, session and security data, Telegram or MAX identifiers when you use or link those services.
• Connected destinations: identifiers and titles of chats, groups or channels that you authorise StreamifyExpress bots to use.
• Connected streaming platforms: platform name, channel URL, channel name, stable channel identifier, granted OAuth scopes, access token, refresh token and token expiry.
• YouTube API Data: your YouTube channel identifier, name and URL; your broadcasts and videos, including identifiers, titles, descriptions, categories, tags, schedules, live status and available viewer statistics; live-chat identifiers, messages, message identifiers, timestamps, author channel identifiers, display names, profile images and roles; supported Super Chat, Super Sticker, membership and public subscription events.
• Creator instructions: messages you ask us to send, moderation actions you initiate, and title, description or category changes you submit for your own broadcast.
• Service configuration: notification templates, schedules, rules, TTS and widget settings, public-page content and other preferences you choose to save.
• Friends and private messages: your friend code, friendship requests, relationships and blocks, message text, timestamps, and read positions. We store these on the server to synchronise your conversations between the website and Windows app. Access to private conversations through the service is restricted to their participants. These messages are not end-to-end encrypted. Removing a friend or blocking a user does not delete the conversation history; the account-deletion policy below applies.
• Technical data: session cookies, CSRF tokens, application version, provider health state and limited request/error logs required to operate and protect the service.

2a. Your device, cookies and similar storage

StreamifyExpress stores information on your device and accesses it to provide the features you use. Our website uses first-party cookies for login sessions, pending identity linking and language selection. Authentication cookies help identify your signed-in session; they are not advertising cookies. Requests also transmit technical information such as your IP address and browser user agent to our servers and hosting provider for delivery and security.

We use browser localStorage for preferences such as theme, language and chat appearance, and sessionStorage for temporary sign-in return routes and payment-flow state. Remote OBS controls may store a layout in localStorage and an access key in sessionStorage. Persistent preferences remain until you change them or clear site data; sessionStorage is normally cleared when its tab is closed. Session cookies expire or are invalidated when you sign out. You can block cookies or clear cookies and site storage in browser settings, but doing so may sign you out, reset preferences or prevent authentication and other features from working.

The Windows application stores settings and cache files on your computer, including window, chat, OBS and widget preferences. Its credential store keeps the credentials needed for your desktop session. Camera and microphone access requires your permission and is used for the corresponding avatar or audio features. You can manage access in Windows privacy settings.

Third parties may also store or access information on your device when you open their OAuth sign-in or payment pages, load their embedded players, images or other external content, or follow their links. For example, Google/YouTube may receive your IP address and browser information and use its own cookies under the Google Privacy Policy. Other providers, including Twitch, Telegram and YooKassa, apply their own privacy and cookie policies on their services. We do not control those cookies; use the provider's privacy controls and your browser settings to manage them. We do not use YouTube API Data for advertising cookies or third-party advertising tracking.

3. How we use data

• To authenticate you and maintain your web and desktop sessions.
• To manage friendships and deliver and synchronise private messages and read positions.
• To verify and display the streaming channels you explicitly connect.
• To determine whether your own broadcast is actually live and send configured notifications.
• To show clearly labelled platform messages and events in your multichat and event journal.
• To perform only the chat, moderation and broadcast-metadata actions that you initiate.
• To render your selected OBS overlays and widgets and apply your saved settings.
• To prevent abuse, diagnose failures and improve reliability and security.

We do not sell personal data or YouTube API Data. We do not use Google user data for advertising, credit decisions or unrelated profiling.

4. Google and YouTube API Services

StreamifyExpress uses YouTube API Services. Connecting YouTube is optional and starts only after you press the connection button and approve the Google OAuth consent screen. New connections request the youtube.force-ssl scope, which is required for the creator-facing reads and writes described above. We do not ask for your Google password.

We use documented YouTube Data API and YouTube Live Streaming API methods to identify your channel and active broadcast, receive live-chat messages, send messages, carry out moderation, retrieve supported creator events and update metadata of your own broadcast. YouTube data is visibly attributed to YouTube and remains separate from data supplied by other platforms.

By using the YouTube integration, you also agree to the YouTube Terms of Service . You should also review the Google Privacy Policy . Our use of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

5. Storage, refresh, deletion and revocation

• OAuth tokens are kept server-side while the integration remains connected and are never intentionally exposed on public pages or sent to OBS widgets.
• Time-sensitive YouTube metadata is refreshed through the API when the relevant feature is used. Channel names are scheduled for refresh every seven days. Metadata that cannot be refreshed is discarded after 28 days; your saved channel selection may remain as an identifier. Chat and event history expires after 28 days: reads exclude expired records, and hourly maintenance removes them even for inactive accounts (normally within 29 days). History may be removed sooner because it is also size-limited.
• When you disconnect YouTube in Integrations / Platforms, StreamifyExpress immediately deletes the stored YouTube OAuth tokens and cached YouTube message/event data for that channel and sends a revocation request to Google.
• You can independently revoke StreamifyExpress access at any time on the Google Account permissions page . If the service can no longer verify authorisation, the affected authorised data is deleted no later than 30 calendar days afterwards.
• Account and configuration data is retained while your StreamifyExpress account is active. You may request account and personal-data deletion by emailing notification@streamifyexpress.com from the account email. YouTube API Data covered by a verified deletion request is deleted as soon as possible and within seven calendar days. Requests for other account data are completed within 30 calendar days, except records we are legally required to retain, such as accounting records.

6. Sharing

We disclose data only to processors and providers needed to deliver a feature you use, such as hosting, email delivery, Telegram, MAX, Google/YouTube APIs, Twitch, Kick and YooKassa. Authorised YouTube API Data is shown only to the authorising creator and representatives to whom that creator explicitly grants access. Public pages expose only content the creator deliberately publishes. We do not disclose YouTube API Data to data brokers.

7. Security

We use HTTPS, hashed passwords, server-side access controls, CSRF protection and restricted access to credentials. No storage or transmission method is completely risk-free. If we learn of a security incident affecting your data, we will act and notify affected users as required.

8. Your rights

Depending on your jurisdiction, you may request access, correction, export, restriction or deletion of your personal data by emailing notification@streamifyexpress.com. We may ask you to verify that you control the affected account before fulfilling the request.

9. Children

The service is not directed to children under 13 or below the minimum age required to manage their own Google Account in their country.

10. Changes

We may update this policy when the service or legal requirements change. The effective date above will be updated, and material changes will be communicated through available service channels where required.