What alerts do in OBS and what they expose

Alerts in OBS Studio are notifications that pop up on your stream when viewers perform actions — following, subscribing, donating, or raiding. They're built to grab attention and reward your audience for supporting you. But alerts also create a direct connection between your streaming software and external services, which means you're sharing data about your viewers and your stream activity with whoever runs that alert service.

When you add an alert, OBS doesn't generate it alone. You connect OBS to a third-party alert provider — services like Streamlabs, StreamElements, Tipeee, or Alerts.tv — and give that service permission to watch your channel for certain events. That service then sends the alert back to OBS to display. Every time someone follows, subscribes, or donates, that event flows through their servers. They see the viewer's name, the action taken, and often the amount donated or the message sent.

The privacy question isn't whether alerts are dangerous — it's whether you're comfortable with that particular service holding that data, and whether you've told your viewers that's happening. Many streamers don't realize their alert provider is also collecting analytics on their stream, storing viewer information, or selling aggregated data about streaming trends.

Key Takeaways

  • OBS alerts require you to connect to an external service like Streamlabs or StreamElements, which then sees every follower, subscriber, and donation on your channel.
  • Different alert services have different privacy policies — some store viewer data longer than others, and some use it for analytics or marketing purposes.
  • You can reduce what you share by choosing a service with a clear privacy policy, limiting the data fields the alert displays, and telling viewers what happens to their information.
  • If you want alerts without a third party, you can use OBS's built-in browser source feature to display alerts from your own server or a privacy-focused alternative.
  • Disabling alerts entirely is always an option — many successful streamers use text-based chat notifications instead.

How alerts flow through OBS and where your data goes

OBS itself doesn't store alert data. When you set up an alert, you're creating a link between OBS and an external service. Here's the actual flow: a viewer follows your channel on Twitch or YouTube. That platform sends a notification to the alert service you've chosen. The alert service receives that notification, stores it in their database, and sends a signal back to OBS telling it to display the alert graphic and sound you configured.

The alert service sees the viewer's username, the timestamp, and the action type. If it's a subscription or donation, they also see the amount and any message the viewer included. They store this information on their servers. What they do with it depends on their privacy policy — some delete it after 30 days, some keep it indefinitely, and some use it to build analytics dashboards that show you trends about your audience (which means they're analyzing the data even if they don't sell it).

The risk isn't that the alert service will misuse your data maliciously. The risk is that you've handed them a detailed log of your stream's financial activity and your audience's behavior, and you may not know how long they keep it, who can access it, or whether they use it for purposes beyond displaying alerts.

Choosing an alert service based on what it collects

Not all alert services collect the same information or keep it for the same length of time. Before you connect one to OBS, read its privacy policy — specifically the sections on data retention and data use. Look for answers to these questions: How long do they store alert data? Do they use it for analytics? Do they share it with third parties? Do they allow you to delete your history?

Streamlabs (owned by Logitech) stores your alert history indefinitely and uses it to generate analytics dashboards. They have a detailed privacy policy, but the default is that your data stays in their system. You can request deletion, but it's not automatic. StreamElements also stores alert data and offers analytics, but they're more transparent about letting you control what data they collect — you can disable certain tracking features in settings. Tipeee is a European service that follows GDPR rules, which means stricter data retention limits and clearer deletion rights. Alerts.tv is smaller and less documented, so their privacy practices are harder to verify.

If privacy is your priority, look for a service that offers a data deletion option, doesn't use alert data for analytics without your consent, and has a privacy policy you can actually read and understand. Some streamers choose services based in Europe (which fall under GDPR) because European privacy law is stricter than U.S. law.

Setting up alerts in OBS with minimal data exposure

Once you've chosen a service, the setup process is similar across most platforms. You'll authorize OBS to connect to your streaming account (Twitch, YouTube, or another platform), then authorize the alert service to read events from that account. OBS itself doesn't need special permissions — it just displays what the alert service tells it to display.

To reduce what you're sharing, configure your alert settings to show only what you need. Most alert services let you choose which events trigger alerts — you can turn off alerts for follows if you only care about subscriptions and donations, for example. You can also limit the data displayed in the alert graphic itself. If the service offers a field for "viewer message," you can disable it so that private messages don't flow through the alert service's servers. Some services let you set a minimum donation amount before an alert triggers, which reduces the number of transactions the service records.

