Privacy
REBot is a bot for streamers on Twitch, Discord and YouTube. This page explains which data comes up, what we need it for and how long we keep it. REBot shows no ads, uses no analytics or tracking services and does not sell data.
Controller
Ricardo EdelmannNeustraße 21
40789 Monheim am Rhein
Deutschland
Email: ricardo@einfachriggo.com
Login and account (streamers and team members)
You log in with Twitch or Discord. We receive your account ID, login name, display name and the address of your profile picture. We do not get a password or your email address. You can change your display name and language under "My account".
To keep you logged in we set a cookie with a random key. We only store a check value of it, together with the browser identifier, IP address and the times of the session. A session lasts at most 30 days and is deleted afterwards; you can log out at any time, also on all devices.
When your account is created we record the time, provider, login name and IP address in the log to detect abuse. This entry is deleted together with your account.
The change log of a channel shows who changed what and when. The owner and team members with the matching permission can see it. It is kept as long as the channel exists.
When you connect your Twitch channel or a bot account, we store the Twitch authorization encrypted and only use it for the features you switch on. When you disconnect or delete, we revoke it at Twitch.
When you connect a Kick account, we store its ID, name and profile picture and the Kick authorization encrypted. With it we subscribe to your channel’s events at Kick (chat, follows, subscriptions, Kicks, live status, bans and rewards). When you disconnect or delete, we unsubscribe them at Kick and revoke the authorization.
The legal basis is your use of REBot (Art. 6(1)(b) GDPR). The logs serve secure operation (legitimate interest, Art. 6(1)(f) GDPR).
Viewers in chats where Bot runs
When a streamer switches REBot on in their Twitch chat, the bot reads the messages to answer commands, award points and – if enabled – moderate. We do not store chat messages. The only exceptions are the following features, if the streamer uses them:
- Moderation: Twitch name and the offending message (shortened) for 30 days, visible to the channel's team with access to moderation.
- Points: Twitch ID, name, balance and bookings, as long as the channel uses points. A public leaderboard with Twitch names only exists if the streamer switches it on. Points have no monetary value.
- Games (slot machine, card packs, fishing, drag race): Twitch ID, name, bet and result of every round for 30 days; bets and wins are also part of the points bookings. During a round, name, bet or price and the result appear in the streamer's browser source, i.e. on stream.
- Drag race: Twitch ID, name, chosen car, amount and win of every bet for 30 days. Whoever bet on the winning car appears with name and win on stream and in chat; every bet is confirmed in chat.
- Collection games (card packs, fishing): Twitch ID, name and every pulled card or catch with its time, plus collection book, rankings and channel records per season. Closed seasons are kept as an archive as long as the channel uses the game. On !packtop or !fishtop the bot names the rankings with Twitch names in chat and shows them on stream. A public page shows rankings, records and each person's collection book (search by Twitch name) only if the streamer switches it on.
- Giveaways: the Twitch names of the participants, plus the Discord ID when entering via Discord. Drawn names appear in chat, on Discord and – if the streamer switches it on – on stream, where names of other participants also run through during the draw. Closed giveaways are deleted over time; the last 20 per channel are kept.
- Linking Discord and Twitch (for giveaways on Discord): ID and name of both accounts, as long as the channel uses REBot. Confirming with Discord shares the accounts connected in Discord with REBot once; only the Twitch account is taken from them. A code for linking is valid for 10 minutes and deleted afterwards.
- Quotes and regulars: the quote text with the name of whoever added it, and the list of regulars, as maintained by streamers or mods.
- Channel points: Twitch ID, name, the redeemed reward and any text entered with it for 30 days, visible to the channel's team.
- Song requests: Twitch ID, name and the requested song. Played, skipped and removed requests stay in the history for 30 days. Song and name may appear in the streamer's browser source, i.e. on stream.
- Greetings: Twitch ID, name and when someone first and last wrote in chat and was last greeted, as long as the channel uses REBot. This applies to everyone who writes in chat, so the bot can recognise new viewers.
Viewers: legal basis
We process this data because the respective streamer uses the feature in their channel and viewers use it in chat (legitimate interest in chat features and a safe chat, Art. 6(1)(f) GDPR). You can direct questions to the streamer or to us.
Discord
When a streamer adds the bot to their Discord server, we store the server ID, name and icon as well as the chosen channels and roles. To update posted messages later we keep their IDs.
Depending on the features switched on, the bot reads messages, reactions, joins, leaves and roles on the server, for example for moderation, automations, achievements, tickets, greetings, giveaways and stat channels. We do not store the text of messages. The only exceptions are the following features, if the streamer uses them:
- Moderation: warnings and actions with the Discord ID and name of the person, the moderator and the reason. We do not store the checked messages.
- Tickets: who opened, claimed and closed a ticket, and on closing the transcript with names, text and attachments. Depending on the settings, the transcript is also posted as a file to a channel of the server and sent by direct message to the person who opened the ticket.
- Activity and achievements: Discord ID, name, number of messages, time in voice channels, time of the first and last message and unlocked achievements. This is counted for everyone who writes on the server.
- Birthdays: Discord ID, name, day and month, optionally also the year.
- Reminders: Discord ID, text and time of the reminder.
- Polls with buttons: who chose which answer.
- Temporary voice channels: who created the channel, as long as it is open.
- Automations with a wait: the triggering event, for messages including their text, until the next step has run.
Discord: retention and legal basis
This data is kept as long as the server is connected to the channel. If the streamer disconnects the server in the dashboard or deletes the channel, we delete it. The owner and team members with the matching permission can see it.
The legal basis is the streamer’s legitimate interest in these features on their server and in a safe server (Art. 6(1)(f) GDPR).
Events, widgets and flows
So that alerts, flows and the PC app can react, a channel’s events pass through a shared buffer: from Twitch and Kick (including chat messages), from Discord (including message text), from YouTube chat and from connected services. It only holds the latest roughly 20,000 events of all channels; older ones drop out automatically. REBot only reads YouTube chat while the channel’s own YouTube channel is live and a flow listens to YouTube events.
Events used by one of the channel’s widgets (e.g. follows, subscriptions, Bits, raids, donations and orders) are stored for 90 days for event lists, credits and labels: names, amounts and the message sent along. Chat messages are not part of this; the chat box only displays the chat. Whatever a widget shows appears on stream.
Flows, custom overlays and webhooks set up by the streamer receive the data of the chosen events and pass it on to the destinations the streamer specifies. Of a custom overlay’s key we only store a check value and the last four characters.
Flows and C# scripts of the app can remember values, also per viewer (user variables, e.g. a counter or a note). We then store the viewer’s platform, ID and username, the name and value of the variable and when it was last changed. The values stay as long as the channel uses them: the streamer can delete them through flows (one variable, all of a viewer’s, or the variable for everyone), and we delete them with the channel. Each channel can hold at most 20,000 values of 500 characters each.
Images, videos, sounds and fonts the streamer uploads for widgets are stored on our server with file name, size and checksum. Without login they can only be retrieved via a random address that cannot be guessed. When the streamer deletes a file, we remove it immediately.
The legal basis is the streamer’s use of REBot (Art. 6(1)(b) GDPR) and, towards viewers, the legitimate interest in these features (Art. 6(1)(f) GDPR).
Connected services (donations, shops, heart rate, webhooks)
A streamer can connect services whose events REBot passes on: Ko-fi, Fourthwall, Shopify, Throne, Patreon, StreamElements, Streamlabs, TipeeeStream, Pally.gg, DonorDrive, Pulsoid, HypeRate, TreatStream, Crowd Control and custom webhooks. We store the keys and secrets for them encrypted.
From each event we take what alerts and flows need: the name the person gives at the service, amount, items and the message sent along, and for Pulsoid and HypeRate the heart rate. We do not pass on email addresses and postal addresses, for Shopify also not the customers’ names, and for Ko-fi no private messages. To make sure no event arrives twice, we keep its ID for 8 days.
The legal basis is the streamer’s use of REBot (Art. 6(1)(b) GDPR) and, towards supporters, the streamer’s legitimate interest in showing donations and purchases on stream (Art. 6(1)(f) GDPR).
PC app
When a streamer pairs the REBot app on their PC, we store the device name, role, app version and when it was last connected, plus its reported state: which programs it reaches (status, host and port) and which permissions it has. Login details for these programs stay on the PC. Of the device key and the pairing code we only store check values; a code is valid for 10 minutes. When pairing, the IP address is recorded in the change log.
The app receives the channel’s events so that flows can run actions there. We keep the results of its latest jobs for 7 days for the status display in the dashboard. Unpaired devices remain marked as invalid until the channel is deleted. The legal basis is the use of REBot (Art. 6(1)(b) GDPR).
Live and post notifications for other streamers
A channel can have REBot announce when other streamers go live. For this we store the public details of these streamers (name, profile picture, channel ID) and the title, category and times of their streams. A channel can also announce new posts from Bluesky and Instagram accounts or from RSS feeds; for this we store the name, picture and address of the source and remember which posts are already known. The legal basis is the channel’s legitimate interest in pointing to these streams and posts (Art. 6(1)(f) GDPR). If you do not want this, write to us.
Hosting and other providers
- Server and website are run by STRATO AG, Otto-Ostrowski-Straße 7, 10249 Berlin, Germany, in data centers in Germany, on behalf of the operator (Art. 28 GDPR).
- Twitch (Twitch Interactive, Inc., USA), Discord (Discord Inc., USA) and YouTube (Google Ireland Limited, Ireland; Google LLC, USA): For login and the bot features we exchange data with these services. Their own privacy policies apply. Transfers to the USA rely on the EU-US Data Privacy Framework.
- If a streamer connects further services, we also exchange data with them, only for their channel: Kick, Ko-fi, Fourthwall, Shopify, Throne, Patreon, StreamElements, Streamlabs, TipeeeStream, Pally.gg, DonorDrive, Pulsoid, HypeRate, TreatStream and Crowd Control. For song requests we query YouTube and SoundCloud, for post notifications Bluesky, Instagram (Meta) and the RSS feeds entered. Their own privacy policies apply.
- Profile pictures in the dashboard load directly from the servers of Twitch, Discord and YouTube. These services learn your IP address in the process.
- Our server logs requests (time, IP address, requested address without parameters, browser identifier) to detect attacks and errors (legitimate interest, Art. 6(1)(f) GDPR). The logs are overwritten continuously by size and are not analysed unless there is abuse.
Cookies and browser storage
We only set what is needed for operation, which requires no consent (§ 25(2) TDDDG):
- rebot_session: keeps you logged in, at most 30 days.
- rebot_oauth: secures the login process with Twitch or Discord, at most 10 minutes.
- rebot_kick_oauth: secures connecting a Kick account, at most 10 minutes.
- In your browser storage: your chosen language and whether the dashboard is light or dark.
Backups
Once a day we back up the database and the widget files, encrypted, to storage in Germany. Each backup is deleted after 30 days. Deleted data therefore also disappears from the backups after 30 days at the latest.
Deleting your account and your rights
Under "My account" you can delete your account yourself at any time. Your own channel is deleted with all data, the bot leaves your Twitch chat and Discord servers, and the Twitch and Kick authorizations are revoked.
You also have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interest (Art. 21). Write to us at the address above. You can also lodge a complaint with a data protection supervisory authority (Art. 77 GDPR).
Last updated: October 28, 2026