privacy policy.
how we handle your data — what we collect, why, where it lives, and how you can take it back.
last updated: 23 May 2026
tl;dr
you sign in with twitch so klypra can watch your chat and turn highlights into clips. we store the minimum needed to do that — your twitch identity, the channels you monitor, and the clips we generate. clips reach you either through your own telegram bot or directly in the klypra dashboard. we never sell your data to anyone. you can delete your account at any time and we will wipe everything.
1. why you sign in with twitch
klypra needs two things from twitch to work:
- ·chat:read — so our worker can read your channel's chat in real-time and score every message for hype. this is how we detect viral moments.
- ·user:read:email — we receive your account email from twitch and use it as the unique identifier for your account in our database. we do not send marketing or notification emails.
we do not request any other twitch scopes. we cannot post to your channel, modify your settings, create twitch clips on your behalf, or read your private messages.
you can revoke klypra's access at any time from your twitch connections page. revoking access will stop monitoring immediately.
2. what we collect
here is the complete list of data klypra stores about you:
from twitch (at sign-in)
- ·twitch user id — your numeric twitch identifier, used as the primary key for your account.
- ·twitch username (login) — e.g.
xqc. - ·display name — your twitch profile name.
- ·email address — used as the account identifier in our database.
what you create in klypra
- ·monitored channels — the list of twitch channels you've added (their usernames + per-channel settings).
- ·clip settings — your preferences (threshold, format, subtitle style, etc.).
- ·generated clips — the mp4 files we produce, their metadata (timestamp, score, transcript), and how long until they expire.
- ·worker stats — chat rates, processing heartbeats, error logs (for operational monitoring).
if you set up telegram delivery
- ·your telegram bot token — stored in our database, access-restricted so only your account can read it. it is never returned to your browser after setup; it is only used server-side when delivering a clip to telegram's api.
- ·your telegram chat id — where clips get sent.
- ·notification preferences — which events trigger a notification.
if you join the waitlist
- ·email address — to notify you when pro launches.
3. what we don't collect
- ·your twitch password or access token (oauth handles this — we never see them).
- ·private twitch messages or DMs.
- ·card or banking information.
- ·browser fingerprints, third-party analytics, or behavioural tracking pixels.
- ·data from twitch accounts other than the one you sign in with.
4. how we use your data
- ·to operate the service — read chat, detect highlights, generate clips, deliver them through your telegram bot (if configured) or your klypra dashboard, and render your settings.
- ·to notify you — if you joined the waitlist, we use your email to let you know when pro launches.
- ·to keep the service healthy — we keep operational logs (worker heartbeats, error rates) so we can diagnose issues.
we do not use your data for advertising, profiling, machine learning training, or sell it to any third party. we do not send marketing emails.
5. where it lives & how it's secured
- ·account data, settings, clip metadata — stored in a managed postgres database. encrypted at rest by the provider, accessed over tls.
- ·clip mp4 files — stored in object storage. files are not publicly browsable; public shares use a randomized slug that is only known to whoever you share it with.
- ·telegram bot tokens — kept in our database with row-level access control so only your account row can read them. the raw token is never returned to your browser after setup.
- ·passwords — we don't have any; sign-in is delegated to twitch oauth.
- ·session cookies — http-only, secure, sameSite. used only to keep you signed in.
6. how long we keep it
- ·account data — until you delete your account.
- ·clips (free plan) — auto-deleted after 14 days.
- ·clips (pro plan) — auto-deleted after 30 days.
- ·operational logs — short-lived worker logs are kept only as long as they are useful for diagnosing issues, and are not used for any other purpose.
when you delete your account, we wipe everything in the above list. this happens immediately — no soft-delete or grace period.
7. third parties we share data with
klypra relies on a small set of infrastructure providers to do specific jobs. we only share what each one needs:
- ·account and settings storage — a managed database provider holds your account data, channel list, and clip metadata.
- ·clip file storage — an object storage service holds the generated mp4 files.
- ·email service — if you join the waitlist, an email provider handles delivery of launch notifications.
- ·website hosting — a hosting platform serves the klypra web frontend; they see standard http request logs only (no body content).
you also actively connect two services that we exchange data with on your behalf:
- ·twitch — we connect to public chat for the channels you add (using the
chat:readscope) and verify your identity at sign-in. - ·telegram — if you set up delivery, your own bot token + chat id are used to send clips through your own bot.
we do not use any analytics or behavioural tracking services.
8. your rights
you can, at any time:
- ·access the data we hold about you — write to timpe.hen@gmail.com and we will send you a complete export.
- ·correct anything inaccurate — most fields are editable from your settings page; for anything else, write to us.
- ·delete your account and all associated data — there is a delete-account option in settings, or write to us.
- ·revoke twitch access — from twitch's connections page. this stops monitoring immediately.
- ·export your clips — every clip is downloadable as mp4 from the clips page.
if you are in the eu/uk, you have additional rights under gdpr (data portability, restriction of processing, objection to processing, lodge a complaint with a supervisory authority). we honour all of them.
9. changes to this policy
we will update the "last updated" date at the top whenever we change anything material. it is your responsibility to check this page from time to time for changes.
10. contact
questions, requests, or concerns? write to timpe.hen@gmail.com.