Privacy Policy

1. Who we are

This policy covers the Discord bots and web apps run by Resorted ("we", "us") and their websites:

• RizzyBot - bot.resorted.dev
• PropellBot - bot.propelldir.no
• The ChædderHeim Valheim bot - heim.propelldir.no
• Twitch Watcher - app.resorted.dev/twitch-watcher
• Propell IRL (signs in with PropellBot) - app.propelldir.no
• SRT Relay - app.resorted.dev/srt, with its stream server at srt.resorted.dev

Resorted is the data controller for the data the bots store. Discord, Twitch and Valve (Steam) handle your data under their own privacy policies.

2. What we collect

All bots: when a bot is in your server

Discord sends the bot information about the servers it's in, so that it can work. This includes the server's name, icon, roles and channels, and the member list (each member's user ID, username, display name, avatar and roles). The member list is kept in memory only, to show it on the dashboard and to give out roles. It isn't written to disk and is gone when the bot restarts.

When you click a bot's button or react to one of its role panels, the bot uses your user ID to give or take the role. These clicks aren't stored.

All bots: when you sign in on a website

Signing in with Discord gives us your Discord user ID, username, display name and avatar. On the dashboards it also gives us the list of servers you're in, so we can show the ones you can manage. We ask Discord only for the identify scope (plus guilds on the dashboards) - never your email address, messages or connections. We keep this in a sign-in session tied to a cookie in your browser.

All bots: server settings

For each server, we store the settings people make on the dashboard: which roles or users can use each module (by ID), the bot's profile in that server, the messages and embeds sent through the dashboard (their content, channel and message IDs, so they can be edited later), role panels, and feature settings. Custom emojis used in a message may be copied to the bot's own emoji list so it can use them.

PropellBot: Twitch VIP roles

• When the Twitch channel's owner clicks Connect Twitch channel, we store the access tokens Twitch gives us. They only allow reading the channel's VIP list (channel:read:vips).
• We read the channel's VIP list (each VIP's Twitch user ID, login and display name) every 10 minutes.
• When someone matches a VIP to a Discord member, we store that link (Twitch user ID ↔ Discord user ID), or a "No Discord" mark, along with who made the match. Matching is done by people; the bot never reads your Discord account connections.

Valheim bot: whitelist requests

• When you ask to be whitelisted, you sign in with Discord (your ID, username, display name and avatar) and with Steam. Steam's sign-in gives us only your SteamID64. We then look up your public Steam profile name and avatar.
• We store the request: your Discord and Steam details, the note you write, when you sent it, and whether it was approved or denied, by which moderator and when.
• Your request is posted in the server's moderator channel, and the answer is sent to you by Discord DM or in a channel, depending on the server's settings.
• If you're approved, your SteamID64 is added to the Valheim server's whitelist file.
• If the server turns on event posts, the bot posts things like players joining, leaving, dying or being turned away, using the in-game character name and Steam name, in a Discord channel. These posts aren't stored by the bot beyond Discord itself.

Twitch Watcher: announcements

• Signing in gives us your Discord user ID, username, display name, avatar and the list of servers you're in (with whether you can manage each), as above. We also keep the tokens Discord gives us for your sign-in, only to update that server list, and - if you add Twitch Watcher to your Discord apps so it can send you direct messages - the token from that, only so we can revoke it when you remove the app.
• For each place you set up announcements in, we store: the Discord channel (server and channel ID) for the bot, or the webhook's URL and name, or - for direct messages - your user ID; the texts you write for the posts; and the IDs (and names, for showing them on the page) of the roles and people you choose to ping.
• The Twitch Watcher bot doesn't keep member lists. When you search for someone to ping, the server's members are looked up at that moment and not stored.
• The public badge and emote pages need no sign-in and store nothing about visitors.

Propell IRL: live location overlays and chat commands

• Signing in to the dashboard with Discord (through PropellBot) gives us your Discord user ID, username, display name and avatar. The Discord token is thrown away right after sign-in; your roles in the server are looked up through PropellBot each time you use the dashboard and not stored.
• The streamer's own location comes from RealtimeIRL. We keep the current trip (distance, steps and the route, without points inside privacy zones) and the settings made on the dashboard. Place names come from OpenStreetMap and weather from Open-Meteo, which receive the coordinates for those lookups.
• The overlays, chat commands and the live map at app.propelldir.no/gps are public and store nothing about the people who view or use them.
• The live map can also show other streamers from RealtimeIRL's own public map (name, channel, category and last position, as RealtimeIRL publishes them while they share their location). This is fetched from RealtimeIRL while someone views the map, kept in memory only and never stored.

SRT Relay: camera feeds

