Straight answers for your stream.
The practical details behind StreamLoop's automations, platform connections, OBS actions, clips, and creator data.
Will automation feel slow on stream?
Twitch events arrive through the EventSub WebSocket, YouTube live chat uses the existing short polling interval, and OBS actions use a persistent OBS WebSocket connection. Timing can still vary with platform and network conditions, so StreamLoop does not promise a fixed latency.
Could using StreamLoop get my channel banned?
StreamLoop uses the connected platform's OAuth and API permissions and does not bypass platform controls. You remain responsible for your channel, the automations you configure, and following each platform's terms.
Does StreamLoop work with OBS?
Yes. StreamLoop supports OBS WebSocket Protocol 5.x and sends scene and action requests over your configured host and port, with an optional password. No OBS plugin is required.
Who owns the clips StreamLoop creates?
You retain ownership of your clips, subject to the platform's own terms. StreamLoop requests clips through your connected account and stores the resulting platform IDs, URLs, edit links, and available thumbnail metadata for the gallery—not the hosted video files themselves.
What happens to my data?
Data is used to operate your configured automations and account. The app persists connection records, flow definitions, event payloads, and flow-run outputs. Clip media remains on the platform; StreamLoop keeps only the clip references used by the gallery. We do not promise specific encryption, deletion windows, or access controls beyond what is implemented and documented.