Privacy Policy

Who is responsible

OBS Blade is developed and published under the name Kounex by:

René Schramowski
Yokohamastr. 3
20457 Hamburg
Germany
[email protected]

René Schramowski is the controller for the little data described here that we process ourselves (the two Kick relays and this website). If you have questions about your data or want to use your rights, write to [email protected]. See also the imprint.

OBS Blade is an unofficial app and is not affiliated with the OBS Project.

What stays on your device

Everything the app needs to work is stored locally on your phone or tablet and is never sent to us:

• your saved OBS connections, including their passwords,
• your settings, dashboard layout, hidden scenes and sources, and themes,
• the statistics of your past streams and recordings,
• the chats and channels you added, and the sign-in tokens and API keys for Twitch, YouTube and Kick,
• your activity feed (follows, subs, raids, cheers, Super Chats, KICKs and similar events on your own channels, kept for 30 days) and which of them you've seen or thanked.

There's no OBS Blade account and no cloud sync. If you have device backups turned on (iCloud or Google), your operating system may include this data in them, under Apple's or Google's terms. You can delete saved data at any time in Settings → Data Management, sign out of a platform in the chat settings, or remove everything by uninstalling the app.

Connecting to OBS

OBS Blade connects directly to the OBS WebSocket server on your computer, normally over your local network, or to an address you enter yourself. This traffic goes between your device and your computer only. It never passes through us.

Purchases (OBS Blade Pro)

Payments are handled entirely by the Apple App Store or Google Play. We never see your payment details, name or store account.

To know whether Pro is unlocked, and to restore it after a reinstall, the app uses RevenueCat (RevenueCat, Inc., USA). RevenueCat receives:

