A German version of this policy is available — use the DE switch at the top. Both versions say the same.

1 · Controller

The controller responsible for processing personal data within the meaning of the General Data Protection Regulation (GDPR) is:

Tony Hilbert
Limbacher Straße, 09243 Niederfrohna, Germany
Email: info@kasaicore.com
Service: Death Counter — deathcounter.kasaicore.com

2 · In short

3 · Hosting, delivery and server logs

Server: The application and its database run on a server of netcup GmbH, Daimlerstraße 25, 76185 Karlsruhe, Germany. netcup processes the data on our behalf (Art. 28 GDPR); the database can only be reached from inside the server.

Cloudflare: All requests go through Cloudflare, Inc. (101 Townsend St, San Francisco, CA 94107, USA), which delivers and caches the site and protects it against attacks (e.g. DDoS). Our CDN (cdn.deathcounter.kasaicore.com: fonts, scripts, images) and the storage for sound files (Cloudflare R2, sounds.deathcounter.kasaicore.com) also run on Cloudflare. Cloudflare processes your IP address and technical details of the request; processing in the USA is possible. Cloudflare is certified under the EU-US Data Privacy Framework (adequacy decision, Art. 45 GDPR); standard contractual clauses apply in addition. The legal basis is our legitimate interest in secure and fast delivery (Art. 6(1)(f) GDPR). cloudflare.com/privacypolicy

Server logs: Each request is logged with IP address, time, requested address, status code and browser identifier (user agent). The application also logs operational events, e.g. errors, rejected uploads, or chat commands the chat bot recognised (command, channel). The purpose is security, abuse prevention and troubleshooting (Art. 6(1)(f) GDPR). Logs are deleted automatically after 14 days.

4 · Login with Twitch and the chat bot

You log in through Twitch (OAuth 2.0) of Twitch Interactive, Inc. (USA). We never see your password. Twitch sends us your Twitch ID, login name and the address of your profile picture — we store these. Because of the requested permission, Twitch also sends your email address; we neither store nor use it. Whatever happens on Twitch itself is covered by Twitch's privacy notice.

Chat bot: For the counter to work from chat, you invite our bot into your channel and grant it permissions on Twitch. We store the access tokens Twitch issues for this as long as the bot is in your channel. The bot reads the chat messages in your channel to recognise commands such as !death. When you authorize it, the bot uses your permission to make itself a moderator in your channel. Only then can it reply in every chat mode (e.g. followers-only or slow mode) without being held back by Twitch's chat limits. It takes no other moderation actions with it; you can remove the role at any time with /unmod. We do not store chat messages; recognised commands only appear in the server logs (§ 3). You can remove the bot at any time with !leave or under "Connections" in your Twitch settings.

The legal basis is providing the service you want to use (Art. 6(1)(b) GDPR).

5 · What the service stores

DataPurposeStored inLegal basis (GDPR)Retention
Twitch ID, name, profile picture address Recognise your account, show your dashboard Database (netcup, Germany) Art. 6(1)(b) As long as you use the service
Settings (overlay, sounds, announcer voice, chat commands, prefix) and your secret overlay links Show your overlays the way you set them up Database (netcup, Germany) Art. 6(1)(b) As long as you use the service
Death counts per game and death statistics: every change with time, game, old and new count, and the Twitch name that triggered it (you or your mods via chat command, Stream Deck) Counter, timeline and statistics Database (netcup, Germany) Art. 6(1)(b) As long as you use the service; deleted on request
Uploaded sounds + details (name, size, length) Play your own death sounds Cloudflare R2 (see § 3) Art. 6(1)(b) Until you delete them; rejected files are deleted immediately
Login session incl. security details (see § 6) Keep you logged in, detect misuse Database (netcup, Germany) Art. 6(1)(b) and (f) Until logout or the login expires
Feedback messages (see § 10) Read and answer your message Database; notification via Discord Art. 6(1)(f) 12 months at most
Messages from the developer: who read which message when (see § 10) Show what is new under the bell Database (netcup, Germany) Art. 6(1)(b) Message: 7–365 days (usually 30); read marks 13 months at most

No profiling or automated decision-making takes place.

6 · Cookies and browser storage

We only set cookies that are strictly necessary for the service or that you trigger yourself — no consent is required for these (§ 25(2) no. 2 TDDDG):

What the login session holds: your Twitch ID, name and profile picture, the time of login and — for security — the IP address, the approximate country (from Cloudflare), a description of your browser and device, and the last five IP addresses of that session. This lets us spot logins that are not yours and end single logins (Art. 6(1)(f) GDPR). These details disappear with the session.

Local storage (localStorage/sessionStorage): the site remembers a few interface preferences in your browser, e.g. the section you had open, the preview background, frames you have already seen, and the tour's volume and language. This never leaves your browser, and you can delete it at any time in your browser settings.

No tracking, advertising or third-party cookies are set.

7 · Sound uploads

Uploaded audio files are checked and normalised on our server and stored in Cloudflare R2 (see § 3). Uploads may be reviewed before they go live (see Terms of Service § 4); rejected files are deleted immediately and permanently. We are notified of new uploads in a private Discord channel (see § 11).

