Privacy Policy

This is what StreamCatcher collects, why, and who else ends up seeing it. It covers streamcatcher.pro and the app behind it. We have tried to write it in the same language we would use to answer the question in an email.

The short version

• We collect what we need to run the product: your account, the clips you make, and basic technical logs.
• Your video and audio go to a handful of named services because the product cannot cut, transcribe or store a clip without them. They are all listed below.
• We do not sell your data, and there are no advertising or analytics trackers on this site.
• Delete a clip and it is gone. Delete your account and all of it is gone.

What we collect

Your account

Your name, your email address, a hashed password, and — if you add them — an avatar, a username for your public profile, and your team's name. If you sign in with a two-factor code we store the secret needed to check it. We never store your password in a form we can read.

What you make

The clips you create and everything attached to them: the segment we cut from the VOD, the finished MP4, the thumbnail or cover image, the transcript and any translation of it, your caption settings, and — if you record them — your voiceover audio and your picture-in-picture webcam video. Also the stream metadata we fetched from Twitch so the clip has a title, a channel and a timestamp.

What you connect

If you connect Twitch (optional — public VODs do not need it), we store the access and refresh tokens for that connection, encrypted at rest. If you bring your own AI API keys in settings, those are encrypted at rest too, used only for your own account's jobs, and never shown back to you in full.

Usage and technical data

Ordinary server logs: the pages and API endpoints you request, your IP address, your browser and operating system, timestamps, and the outcome of background jobs (whether a clip trimmed, transcribed and captioned, or failed and why). When something errors we capture a diagnostic report — the error, the request, and which account hit it — so we can fix it.

Billing

We never see or store your card number. Payment details are entered into Stripe's own checkout and stay with Stripe. What we keep is what Stripe tells us afterwards: a customer id, which plan you are on, whether you are in a trial, when the next renewal is, and your invoices and receipts. If tax has to be calculated, Stripe may also hold a billing address you gave it.

What we do not do

• We do not sell or rent your personal data, and we do not share it for advertising.
• There are no ad pixels, no analytics SDK and no cross-site trackers on this site.
• We do not read your clips for anything other than running the service and, if you ask us to, helping you with a support question.

Who else touches your data

A clip cannot be made without outside services. These are all of them, and exactly what each one receives:

• Twitch — the channel name you search for and the id of the VOD you open. We read public stream metadata, and for the chat-activity view we read the VOD's public chat replay to count messages per ten seconds. When you export, the marked segment is fetched from Twitch's video servers.
• OpenAI — the audio of the segment you clipped, sent to the Whisper API to produce the word-level transcript your captions are timed to.
• Anthropic and DeepSeek — text only. The stream's title, game and audio-peak timings when you ask for AI highlight suggestions, and your transcript text when you ask for a caption translation. Whichever of the two runs depends on which key is configured for your account.
• Replicate — a single still frame from your clip, used by the face-detection model that positions the crop window for Pro's face-aware reframe. Nothing is sent unless that feature runs.
• DigitalOcean Spaces — object storage. Your video files, audio, thumbnails and covers live here.
• Stripe — your payment details, your email and your subscription. Stripe's checkout is embedded in our billing page, so it loads from Stripe and sets its own cookies there for fraud prevention.
• Resend — your email address and the contents of the transactional email we send you: password resets, receipts, invitations, notifications about your clips.
• Hexdump — our own self-hosted error tracking and logging. It receives the diagnostic reports described above.
• Google Fonts — our pages load two typefaces from Google's font servers, which means Google sees the IP address of the browser requesting them. No cookie is set by that request.

Some of these are outside your country, so your data may be processed elsewhere — the United States in particular. We only send each service the part it needs, and we only use services whose own terms cover processing on our behalf.

We may also disclose data where the law requires it, or where it is necessary to investigate abuse of the service or to defend a legal claim.

How long we keep it

• Clips, transcripts and their files — until you delete them, or until you delete your account.
• Your account — until you delete it.
• Server and error logs — kept only as long as they are useful for debugging and security, then rotated away.
• Billing records — invoices and payment records are kept as long as tax and accounting law requires, even after an account is closed.

Deleting things

Deleting a clip deletes its transcript and its files. Deleting your account, from your account settings, removes your profile, your clips, your transcripts, your stored files and any connected-account tokens. Backups roll over on their own schedule, so a deleted item can survive in a backup for a short window before it is overwritten; it is not restored to the live service. If you would rather we did it for you, email us and we will.

Cookies

Only the ones the site cannot work without:

• a session cookie, which keeps you signed in while you use the app and protects forms against cross-site request forgery;
• a remember-me cookie, set only if you tick that box when signing in, so you are not asked for your password every visit.

That is the whole list. There are no advertising or analytics cookies, which is why you have not been shown a consent banner. Stripe sets its own cookies inside its checkout when you open the billing page.

Your rights

Depending on where you live you can ask us to show you the personal data we hold about you, correct it, delete it, export it in a portable form, or restrict or object to how we use it. Most of that you can do yourself from your account settings; for the rest, email us and we will handle it — normally within thirty days, and without charging you for it. If you think we have got it wrong, you can complain to your local data protection authority.

Children

StreamCatcher is not intended for children. You need to be old enough to hold a Twitch account and to enter a contract where you live. If you believe a child has created an account, tell us and we will remove it.

Security

Traffic is encrypted in transit. Passwords are hashed, and connected-account tokens and any API keys you add are encrypted at rest. Access to production data is limited to the people who need it to operate the service. No system is perfect; if we ever have a breach that affects you, we will tell you.

Changes to this policy

When this policy changes, the date at the top of the page changes with it. If a change is significant — a new service receiving your data, a new category of data collected — we will tell you by email or in the app rather than quietly editing the page.

Contact

Questions, requests, or a data-protection complaint: support@streamcatcher.pro.