Last updated: October 16, 2026
The short version
Cwtch.es doesn't set cookies of its own. A few tools save small settings in your browser's own local storage — things like a saved OBS link or a Twitch connection — so you don't have to redo them every visit, but that data never leaves your device on its own. The one thing that does involve real cookies is the advertising that keeps the site free, run through Google AdSense, which is a third party with its own cookies and its own rules.
Cookies we don't use
None of the tools on this site set their own cookies. There's no login system, no session tracking, and nothing that follows you from page to page using a cookie. If you check your browser's cookie list after using a tool here, you won't find anything from cwtch.es itself.
What we use instead: your browser's local storage
Some tools save small bits of data using your browser's local storage (technically different from a cookie — it's never automatically sent to any server, and only that tool can read it back). This is purely so a setting or a saved link is still there next time you open the same tool on the same device. It's used for:
- Saved OBS browser-source links — tools like Goal Bar, Subathon, Raffle, Spin Wheel, Countdown Timer, and Streamer Bingo remember the unique link you generated, so it's still there if you come back to update your settings.
- Twitch and Kick connection info — so a streamer using the TTS Reader, Goal Bar, Raffle, or Subathon doesn't have to reconnect their account on every visit.
- Saved tool preferences — a few tools, like the Slideshow Maker, Podcast Clip Maker, and Spin Wheel, remember your last settings or saved presets.
You can clear any of this at any time through your browser's own site data settings — doing so just means re-entering those settings next time, nothing more.
Connecting your Twitch, Kick, or YouTube account
Several tools — including Multi-Chat, Goal Bar, Raffle, Subathon, and the TTS Reader — let you connect a Twitch, Kick, or YouTube account so the tool can read live chat messages or channel activity while you're using it. This is entirely optional and only happens if you click "Connect" and approve it on that platform's own authorization screen.
What we access and why:
- Twitch / Kick — your channel's basic identity (so we know which channel to watch) and chat messages sent while a connected tool is running, via each platform's official EventSub/webhook system.
- YouTube — your channel's basic identity and live chat messages, read-only, via YouTube's official Data API. We never post, comment, upload, or change anything on your behalf, and we never read private messages, analytics, or anything outside of a live stream's public chat.
What's stored on our server: an access token (so we can keep reading chat without asking you to reconnect constantly) and, for chat-feed tools, a rolling window of recent messages (typically the last 500) so the feed has something to show — older messages are automatically dropped, not archived indefinitely. We don't sell, share, or use this data for advertising, and nothing connected-account-related is ever shown to other visitors beyond the live chat feed itself doing exactly what it says on the tin.
YouTube data and Google's rules: Cwtch.es's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In plain words: we only use your YouTube data to show your live chat inside the tool you connected it to. We don't sell it, we don't use it for advertising, and we don't share it with anyone else. YouTube sign-in details are kept as a stored token (including a refresh token, so you aren't asked to reconnect every hour) until you disconnect.
You can disconnect at any time from within the tool itself, which deletes the stored token and any cached state on our end immediately. You can also revoke access directly from the platform's own side at any time: Twitch's connected accounts settings, Kick's account settings, or Google's own third-party access page for YouTube — any of these immediately cut off access whether or not you've disconnected from cwtch.es itself.
Third-party cookies: advertising
Cwtch.es is free to use, and that's paid for with ordinary display advertising through Google AdSense. AdSense does use cookies — for showing ads, limiting how often you see the same one, and detecting fraud — and if you're visiting from the UK, the EU, the EEA, or Switzerland, you'll be shown a consent choice before any of that happens, in line with Google's own EU User Consent Policy. You're free to decline personalized ads; the site works exactly the same either way.
We don't control what AdSense itself does with its cookies beyond configuring that consent choice. For the details, Google publishes its own documentation on how it uses cookies for advertising.
Other third-party requests
A handful of other outside services get loaded as part of how the site runs:
| Service | What it's for |
|---|---|
| Google Fonts | The typefaces used across the site |
| cdnjs, jsDelivr, unpkg | Third-party code libraries a few specific tools rely on (e.g. video/audio processing) |
These are standard, widely-used content delivery services. Loading them means your browser makes a direct request to that provider, the same as loading an image from any other website — we don't have visibility into or control over what they individually log on their end.
Your choices
- Decline or adjust ad personalization through the consent choice shown on your first visit (EEA/UK/Switzerland), or through Google's own Ad Settings at any time.
- Clear local storage for this site through your browser's site settings — this only resets saved links/preferences, nothing else.
- Use a browser extension or setting that blocks third-party ad cookies, if you'd rather not have them at all. Every tool here still works fully either way.
Questions about this?
If anything here is unclear, or you want to know more about how a specific tool works, we're happy to explain.