• Signing in with Twitch gives us your Twitch user ID, login, display name and profile picture. We ask Twitch for no permissions at all, and the token Twitch gives us is revoked right after reading who you are. Your account also has an access status (waiting, approved or blocked), set by the owner.
• For each feed and source you make, we store their names and settings (camera settings, delay, which source the feed shows, encryption) and the keys and passphrase in their addresses.
• For each source we keep a summary of its last five streams: when it started and ended, how it connected (SRT or RTMP), the delay, round trip, packet loss, bitrate, resolution and codecs.
• The video and sound you send pass through the server to OBS as they arrive. They are not recorded or stored.
• The stream server writes a technical log line for each camera and OBS connection, with the IP address it came from, to find problems and misuse.
• The stats address for NOALBS shows numbers about your live feeds (bitrate, round trip, loss) to whoever has the address - nothing else.
• If you let someone edit a feed, we store who edits which feed and when they joined, and the invite links nobody has used yet. Editors see the feed's settings and addresses, and the feed's owner sees its editors' Twitch names and profile pictures. The page also shows who made the latest change to a feed.

Technical logs

The bots write short technical logs (start-up, errors, failed API calls). These may sometimes include a user, server or Steam ID. We don't keep access logs of IP addresses on these websites; SRT Relay's stream server logs the IP addresses of stream connections, as above.

3. What we don't collect

• The bots don't use Discord's Message Content intent, and don't read, log or store the messages in your server.
• We don't collect email addresses, passwords, payment details, or voice data.
• We don't use analytics, advertising, tracking pixels or third-party cookies.
• We don't sell, rent or trade data, and don't use it to train AI models.

4. Why we use it, and the legal basis

5. How long we keep it

• Member lists: in memory only, until the bot restarts or you leave the server.
• Sign-in sessions: 30 days, or until you sign out.
• Server settings, sent messages and role panels: until they're deleted on the dashboard, or until the server asks us to delete them.
• Twitch tokens: until the channel is disconnected on the dashboard; the tokens are revoked with Twitch at that point.
• Twitch VIP matches: until they're removed on the dashboard or the helpers page.
• Whitelist requests: pending requests until they're decided; decided requests stay in the history until they're among the oldest past the 200 most recent, then they're deleted. Your SteamID64 stays on the server's whitelist until it's revoked.
• Twitch Watcher announcements: until you remove them on the page. Removing Twitch Watcher from your Discord apps on the page stops your direct messages and revokes its Discord tokens for you.
• Propell IRL: sign-ins last up to 30 days or until you sign out; a trip until the next one starts.
• SRT Relay: sign-ins last up to 90 days or until you sign out; feeds and sources until you delete them; who edits a feed until the owner removes them or they stop; unused invite links 48 hours; stream summaries - the last five per source; your account until you ask us to delete it or the owner removes it. Stream connection logs are kept until the stream server's logs are cleared, at the latest when the service is updated.
• Technical logs: only as long as needed to fix problems.

Messages the bot posted in Discord stay in Discord until someone deletes them there.

6. Who it's shared with

• The server's admins and moderators see the server's data on the dashboard, according to the server's access settings - for example, moderators see whitelist requests, and helpers see Twitch VIP matches.
• Discord, Twitch and Valve (Steam) receive the requests the bots make to their APIs, as needed for the features above.
• We may disclose data if the law requires it.

We don't share data with anyone else.

7. Cookies

The websites set only the cookies needed to sign you in: a session cookie (up to 30 days, 90 for SRT Relay) and a short-lived cookie that protects the sign-in from being tampered with. Both are signed, HTTP-only and not used for tracking.

8. Storage and security

The data is stored on a server we run ourselves, readable only by the bots and their operator. Connections to the websites use HTTPS. Bot tokens and keys are kept out of the code and out of any public place. No system is perfectly secure, but if something goes wrong we will act on it and tell those affected where the law requires it.

9. Your rights

Under the GDPR (and similar laws), you can ask us to:

• tell you what data we have about you and give you a copy;
• correct it;
• delete it;
• stop or limit using it, or object to how we use it.

To ask, use the contact below. We'll answer within a month. Some things you can do yourself: sign out, remove the app under User Settings → Authorized Apps in Discord, or leave the server. If you think we've handled your data wrongly, you can complain to your data protection authority - in Norway, Datatilsynet.

10. Children

The Services follow Discord's and Twitch's age rules: you must be old enough to use them in your country (at least 13). We don't knowingly collect data from anyone younger. If you think a child has used the Services, contact us and we'll delete their data.

11. Changes

If we change this policy, we'll update it here and change the date at the top. If a change matters a lot - for example, a bot starts collecting a new kind of data - we'll say so in the bot's Discord server too.

12. Contact

For privacy questions or to delete your data, ask a moderator in the Discord server where you use the bot to pass it on to Resorted, who runs the bots. For SRT Relay, contact the streamer who gave you access, or Resorted on Twitch.