Privacy policy
You sign in to Wojak Stream with a Twitch account. The page sets one session cookie and has no third-party analytics or ads. This page says which data, why, and for how long.
As of .
Controller
The data controller is Jakub Wojdziak. I run Wojak Stream as a private person, not as a business. Contact: [email protected]. There is no data protection officer.
What data and why
Captions on the overlay server
After you click Start, the page sends the server what the OBS overlay should show:
- finished caption lines, the translation together with the original,
- the current draft of a sentence Soniox hasn't finalized yet,
- the overlay look settings.
The server keeps them in memory only, never on disk, under a random room ID tied to your account. Captions never go into the database. Captions hold personal data only if you say it, for example your name or someone else's.
Purpose and legal basis. Showing captions on the overlay you asked for, that is performing the agreement under the terms of service (Art. 6(1)(b) GDPR). Giving this data is voluntary, but without it the overlay shows no captions.
How long. The server keeps at most the last 50 lines. A few seconds after Stop it deletes the lines and the draft, and right away after New address. A room nobody has written to for two days and no overlay is reading is deleted entirely, and a server restart deletes all rooms.
Twitch account and daily limit
You sign in with Twitch. We ask Twitch for no extra permissions, so we get only your ID, display name and the date your account was created. We don't get your email address. The server's database keeps:
- your Twitch ID and display name, when your Twitch account was created, when you first signed in and when you accepted the terms,
- the random ID of your room (from the overlay address) and your daily limit, if I set one other than the default,
- for every Soniox connection: the ID Soniox gave it, the day, the hour it began (the full hour in Polish time, no minutes), duration, cost, spoken language and caption language.
Purpose and legal basis. Signing in, an overlay address tied to your account and counting the daily limit are how the service works (Art. 6(1)(b) GDPR). The 30-day account age rule, the monthly cost cap and usage statistics protect the service from abuse and costs, and the starting hour tells me when people stream, so I don't deploy changes then and cut anyone's captions. I keep the date you accepted the terms so I can show when and on what terms we made the agreement. This is my legitimate interest (Art. 6(1)(f) GDPR).
How long. I keep the account until you delete it with Delete my data or by email. Usage records are deleted after 13 months. Once you delete your account, its usage records stay in the statistics without your ID: older ones lose it right away, today's at midnight, so deleting the account does not reset the limit. One exception: if I blocked the account for breaking the terms (daily limit 0), Delete my data doesn't work, because signing in again would lift the block. I then keep the account and its usage records for as long as the block lasts, under my legitimate interest in protecting the service from abuse (Art. 6(1)(f) GDPR). After that you can delete them as usual. Every night the server makes a copy of the database and keeps the last 7. The copies also go to Cloudflare R2 storage, where the nightly ones stay for 8 days. Every so often I copy them to my computer and delete the copies there that are older than 8 days. Data deleted from the database is therefore gone from the copies on the server and in R2 within 8 days, and from the copies on my computer at the first copy after that.
Counters without your ID
The server counts how many accounts met a given event on a given day and stores three things: the day, the event's name and the number of accounts. It doesn't store which accounts. The events come from a fixed list:
- an error in the panel: the microphone (access denied, unplugged, another error), audio processing, a Soniox error or dropped connection, a browser recognition error, no connection to the overlay server,
- a refused Soniox key: the daily limit, the monthly budget, a Twitch account that is too new, too many connections at once, an error on Soniox's side,
- streaming: the account got a Soniox key that day, and whether an overlay was reading its room at the time,
- options switched on in the panel when a connection opens: hidden draft, auto-stop, CC captions in OBS, the Text source in OBS, a second spoken language, a non-empty list of fixes. Only the option's name, never the fixes themselves or the source name.
Your browser reports the errors and options; the server counts the rest itself. An account counts once a day per event. To keep to that, the server remembers until the next day, Polish time, which accounts it has already counted. It holds that in memory only, never on disk.
Purpose and legal basis. I want to know whether the service works, how many people run out of free minutes and which options anyone uses at all. This is my legitimate interest (Art. 6(1)(f) GDPR). A counter doesn't hold your ID. On a day when few accounts streamed, though, I could guess which account it is about by setting it beside the usage records, which is why I describe the counters here.
How long. Counters are deleted after 13 months. They stay when you delete your account, because I can't tell which are yours. The memory of who was counted today is gone the next day and on a server restart.
Bought minutes
When you open the payment window, the server creates a Paddle transaction and stores its ID with your Twitch ID. Once you've paid, Paddle sends the server a confirmation. The database keeps your balance of bought minutes, their expiry date and each purchase: the Paddle transaction ID, date, hours and price. Each refund and chargeback is kept the same way: its ID, date, the hours taken back and the amount returned. For every Soniox connection it also keeps how many minutes came off the balance. I don't store your name, email address or payment details. Paddle collects those.
Purpose and legal basis. Adding bought minutes to your account, counting them and working out a refund, which is performing the agreement (Art. 6(1)(b) GDPR).
How long. The balance stays with the account. The record of an opened payment (the transaction ID with your Twitch ID) is deleted after 30 days, paid or not, because by then a purchase has its own record. Purchase records are deleted after 13 months, but not before the bought minutes expire, because a refund can't be worked out without them. When you delete your account, the balance is gone, records of opened payments are deleted and purchase records lose your Twitch ID right away.
Logs and Cloudflare
My server keeps no request logs and no IP addresses. It logs errors only, and for a payment error or an unreadable entry in Soniox's billing logs that log holds your Twitch ID or the transaction ID. All traffic to the page passes through Cloudflare, though, which sees the IP address, date and time, page address and browser name of every request. The overlay address holds the room ID.
Purpose and legal basis. Delivering the page and protecting it from attacks. This is my legitimate interest (Art. 6(1)(f) GDPR).
How long. Cloudflare keeps this data under its data processing agreement, at most until it stops providing the service to me. My server's error log holds at most 30 MB and older entries drop out of it by themselves.
Soniox key
Start asks the server for a one-time Soniox key for one connection, limited to what is left of your daily limit. The server doesn't store the key. It attaches your Twitch ID and languages to it, and Soniox lists them in the billing logs the server counts usage from. Soniox confirmed to me by email that it keeps these logs for 30 days. I can't delete them.
When you write to [email protected], I get your email address and whatever the message contains.
Purpose and legal basis. Replying to you, which is my legitimate interest (Art. 6(1)(f) GDPR). When you write about your GDPR rights, the basis is a legal obligation (Art. 6(1)(c) GDPR).
How long. Until the matter is settled. Messages about GDPR rights I keep for as long as claims may arise from them.
What skips my server
- Speech recognition and translation. After Start, the browser sends microphone audio straight to Soniox's servers in the European Union (Soniox Inc., 1045 Helm Lane, Foster City, CA 94404, USA), bypassing my server. After 10 seconds of silence the page disconnects from Soniox and sends nothing until you speak again. Along with the audio the browser gives Soniox hints so it hears names better: the spoken languages, your Twitch name, the Twitch category you are streaming in (the game's name, say) and the words in your list of fixes (those after "=>", and whole pairs when translating). Soniox recognizes the speech, translates it and sends the text back. An artificial intelligence system does this, automatically and with no human check. Under the Soniox Privacy Policy, it does not store real-time audio or text and does not train models on them. Soniox acts here as my processor, on my behalf, under an Art. 28 GDPR data processing agreement, in which it commits not to train models on this data.
- Recognition in the browser. When you tick "Free, no translation", your browser recognizes the speech instead of Soniox. If it has your language's pack, it does so on your computer and the audio never leaves it. If not, it sends the audio to its maker's speech recognition service (Chrome to Google, for example), bypassing my server and Soniox. After Start the panel says which it is. The browser maker doesn't act on my behalf then: it processes the audio under its own terms, as a separate controller. The recognized text reaches the room on my server just as it does with Soniox.
- OBS. CC captions and the Text source go to 127.0.0.1, which is OBS on your own computer. The page never saves the OBS password.
- The Wojak Stream (ALPHA) app. Runs on your computer and sends nothing. The download is hosted on Google Drive, which has its own rules and cookies.
- Fonts. Served from this server, so the page doesn't connect to Google Fonts.
Who gets the data
- mikr.us (UW-TEAM.org Jakub Mrugalski, Polish tax ID 6821639338) rents me the server that runs the page and the overlay server. The server sits in the Hetzner data center in Helsinki, Finland.
- Cloudflare (Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA) carries all traffic between your browser and the server and stores the database copies in R2. It processes data on my behalf under the data processing agreement that is part of Cloudflare's terms.
- Soniox (Soniox Inc., USA) recognizes and translates speech on my behalf and gets your Twitch ID for its billing logs, as described above. I use Soniox's EU region, so the data Soniox processes on my behalf stays in the European Union. Soniox may also process billing, security and fraud-prevention data on its own account, as a separate controller. It runs on AWS, Google Cloud and Oracle Cloud, and uses Cloudflare.
- Paddle (Paddle.com Market Ltd, Judd House, 18-29 Mora Street, London EC1V 8BT, United Kingdom) sells bought minutes as the Merchant of Record. I pass it only your Twitch ID, to tie the purchase to your account. Your browser loads the payment window and its script straight from Paddle's servers, and only once you click to buy. Paddle collects your name, email, country and payment details itself, as a separate controller, under its privacy policy.
- Twitch (Twitch Interactive, Inc., 350 Bush Street, 2nd Floor, San Francisco, CA 94104, USA) handles sign-in. Your Twitch account is under Twitch's own terms, as a separate controller. When you sign in, Twitch learns that you are signing in to Wojak Stream. While the panel is running, the server asks Twitch at Start and then every minute whether your channel is live and in which category. That lets auto-stop end the captions after the stream, and gives Soniox the category as a hint. When the channel isn't live, Soniox gets no category. The server doesn't store the answer.
- OVHcloud (OVH SAS, 2 rue Kellermann, 59100 Roubaix, France) hosts the [email protected] mailbox and redirects the old wojak.works/stream/ address. It processes data on my behalf under the Art. 28 GDPR data processing agreement that is part of OVHcloud's terms.
- Anyone with the overlay address can see the room's captions. Your viewers see the captions on stream. You decide who gets the address and what you say.
- Public authorities get data only when the law requires it.
I don't sell data or pass it to advertisers.
Outside the EEA
The server is in Finland, email at OVHcloud in France, and Soniox recognizes speech in the European Union, all in the EEA. Data may reach the US in four places:
- Cloudflare, for traffic to the page and the database copies. Cloudflare is certified under the EU-US Data Privacy Framework, and its data processing agreement falls back to the standard contractual clauses should that lapse.
- Soniox, because it is a US company. It processes microphone audio, recognized text and the Twitch ID in its billing logs in its EU region. The data processing agreement allows only limited processing outside it, as needed for security, support, running the service or legal compliance. Such a transfer is covered by the European Commission's Standard Contractual Clauses (Decision 2021/914, Module 2), which are part of that agreement.
- Twitch, for sign-in. Twitch handles account data under its own privacy policy.
- Your browser's maker, if you tick "Free, no translation" and the browser has no pack for your language. Microphone audio then goes to its speech recognition service, under its own terms.
Paddle operates in the United Kingdom, which the European Commission has found to ensure an adequate level of data protection (Art. 45 GDPR).
Your rights
You have the right to:
- access your data and get a copy (Art. 15 GDPR),
- rectification (Art. 16),
- erasure (Art. 17),
- restriction of processing (Art. 18),
- portability of your account data, usage and the room captions I process to provide the service (Art. 20),
- object to processing of statistics, logs and email, which rests on legitimate interest (Art. 21),
- lodge a complaint with a supervisory authority, in Poland the President of the Personal Data Protection Office (UODO), ul. Stawki 2, 00-193 Warszawa, uodo.gov.pl, or the authority where you live or work.
I find your data by your Twitch name. For logs, give your IP address and the rough time of your visit. If I can't identify you, I'll tell you (Art. 11 GDPR). I reply within a month.
Some of it you can do yourself. Delete my data on the control page deletes your account, Stop deletes captions from the server after a few seconds, New address right away.
I do no profiling. The server itself refuses a Soniox key when the Twitch account is under 30 days old, when you've used up the daily limit or when the monthly budget runs out. These aren't decisions with legal or similarly significant effects under Art. 22 GDPR, but if you disagree with one, write to me and I'll review it myself.
Cookies
The page sets two first-party cookies, both needed for signing in:
- s, the session: your Twitch ID, an expiry date and the server's signature. Valid for 30 days from your last visit; Sign out or Delete my data removes it at once.
- st, during sign-in: a random code that checks the sign-in was started by you. Valid for 10 minutes and removed as soon as you come back from Twitch.
The page sets no third-party cookies; on Twitch's own sign-in page, Twitch's rules apply. There is no cookie banner, because cookies needed for a service you asked for require no consent.
Settings stay in your browser's storage (localStorage):
- languages, microphone and its channel, the "Free, no translation" option,
- the list of name fixes,
- overlay look,
- auto-stop, CC captions in OBS, OBS port and Text source name,
- light or dark theme.
Only two things from this list reach the server: the overlay look, because the overlay in OBS reads it, and the languages on Start, for the Soniox key and the statistics. Without this storage and the cookies the page couldn't keep your settings, so it needs no consent (Art. 5(3) of Directive 2002/58/EC, Art. 399 of the Polish Electronic Communications Law).
Separately, for the counters in section 02, the panel tells the server the bare fact of which options are on, and the name of an error when something fails. Words from the list of fixes go to Soniox as hints, bypassing my server. During sign-in the page also keeps, in the tab's storage (sessionStorage), the time it sent you to Twitch, so a failed sign-in doesn't loop.
To delete it in Chrome or Edge, click the icon left of the address bar, choose Site settings, then Delete data.
Contact and changes
For anything about your data, write to [email protected].
If I change how data is processed, I'll update this page and the date at the top. The rules for using the service are in the terms of service.
What changed
- 15 November 2026. When translating, Soniox now gets whole pairs from your list of fixes: the words before "=>" too, not only those after it.
- 14 November 2026. I record when you accepted the terms with your account. Accounts created earlier have their first sign-in date there, because back then signing in alone accepted the terms.
- 13 November 2026. Added the "Free, no translation" option: the browser then recognizes the speech, on your computer or in its maker's service, instead of Soniox.
- 12 November 2026. The hints for Soniox now include the Twitch category you are streaming in. The server asks Twitch for it along with whether the channel is live, at Start too.
- 11 November 2026. Added the counters without your ID and the hour a Soniox connection began. I also wrote down what already worked but wasn't described here: the hints for Soniox (your name and fixes), asking Twitch whether the channel is live, Paddle's script on purchase, the server's error log, refund records and a few browser settings.