8 · Announcer voice (text-to-speech)

For the announcements we send a short text to a speech service that turns it into audio: on a game switch the game name and your death count, for the milestone announcements (e.g. at 100 deaths) a fixed line with the death count. The texts contain no name and nothing else about you. Speech services: Fish Audio (fish.audio) or Microsoft Azure AI Speech (Microsoft Corporation, USA). Our server makes the request; your browser is not involved. We cache the finished audio so the same text does not have to be generated again.

9 · Content from Twitch

10 · Deck, Counter Team and the Twitch extension

Deck page (/deck): uses your normal login with Twitch. It stores nothing extra on our side; in your browser it remembers whether the screen should stay on and whether you closed the "add to home screen" hint.

Counter Team: a streamer can let other Twitch users count deaths for their channel. For that we store, per channel, the team member's Twitch user ID, login name and display name, when they were added and when they last used the deck — so the streamer can see and manage the list. Names are refreshed from Twitch. A team member is removed when the streamer removes them or the $1 $2

$2

$2 Blocked people: a streamer can also lock single people out of the extension and the deck, mods included. For that we store, $2 per channel, the Twitch user ID, login name and display name of that person and when they were blocked, until the streamer unblocks them or $2 the streamer's data is deleted (Art. 6(1)(f) GDPR: the streamer's interest in keeping control of their counter). $2

Twitch extension: when you open the extension on a stream, Twitch gives it a signed token with the channel ID, your role (streamer, moderator or viewer), an anonymous ID and — only if you agree to share your identity — your Twitch user ID. We use it only to check whether you may count and, for a counted tap, to name you in the bot's chat reply. We keep the channel ID and the time of the last use briefly in memory, to send live updates to the extension through Twitch. For viewers nothing else is processed or stored. The extension loads no third-party content apart from Twitch's own extension script and game covers from Twitch; inside the extension frame Twitch's privacy notice applies as well. Short version for the extension: extension privacy.

Who counted: taps on the deck, in the extension, on a Stream Deck link and chat commands are saved like any counter change, with the name of whoever counted (as with chat commands). So that several people do not count the same death twice, the counter also keeps a short anonymous code of the last person who counted; it is overwritten by the next death.

11 · Feedback and messages from the developer

If you write to us through the feedback form (only possible while logged in), we store the text, the type you chose, the optional contact detail, your Twitch ID and name, and the time. We use this only to read and answer your message and to improve the service. To stop abuse (spam, insults), messages are checked automatically and may be rejected; rejected messages are kept (marked as rejected) for the same period. Anyone abusing the form can be blocked — for that we store the Twitch ID, name and time of the block until it is lifted. We are notified of each message in a private Discord channel (text, contact detail, Twitch name and profile picture). Please do not put passwords or sensitive data in the form. Messages are deleted when no longer needed, after 12 months at the latest, or earlier on request (Art. 6(1)(f) GDPR).

Messages from the developer appear under the bell in the page header (important ones also as a popup). So the bell can show what is new, we store which message you read and when. Messages expire on their own after the set time; nothing from them is shared with third parties.

12 · Operations log in Discord

So that we notice problems and abuse quickly, the service sends certain events to a private Discord channel of the operator at Discord Inc. (USA): e.g. login and logout, inviting or removing the bot, connected overlays, sound uploads, feedback, security-relevant actions (such as a new overlay link) and server errors. These messages contain your Twitch name, Twitch ID and profile picture, but no IP addresses and no secret links. The legal basis is our legitimate interest in running the service securely (Art. 6(1)(f) GDPR). We delete these messages when they are no longer needed. Discord is certified under the EU-US Data Privacy Framework.

12a · Internal activity log

To investigate problems, abuse and support requests, the service keeps an internal log on our own server of what happens on the website and in the chat bot: login and logout, changes to settings (old and new value), counter changes, chat commands (the command, Twitch name and ID, channel and result), deck and extension actions, uploads, refused requests and errors. An entry holds the time, the Twitch name and ID of who did something and for which channel, and a short description. To group entries that belong together, it can also hold a random request code and a short code derived from the login session (the session cannot be recovered from it).

Passwords, access tokens, keys and secret overlay links are filtered out and never stored. IP addresses are only stored with security events (such as a login, refused access or too many requests). Only the operator can see the log, entries cannot be changed, and every entry is deleted automatically after 90 days. Nothing from it is shared with third parties. The legal basis is our legitimate interest in running the service securely and helping you with problems (Art. 6(1)(f) GDPR).

13 · Your rights

Under the GDPR you have the following rights:

Just email info@kasaicore.com. We reply within one month (Art. 12 GDPR).

14 · Obligation to provide data

You cannot use the service without logging in through Twitch — the Twitch data in § 4 is required for that. Uploading your own sounds and the feedback form are voluntary.

15 · Data security

All connections are encrypted with HTTPS (TLS). The database cannot be reached from outside, uploads are kept in access-controlled storage, and the programs that process uploaded files run with restricted rights.

16 · Changes

When the service changes, we update this policy. The date at the top shows the current version.

17 · Contact

Privacy questions, access or deletion requests: info@kasaicore.com