Privacy policy
Last updated 19 Nov 2026
Which data Schaufilm Clips processes when you upload gameplay, who helps us with it and how long we keep it.
Controller
The controller for processing your data at Schaufilm Clips (clips.schaufilm.de) is Schaufilm, owner Dursun Sagnak, Schloßschmidstraße 23, 80639 München, Germany.
Email: info@kaderoy.app
We have not appointed a data protection officer because there is no legal obligation to do so. Send questions about data protection to the email address above.
Visiting the website
The website and interfaces of Schaufilm Clips run on Cloudflare (Cloudflare, Inc., USA; Cloudflare Workers). On every visit, Cloudflare processes technically necessary data: IP address, date and time, the address requested, browser and device type. Error messages of our server end up in the Cloudflare Workers logs.
- Purpose: delivering the website, protection against attacks and overload.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is secure and stable operation.
- Rate limits: for limits (for example uploads per day) we do not store IP addresses in plain text, only as a hash created with a secret key (HMAC). We delete the counters once their time window has passed, after 24 hours at the latest.
- Third country: Cloudflare, Inc. is certified under the EU-US Data Privacy Framework (adequacy decision of the EU Commission, Art. 45 GDPR).
Bot protection with Cloudflare Turnstile
When you start an upload without an account or sign in, we use Cloudflare Turnstile to check that a human is making the request. Turnstile only loads on these pages. Cloudflare processes your IP address and technical characteristics of your browser and creates a check token that our server has Cloudflare confirm.
- Purpose: protection against automated requests and against abuse of the free minutes.
- Legal basis: Art. 6(1)(f) GDPR; access to your device is strictly necessary under § 25(2) no. 2 TDDDG.
- Third country: Cloudflare, Inc. is certified under the EU-US Data Privacy Framework (adequacy decision of the EU Commission, Art. 45 GDPR).
Using Clips without an account
You can start an upload without an account. We then create a provisional guest account and link it to your browser with the sf_anon cookie. If you sign in within 7 days, we move the upload into your account. Clips made without an account are deleted after 3 days. If you don’t sign in, we delete the rest of the upload after 7 days, together with the guest account.
Legal basis: Art. 6(1)(b) GDPR (contract or pre-contractual steps).
Account and sign-in
You sign in with a link by email, with Google or with Discord. There is no password.
- Account and database: Supabase (Supabase, Inc., USA), servers in the EU (Frankfurt). We store your email address, your account ID, the sign-in method and the times you signed in.
- Sign-in with Google: we receive from Google (Google Ireland Limited, Ireland) your email address, your name, your Google account ID and the link to your profile picture.
- Sign-in with Discord: we receive from Discord your email address, your username, your Discord account ID and the link to your profile picture. Discord’s privacy policy applies to signing in at Discord itself.
- We send the sign-in link and the code for deleting your account via Resend (see Emails).
- Legal basis: Art. 6(1)(b) GDPR.
- Storage period: until you delete your account, afterwards only as far as statutory retention duties apply.
- Third country: Supabase, Inc. is not certified under the EU-US Data Privacy Framework. Transfers are based on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) in the data processing agreement.
Your videos
You upload recordings of your gameplay, up to 50 files per upload. Your browser uploads them directly to our storage at Cloudflare R2 (Cloudflare, Inc., USA). The storage is in Cloudflare’s EU jurisdiction, so the data stays in the EU. Videos can contain personal data: your voice in the commentary, your face in a facecam, your player name and, if they can be heard or seen, voices and names of other people.
- For each video we store the file name, size, length, technical format details, the upload times and a hash of your IP address (HMAC).
- Purpose: creating, previewing and delivering your clips.
- Legal basis: Art. 6(1)(b) GDPR.
- We delete uploaded videos 7 days after the upload. If processing ends later, we delete them 7 days after it ends.
- Uploads that do not finish are aborted after 24 hours without progress or 72 hours in total, and their parts are deleted.
- If you remove a video or cancel an upload, we delete the file at once and, to be safe, once more 2 hours later at the latest.
- The details of the videos (without the video file) stay visible in your account until you delete it.
- If you upload recordings with other people in them, make sure you are allowed to. We only process their data to create your clips.
Processing on our server
Our own renderer processes the videos. It runs on a server we rent from Hetzner Online GmbH (Germany). The server is in a data centre in Helsinki, Finland, within the EU. The renderer reads your videos directly from storage and carries out these steps itself, without passing data to third parties:
- Speech recognition (faster-whisper): a local speech detection on our server first marks where someone talks, and only those parts are turned into text with timestamps, for captions and for picking moments. We only recognise what is said, not who is speaking.
- Facecam detection (YuNet, OpenCV): finds where a face is in the frame so the crop does not cut off the facecam. We do not identify anyone and create no biometric templates.
- Text recognition (tesseract): reads in-game displays, for example banners at game events.
- Cutting, captions and export of the clips (ffmpeg).
The renderer deletes work files (scaled-down videos, audio track) 24 hours after processing ends at the latest, and the files of a finished clip right after saving them to R2. We store the analysis of a video (transcript, timestamps, measurements) and the texts of the clips with your clips in R2 so you can recreate clips later. The legal basis is Art. 6(1)(b) GDPR.
Picking moments with Anthropic
To pick and describe the strongest moments we use the Claude API by Anthropic. Our contracting party is Anthropic Ireland, Limited (Ireland); the data is processed by Anthropic, PBC in the USA. For each candidate moment we send: a contact sheet of 8 still frames from the video (it can show your facecam and thus your face), the transcript of the commentary in that section and measurements such as loudness and scene changes. We do not send the file name, your email address or your account.
Anthropic returns a rating with a reason, hooks, title, description, hashtags and suggestions for the crop. The AI makes no decisions about you as a person. There is no automated decision within the meaning of Art. 22 GDPR.
- Role: Anthropic processes the data as a processor on our behalf (Art. 28 GDPR) and may not use it to train its models.
- Storage at Anthropic: Anthropic deletes inputs and outputs 30 days after receipt at the latest. Longer, up to 2 years, only if Anthropic classifies a request as violating its usage policy or the law requires it.
- Legal basis: Art. 6(1)(b) GDPR.
- Third country: Anthropic is not certified under the EU-US Data Privacy Framework. Transfers are based on the EU Standard Contractual Clauses (Art. 46(2)(c) GDPR) in the data processing agreement.
Finished clips and downloads
We store finished clips in Cloudflare R2 (EU jurisdiction), depending on your plan when they were created: Free 3 days, Starter 30 days, Pro 90 days, Creator 180 days. Then we delete the files. Title, rating and times of the clip stay visible in your account as an expired clip. We delete the ZIP files of an upload once all their clips have expired.
For downloads we create links valid for 10 minutes. We log every download with its time in your download history. The legal basis is Art. 6(1)(b) GDPR.
Minutes and welcome minutes
We store your minute balance, every credit and every charge in a ledger. The 30 welcome minutes without an account are given once per browser and to at most 3 guests per internet connection in 24 hours. For this we store the hash of your IP address (HMAC) with the time of the credit and set the sf_clips_guest cookie. Welcome minutes are given only once per person. For this we store a hash of your normalised email address (HMAC), which remains after you delete your account. Clips made without an account stay locked until you sign in with a confirmed email address: until then you only see the cover, the title and a watermarked 5-second teaser, which we store and delete together with the clip. Minutes the guest work used are deducted from your account when you sign in. We compare the domain of your email address with a list of disposable mail providers; this happens on our servers and nothing is sent to anyone.
Legal basis: Art. 6(1)(b) GDPR for the balance; Art. 6(1)(f) GDPR for limiting the welcome minutes. Our legitimate interest is that free minutes are not claimed several times.
Payment
Payments run through Stripe (Stripe Payments Europe, Limited, Ireland), by card, Apple Pay, Google Pay, PayPal, Klarna or Link, the payment service of Stripe. You enter your payment details directly at Stripe; we do not see them. Stripe is itself responsible for payment data, for PayPal also PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg, for Klarna also Klarna Bank AB (publ), Sweden, for Apple Pay Apple and for Google Pay Google.
- We send Stripe your email address, our internal ID of your account and the product you chose. From Stripe we receive name, billing address and tax ID as far as you enter them, the payment status, invoices and notices of refunds, chargebacks and suspected fraud.
- We store your consent that we start right away (see Right of withdrawal) with its time as proof.
- Legal basis: Art. 6(1)(b) GDPR; for invoices and accounting Art. 6(1)(c) GDPR; for fraud prevention Art. 6(1)(f) GDPR.
- Storage period: we keep invoices and accounting records as long as commercial and tax law requires (§ 147 AO, § 257 HGB, usually 8 to 10 years). They stay with Stripe after you delete your account.
- Third country: Stripe may transfer data to Stripe in the USA; Stripe, LLC is certified under the EU-US Data Privacy Framework (adequacy decision of the EU Commission, Art. 45 GDPR).
Partner program
If you enter a partner code at checkout, we store which partner your account is attributed to and note the code at Stripe. A link with a code only fills in the input field. We set no cookies for this and use neither local storage nor fingerprinting. The partner does not learn who you are: their statement names no name, email address or invoice number.
- Checks for own purchases: for payments of partner accounts and attributed accounts, Stripe gives us an identifier of the payment card that does not reveal the card number. We compare it only to detect purchases with the partner's card or with one card across several accounts, and delete it after 24 months. Legal basis: Art. 6(1)(f) GDPR.
- Customer data: attribution of the account to the partner, amounts paid, payment times, refunds and chargebacks. Legal basis: Art. 6(1)(b) GDPR for the discount, Art. 6(1)(f) GDPR for settling the program; our legitimate interest is correct commission and preventing abuse.
- Partner applications: name, email address, channel link and audience size reach us by email through Resend. Legal basis: Art. 6(1)(b) GDPR (steps before a contract). We delete rejected applications after 6 months at the latest.
- Partners: master data, code, commissions and payouts. Legal basis: Art. 6(1)(b) and (c) GDPR.
- Storage period: we keep commission and payout records as long as commercial and tax law requires (§ 147 AO, § 257 HGB, usually 8 to 10 years). If you delete your account, the attribution is removed; the booking records remain without reference to you.
Protecting our offers against misuse
So that free minutes, the launch offer, the partner discount and withdrawals are not exploited repeatedly through new accounts, we derive a hash from your email address: we normalise the address (lowercase, no plus suffix, no dots for Gmail and Proton, one domain each for Gmail, Proton and iCloud) and calculate an HMAC from it with a secret key. We do not store the address itself for this.
- Free minutes: hash of your email address and of your IP address, so that they are given once a month per mailbox and for at most 30 accounts per internet connection.
- Launch offer: hash of your email address once you redeem the offer, so that it applies once per person. It stays stored after you delete your account until the period below has ended.
- Withdrawals: hash of your email address and the time of completed withdrawals. After 2 withdrawals in 12 months we no longer accept new orders automatically online. Your right of withdrawal is not affected.
- Partner discount: hash of your email address once you redeem a partner code, so that the discount and the attribution apply once per person. It stays stored after you delete your account until the period below has passed.
- Chargebacks and suspected fraud: a note with the hash of your email address that new purchases are blocked until the matter is resolved. The block also applies to new accounts with the same address and stays in place after you delete your account until the period below has passed.
- Legal basis: Art. 6(1)(f) GDPR. Our legitimate interest is protecting our offers and payments against misuse.
- If one of these blocks affects you, write to us: a person reviews the case. You can also object to the processing on grounds relating to your particular situation (Art. 21 GDPR). These blocks apply automatically. You can state your position and ask for a person to review the decision.
Emails
We send emails via Resend (Plus Five Five, Inc., USA): sign-in links, the code for deleting your account, contract confirmations with the terms and withdrawal information, receipts for cancellations and withdrawals, a notice when your clips are ready, reminders before the launch month ends and before a yearly plan turns monthly, and partner program applications. Stripe sends payment receipts and invoices. We do not send a newsletter.
- Legal basis: Art. 6(1)(b) and (c) GDPR.
- Third country: Resend (Plus Five Five, Inc.) is certified under the EU-US Data Privacy Framework (adequacy decision of the EU Commission, Art. 45 GDPR).
Cookies and browser storage
We only use cookies and browser storage needed to provide Schaufilm Clips, including limiting the free minutes to one use per browser (§ 25(2) no. 2 TDDDG). We do not set advertising or tracking cookies. That is why there is no cookie banner.
- sf_anon (cookie, 7 days): links your upload without an account to your browser.
- sf_clips_guest (cookie, 400 days): only notes that this browser has already started without an account. It contains no ID.
- sf_claim (cookie, 1 hour): moves your upload into your account when you open the sign-in link on another device.
- Supabase sign-in cookies (names start with sb-): keep you signed in until you sign out or the session expires.
- sf_clips_auth (cookie, 30 days): only notes that someone was signed in in this browser, so the page knows whether to look up your account. It contains no ID.
- sf_clips_delete (cookie, 15 minutes): holds the code for deleting your account in encrypted form until you enter it.
- clips:own:… and clips:last-session (local storage): remember which videos of an upload come from this device and which upload you opened last.
- clips:arrival (session storage): notes for one page change that a new upload has just started.
- Cloudflare Turnstile: stores technical check data, only when you start without an account and when you sign in.
- Stripe’s payment page runs on checkout.stripe.com. Stripe’s privacy policy governs the cookies Stripe sets there.
Logs and records
We log important events in your account: payments, refunds, your consent to an immediate start, rejected payment events and the deletion of your account including a summary of your minute balance. The legal basis is Art. 6(1)(c) and (f) GDPR. Our legitimate interest is being able to prove payments and consents and to detect abuse.
Analytics and error monitoring
We do not use tools for audience measurement, product analytics or error monitoring. Before that changes, we will update this policy.
Storage periods at a glance
| Data | Storage period |
|---|---|
| Uploaded videos | We delete uploaded videos 7 days after the upload. If processing ends later, we delete them 7 days after it ends. |
| Unfinished or removed uploads | 24 hours without progress, 72 hours in total, removed files after 2 hours at the latest |
| Finished clips | Free 3, Starter 30, Pro 90, Creator 180 days |
| Work files on the renderer | 24 hours at the latest |
| Upload without an account (guest) | 7 days unless you sign in |
| Account, uploads, minutes, download history | until you delete your account |
| IP hash for limits | end of the time window, 24 hours at the latest |
| IP hash of the welcome minutes | 24 hours |
| Email hash of the welcome minutes | 24 months, also after you delete your account |
| Hashes for the monthly free minutes | until the end of the month, then 7 more days |
| Email hash of the launch offer | until 7 days after the offer ended, also after you delete your account |
| Email hash of a redeemed partner code | 24 months, also after you delete your account |
| Billing block (with email hash) | up to 36 months, 12 more months after it was lifted, also after you delete your account |
| Log of completed withdrawals (with email hash) | 12 months, also after you delete your account |
| Analysis files of an upload (transcript, evaluation) | until processing of the upload has ended, its clips have expired and its videos are deleted, at the latest with your account |
| Cancellations, withdrawals and the log of billing events | 10 years from the end of the calendar year (§ 147 AO) |
| Other log of important events | 3 years from the end of the calendar year (§§ 195, 199 BGB) |
| Invoices and accounting records | as commercial and tax law requires, usually 8 to 10 years |
Recipients at a glance
- Cloudflare, Inc., USA: hosting, storage (R2, EU jurisdiction), bot protection (Turnstile). Processor.
- Supabase, Inc., USA: database and sign-in, servers in the EU (Frankfurt). Processor.
- Hetzner Online GmbH, Germany: server of our renderer, located in Helsinki (Finland). Processor.
- IONOS SE, Germany: hosts the mailbox info@kaderoy.app that receives support mail, withdrawals and partner program applications. Processor.
- Anthropic Ireland, Limited, Ireland, with processing by Anthropic, PBC, USA: picking and describing moments. Processor.
- Plus Five Five, Inc. (Resend), USA: sending emails. Processor.
- Stripe Payments Europe, Limited, Ireland: payments, invoices and Link. Separate controller.
- PayPal (Europe) S.à r.l. et Cie, S.C.A., Luxembourg: payments with PayPal. Separate controller.
- Klarna Bank AB (publ), Sweden: payments with Klarna. Separate controller.
- Apple: payments with Apple Pay. Separate controller.
- Google: payments with Google Pay. Separate controller.
- Google and Discord: only if you sign in with them. Separate controllers.
Your rights
- Access to your data (Art. 15 GDPR)
- Rectification of incorrect data (Art. 16 GDPR)
- Erasure (Art. 17 GDPR)
- Restriction of processing (Art. 18 GDPR)
- Data portability (Art. 20 GDPR)
- Withdrawal of consent with effect for the future (Art. 7(3) GDPR)
In your account under “Data and account” you can download your data as a file (the links to your clips in it are valid for 24 hours) and delete your account. For everything else an email to info@kaderoy.app is enough.
You can also complain to a data protection supervisory authority. The authority responsible for us is the Bayerisches Landesamt für Datenschutzaufsicht (BayLDA), Promenade 18, 91522 Ansbach, Germany, www.lda.bayern.de.
Do you have to provide data?
There is no legal obligation. Without videos, however, we cannot create clips, without an email address we cannot create an account and without payment details we cannot bill a plan.
Changes
If we use new services or change processes, we update this policy. The version with the date at the top of this page applies.