• an anonymous ID generated by the app. It isn't linked to a name, e-mail address or any account, and we don't set a custom user ID,
• your purchase history for OBS Blade (which product, when, and whether it's active), as reported by the store,
• the technical data every such request carries, such as platform, app version, store country and your IP address.

We use this only to provide what you bought (Art. 6(1)(b) GDPR). RevenueCat processes it on our behalf. Data may be processed in the United States, relying on the safeguards RevenueCat offers. See RevenueCat's privacy policy.

Chat and signing in with Twitch, YouTube and Kick

Chat features are optional. When you use them, your device talks to the platform directly: Twitch (Twitch Interactive, Inc.), YouTube (Google LLC) or Kick. What you read, send and moderate goes between you and that platform. It doesn't pass through us, and we don't receive it.

• Signing in uses each platform's own login page. The tokens you get back are stored only on your device and used only to call that platform on your behalf.
• Kick chat is read from Kick's public chat feed, which Kick delivers through the real-time service Pusher (ws-us2.pusher.com). Before connecting, the app asks Kick (web.kick.com) which Pusher server the channel's chat is on.
• YouTube uses the API key and optional OAuth client that you set up in the app yourself. Requests go directly from your device to Google.
• Web chat (the embedded chat views) loads the platform's own web page inside the app, and that platform may set its own cookies there. Owncast chat connects to the server you enter.

The platform's own privacy policy applies to everything you do there: Twitch, Google / YouTube, Kick.

The Kick sign-in relay

Kick's login requires a confidential client secret, which can't safely ship inside an app. So when you sign in with Kick, one step goes through a small relay we run at kick-auth.obs-blade.com (older app versions use kick-auth.kounex.com, the same relay):

• Kick sends the one-time login code to the relay. The relay adds the secret, exchanges the code with Kick for your token, and hands the token to your app.
• The pending sign-in (the one-time code, a random session value and the resulting token) is held in memory only until your app picks it up, and for five minutes at most. It is never written to disk.
• To stop abuse, the relay counts requests per IP address in memory for ten minutes. Its logs contain status codes only, never request contents or tokens.

This is processing, not collecting: we keep nothing afterwards. The legal basis is Art. 6(1)(b) GDPR, because you asked to sign in. The relay is reached through Cloudflare (see This website).

The Kick events relay (activity feed)

Kick delivers follows, KICKs, subs, gifted subs, channel point redemptions and stream status only as webhooks to a server, never to an app. So when you have OBS Blade Pro and are signed in with Kick, a relay we run at kick-events.obs-blade.com receives those events for your own channel and passes them to your app. You can switch it off in the activity feed's options (Kick relay).

• To find out which channel is yours, your app sends your Kick token to the relay once. The relay asks Kick who the token belongs to and doesn't store the token. It keeps your channel's Kick user ID and name, and subscribes to your channel's events at Kick.
• Events are stored for 7 days, so the app can catch up after it was closed. They contain what Kick sends: the Kick name and ID of the viewer who followed, subscribed, gifted or redeemed, the amount, and their message if they wrote one.
• Your app gets a random session key from the relay. The relay stores only a hash of it.
• When you switch the relay off, sign out of Kick or use Delete all data on your last device, your channel is unsubscribed and its data deleted. A channel whose app hasn't checked in for 30 days is removed the same way.
• To stop abuse, the relay counts requests per IP address in memory for ten minutes. Its logs contain the request method, path and status code only, never tokens or event contents.

The legal basis is Art. 6(1)(b) GDPR for your channel's data, because you use the activity feed. For the viewers named in those events, it's the legitimate interest in showing streamers who supported their channel (Art. 6(1)(f) GDPR) - the same events Kick shows the streamer anyway. The relay runs on our server and is reached through Cloudflare (see This website).

Text-to-speech

Reading chat out loud uses your phone's own speech engine. On iPhone and iPad, Apple's voices speak on the device. On Android, the voice engine you picked decides: voices marked "needs internet" in the app send the text to that engine's provider (for example Google) to be spoken. Pick a voice without that mark to keep everything on the device. We never receive the text.

Chat extras from third-party services

Some chat extras are loaded from community services, directly from your device:

• Emotes from 7TV, BetterTTV and FrankerFaceZ. The app asks them for the emote sets of the channels you open.
• Twitch chat history from recent-messages.robotty.de, a community service many chat apps use. It fills in the recent messages when you join a Twitch channel.

These services see your IP address and which channel was requested, like any web request. Both are on by default, and you can turn them off in the chat options (third-party emotes and "Chat history").

Apple and Google

You download OBS Blade through the App Store or Google Play. Depending on your device settings, Apple and Google may collect their own usage and crash statistics about apps, and they process your purchases. That happens under their responsibility and policies: Apple, Google. We only ever see aggregated, anonymous numbers from those consoles.

What we don't do

No analytics, no crash reporting, no advertising, no tracking across apps or websites, no profiling, and no selling or sharing of data. We don't use advertising identifiers.

This website

obs-blade.kounex.com is a static site. It sets no cookies, runs no analytics, and loads no third-party scripts or fonts. Store badges only take you to Apple or Google when you click them.

The site and the Kick relays are delivered through Cloudflare (Cloudflare, Inc., USA), which protects them and routes traffic to our server. To do that, Cloudflare processes your IP address and standard request data (such as the page requested, time and browser type), and may keep short-lived security logs. Our own web server keeps no access logs. The legal basis is our legitimate interest in delivering the site securely (Art. 6(1)(f) GDPR). See Cloudflare's privacy policy.

Your rights

Under the GDPR you have the right to access, rectify and erase your data, to restrict or object to its processing, and to data portability (Art. 15-21 GDPR). You can also lodge a complaint with a data protection supervisory authority.

Because we hold almost nothing ourselves, most requests will concern RevenueCat's purchase record (identified by the anonymous ID) or one of the platforms above. Write to [email protected] and we'll help you with it.

Children

OBS Blade isn't directed at children, and we don't knowingly process children's data. The chat platforms set their own minimum ages.

Changes

If a future version sends anything new off your device, this policy will say so before that version ships, and the date above will change. The source code is public on GitHub if you'd like to check for yourself.