In OBS itself, add the alert as a browser source. The alert service will give you a URL to paste into OBS. That URL tells OBS where to pull the alert graphic and animation from. When you go live, OBS loads that URL and displays alerts as they come in. The connection is one-way — OBS receives the alert, displays it, and that's it. OBS doesn't send data back to the alert service about your stream.

Using OBS browser sources to host alerts yourself

If you want alerts without handing your data to a third party, you can host your own alert system using OBS's browser source feature and a straightforward web server. This requires more technical setup, but it means all your alert data stays under your control.

The basic approach: you create a straightforward HTML file that listens for events from your streaming platform (using that platform's API), displays an alert graphic when an event happens, and stores the data on your own server or not at all. You then add that HTML file as a browser source in OBS. Services like Streamlabs Desktop (the standalone app, not the web service) can do this locally without sending data to Streamlabs' servers, though it requires configuration. Alternatively, you can use open-source alert systems like Notifo or Owncast (if you're self-hosting your stream), which you control completely.

This route is best if you're comfortable with basic web setup or have someone helping you. It eliminates the middleman and keeps your viewer data private, but it also means you're responsible for maintaining the system and handling any technical issues that come up.

What to tell your viewers about alerts and data

Transparency matters. If you're using alerts, your viewers should know that their follow, subscription, or donation information is being sent to an external service. You don't need to make a big announcement, but it's fair to mention it in your channel panels, in your stream description, or in a chat command.

A straightforward statement like "We use [Alert Service Name] to display alerts on stream. When you follow, subscribe, or donate, that information is processed by [Service Name] according to their privacy policy" is enough. It tells viewers what's happening and points them to the service's privacy policy if they want more details. Some streamers add a link to the alert service's privacy page in their channel description.

This is especially important if you're streaming to an audience that includes minors or people in regions with strict privacy laws (like Europe). In those cases, you may need explicit consent before connecting an alert service, depending on your local laws and the service's terms.

Alternatives to alerts if you want to avoid third-party services

Alerts aren't mandatory. Many successful streamers use chat-based notifications instead — when someone subscribes or donates, you straightforward announce it in chat yourself or use a chat bot to post a message. This keeps all the data on your streaming platform (Twitch, YouTube, etc.) and doesn't require a third-party alert service.

Chat bots like Nightbot or Streamlabs Chatbot can post automated messages when certain events happen, but they still connect to external services. If you want to avoid that entirely, you can use your streaming platform's native features — Twitch has built-in alerts for subscriptions and raids, and YouTube has Super Chat notifications. These stay within the platform and don't require additional services.

Another option is to disable alerts during your stream and review them afterward in your streaming platform's dashboard or your alert service's history. This removes the real-time visual element but keeps the data flow minimal and under your control.

Frequently Asked Questions

Can I use alerts without connecting OBS to an external service?

Not with traditional alerts. OBS needs an external service to watch your channel and send alert signals. However, you can host your own alert system on a server you control, or you can skip alerts entirely and use chat notifications instead.

Do I need to tell my viewers that I'm using an alert service?

It's good practice to disclose it, especially if your audience includes people in regions with strict privacy laws. A straightforward note in your channel description or a chat command explaining which service you use and linking to their privacy policy is sufficient.

What happens to alert data if I stop streaming or delete my account?

That depends on the alert service's policy. Some services delete data when you close your account, others keep it. Check the service's privacy policy or contact their support to find out. You can also request deletion manually in most cases.

Is it safer to use a smaller alert service or a big one like Streamlabs?

Bigger services usually have more transparent privacy policies and more resources to protect data, but they also collect more data by default. Smaller services may be more privacy-conscious, but they're harder to verify. Read the privacy policy of whichever service you choose, regardless of size.

Can viewers opt out of having their data sent to the alert service?

Not directly through OBS or most alert services. Viewers can choose not to follow, subscribe, or donate, which prevents their data from being sent. Some services let you disable certain alert types (like follow alerts), which reduces the data collected overall.