Privacy Policy
As of: 4 November 2026
This is an English translation for your convenience. Only the German version is legally binding.
Test phase notice: this service is currently in a small, closed test phase with selected users. This policy will be finalized before a wider launch.
1. Controller
Bruno Martin Kempe, c/o Impressumservice Dein-Impressum, Stettiner Str. 41, 35410 Hungen
Email: datenschutz@lazyclipper.com
2. What data we process and why
Submitted video material: When you submit a clip link from Twitch or Kick or a video link from YouTube, we automatically download the clip or the selected excerpt to edit it for you (captions, framing, sound effects). This creates: the video material itself, an automatically generated text transcript, and automatically detected image coordinates (e.g. face position for the framing).
Better image quality for Twitch clips: Twitch stores clips heavily compressed. If the channel's VOD is publicly available, we additionally download the same moment from the VOD, locate it by matching its loudness against the clip and use the sharper picture, while the audio stays that of the clip. We delete the VOD excerpt right after matching; only the finished excerpt is processed further.
About face detection: We only detect the position of a face in the frame, not the identity of the person. No matching against a face database, no biometric profiles, no recognition across multiple videos.
Legal basis: Art. 6(1)(b) GDPR (performance of a contract, you actively request the editing).
Automatic deletion: The extracted audio is deleted automatically as soon as processing is finished. We keep the original clip (for VODs only the chosen section) and the word transcript of the source for at most 6 hours, so you can edit the clip afterwards (change section, revise, fix facecam) without us downloading and transcribing it again. After that both are deleted automatically. Only the finished video and small technical metadata for troubleshooting are kept.
Review by us: To find errors and improve editing quality, the operator can view and download the submitted links, chosen settings and finished clips of individual accounts in the protected admin area for as long as they are stored (see storage period). We only use them for this and do not share them. Legal basis: Art. 6(1)(b) GDPR (performance of contract) and Art. 6(1)(f) GDPR (legitimate interest in an error-free service).
Storage period: Finished videos stay available for download for 7 days on the Free plan, 14 days with Basic or purchased credit, 21 days with Starter, 30 days with Premium, 60 days with Enterprise and 21 or 30 days with the Streamer rank depending on its level, then they are deleted from our servers automatically. We delete a clip earlier if you delete it yourself, if you re-edit it (the new one replaces it) or if your gallery exceeds the maximum of your plan (then the oldest). The same applies to the transcript of the finished clip, which we only keep for the optional AI suggestions for title and description. The related history entry (e.g. for statistics) remains without the video file itself. On request (see contact above) we delete your finished video early at any time. The same goes for a small preview of the source (a strip of low-resolution stills, about one every two seconds, and the spoken text with timestamps), so you can adjust a clip's section later. We delete the raw video no later than 6 hours after processing (see automatic deletion). If you open "Change section", we create a smaller preview from it while the original is still there, otherwise we load it from Twitch or Kick once more. We delete the preview after one hour at the latest.
Uploaded videos (only for unlocked testers): If you upload your own clip as a file (for example from the Whatnot or eBay Live app), we first store the file in an isolated area of our server, scan it automatically for malware (ClamAV, running on our own server) and look at it once by hand before processing. This is necessary because we are responsible for content processed through our service and must not process illegal content. If the file is approved, we process it like a clip link and delete the original right afterwards. If we reject it or do not review it within 72 hours, we delete it and refund the credit. We keep the original file name, your chosen settings and your context text, the time and our decision until you delete your account. Legal basis: Art. 6(1)(b) GDPR (performance of contract) and Art. 6(1)(c) and (f) GDPR (legal obligations and protection against abuse). If instead of a file you provide a share link from Google Drive or Dropbox, our server downloads the file there and then treats it exactly like an upload. Google or Dropbox only see our server's address, no data from your account with us.
Suspected criminal offences in uploads: If an uploaded file gives rise to the suspicion of a criminal offence that threatens the life or safety of persons, we are obliged to report this suspicion, together with the file and the related account data, to the German Federal Criminal Police Office (Art. 18 DSA). The legal basis is Art. 6(1)(c) GDPR. We then keep the file secured until the authority no longer needs it.
Your media library: Images (e.g. your logo) that you voluntarily upload to your media library are stored on our own servers until you delete them or your account. We no longer accept audio files, you can still delete ones uploaded earlier. No access by other users.
Training opt-in (optional, off by default): If you tick the corresponding box when submitting a clip, we additionally store the analysis data derived from your clip (e.g. framing used, detected emphasis points, transcript) in a separate archive so we can fine-tune our detection logic with real cases. The raw video is NEVER stored, only this derived metadata, and there is no automated model training, only manual, iterative calibration. The archive contains no account data, only the clip's name and these analysis files. We keep it for at most 12 months and then delete it automatically. Legal basis: your explicit consent (Art. 6(1)(a) GDPR) by actively ticking the box, without this consent none of this happens. You can withdraw your consent at any time by writing to us. We then delete the archived data of your clips.
Cancellations: If you cancel via "Cancel your contract here", we store your details (email address, optionally your name, type of cancellation, reason if given, requested end date), the date and time of receipt and your IP address. We need this to carry out the cancellation, confirm it to you and prove receipt. Legal basis: Art. 6(1)(b) and (c) GDPR (contract handling and the statutory confirmation duty under § 312k BGB). Storage period: until the regular three year limitation period ends, counted from the end of the year of cancellation.
Withdrawals: If you withdraw via "Withdraw from contract", we store your details (name, email address, affected contract, optional order date), the date and time of receipt and your IP address. We need this to process the withdrawal, refund payments, confirm receipt to you and be able to prove it. Legal basis: Art. 6(1)(b) and (c) GDPR (contract handling and statutory confirmation duty under § 356a BGB). Storage period: until the regular three-year limitation period ends, counted from the end of the year of the withdrawal. The same applies to the record of which Whop purchase belongs to which account.
Revenue: For every payment Whop reports to us, we store the Whop payment ID, amount, time and whether it was a subscription or a token pack for our bookkeeping, and for refunds and chargebacks also the amount paid back. We do not store a link to your account. Legal basis: Art. 6(1)(c) GDPR (retention duty under § 147 AO). Storage period: as long as the tax retention period runs, at most ten years from the end of the year of the payment.
Consent when buying: If you confirm before a purchase that we should start the service immediately, we store the time, the version of the text you agreed to and your IP address so we can prove the consent. Legal basis: Art. 6(1)(b) and (f) GDPR. Storage period: as long as your account exists, but at least 3 years after the purchase, even if you delete your account earlier, because we must be able to prove the consent until possible claims become time-barred.
Confirmation of rights to the clip: When you submit a clip, a VOD or a file, we store, as proof of your assurance under section 3 of our terms, your account, the time, the link or the note "Upload", the version of the text and whether you ticked the box or submitted via the API, a bot or Discord. Legal basis: Art. 6(1)(f) GDPR, our interest is being able to defend ourselves against claims of rights infringement. Storage period: 3 years from submission, even if you delete your account earlier.
Feedback: If you rate a clip (thumbs, tags, free text), we store this with your account and the clip to improve our editing. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a better service). We keep feedback for at most 12 months.
Server logs: Our server logs technical events, for example errors, login attempts and blocked requests. These may contain your IP address. We need this to find errors and detect attacks. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a secure and working service). Retention: at most 30 days, after which the server deletes the logs automatically.
Protection against attacks: To keep LazyClipper available during attacks or very high load, we route all requests through Cloudflare (see section 3). Legal basis: Art. 6(1)(f) GDPR (legitimate interest in a secure and available service). How long Cloudflare keeps request data for security and operations is governed by our contract with Cloudflare. We only receive totals from Cloudflare (for example number of requests and blocked attacks), no data on individual visitors.
Usage analysis: To see which features are needed and which are hardly used, we record on our server on which days your account used which feature (for example VOD analysis, editor, AI titles, downloads) and evaluate the settings of your clips from the history. We also count how many suggestions from a VOD analysis get cut. We only evaluate totals across all accounts. We use no cookies for this, store nothing in your browser and use no third-party services. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in improving the service and spotting unnecessary features). Retention: at most 13 months, immediately when you delete your account. If you object (see below), we switch off the counting and the surveys for your account and delete the previous entries.
Origin and short surveys: If you reach us through a link with an identifier (for example utm_source, utm_campaign or a creator code), our pages attach this identifier to their links so that it arrives at sign-up. We set no cookie for this and store nothing in your browser. At sign-up we store this information with your account. In the app we ask you, voluntarily, how you heard about us and, at most every 90 days, how likely you are to recommend us and what you are missing. After cancelling you can voluntarily pick reasons; the cancellation is valid regardless. All questions are multiple choice without free text, and you never have to answer. We store your answers with your account. If you skip a question we remember that too, so we do not ask again. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in understanding how customers find us and what we should improve). Retention: the origin from the link and your answer on how you heard about us for as long as your account exists; recommendation, missing features and cancellation reasons for at most 24 months. If you delete your account we remove the link to you, and the answers then only count in the totals without reference to a person.
Sign-in and session: When you sign in, we set a cookie called "session" with a random identifier. It is strictly necessary to keep you signed in (§ 25(2) no. 2 TDDDG). If you choose "stay signed in", it is valid for 30 days from your last use, otherwise until you close the browser. For each session we store its start, expiry, your IP address and your browser identifier so you can end sessions and we can detect abuse. This is deleted with the session. We store every sign-in attempt with email address, IP address, result and time to lock an account for 15 minutes after eight failed attempts in a row. We delete these entries after 30 days. So that a stranger cannot lock you out this way, after a successful sign-in we set a cookie called "lc_device" with a random identifier for your device. With it you can still sign in with your correct password while the lock is active. It is strictly necessary (§ 25(2) no. 2 TDDDG), is valid for 180 days and is only sent when signing in. We store only a hash of it with a timestamp, for at most ten devices, and delete all of them when you change your password. If you turn on two-factor sign-in, we store its secret in your account. Password reset links are stored only as a hash and are valid for 30 minutes. Legal basis: Art. 6(1)(b) and (f) GDPR (protecting your account).
Sign in with Twitch: If you sign in with Twitch or connect your account to Twitch in the settings, we send you to Twitch. Twitch then gives us your Twitch ID, your username and the email address of your Twitch account, including whether it is verified. We store the Twitch ID and username to recognize your account at your next sign-in, and create a new account with this email address. We revoke the Twitch access token right away, after that we cannot read or do anything in your Twitch account. During sign-in we set the cookies "lc_tw_state" (10 minutes, protection against forged sign-ins) and "lc_tw_signup" (15 minutes, only for a new account). Both are technically necessary (§ 25(2) no. 2 TDDDG). Details from an unfinished sign-up are deleted after 15 minutes. Legal basis: Art. 6(1)(b) GDPR. Storage period: until you disconnect in the settings or delete your account.
Deleting your account: Write to datenschutz@lazyclipper.com and we will delete your account without undue delay, at the latest within one month. We disconnect your connections at Twitch, YouTube and PostPeer and delete your finished clips, your media library and everything stored in your account (settings, channels, templates, presets, campaigns, posting plan, bot entries, Discord link). We delete the usage analysis of your account. In the history, the error log, feedback and survey answers we remove the link to you and your context text, these entries disappear completely once their period has expired. We keep cancellations and withdrawals as well as the record of your Whop purchases until the limitation period ends (see there), because we must be able to prove them.
Backups: So that no accounts, balances or records are lost in a technical failure, we back up the database once a day. Backups are kept for 14 days on our server in Germany and additionally for at most 90 days, encrypted, on a computer of the operator. If you delete your account, your data therefore disappears from all backups within 90 days at the latest. Legal basis: Art. 6(1)(f) GDPR (legitimate interest in reliable operation) and Art. 32 GDPR.
Email address confirmation: When you sign up, we send you a 6-digit code via our email service provider. Until you enter it, we store your email address, your password only as a hash, the invite code, any creator code you entered and the code itself only as a hash. Without confirmation we delete this after one hour at the latest and no account is created. This ensures nobody uses someone else's address. We check with Brevo whether the email was delivered or rejected, so we can tell you right on the page. Legal basis: Art. 6(1)(b) GDPR and Art. 6(1)(f) GDPR (protection against abuse).
Age confirmation: When you sign up you confirm that you are at least 16, before your first purchase that you are an adult. We only store the time of the confirmation, no date of birth, for as long as your account exists (Art. 6(1)(b) GDPR). If someone signs up with an address that already has an account, we send a notice to that address instead of a code, so nobody can use the form to find out who has an account.
Accepting the terms of service: When you sign up, and for older accounts at the next login after a change, you accept the terms of service. We store the time and which version it was, so we can prove the content of the contract. Legal basis: Art. 6(1)(b) and (f) GDPR. Storage period: as long as your account exists, then until the three-year limitation period ends.
Protection against automatically created accounts: When you sign up, your browser invisibly solves a small computing task (ALTCHA, running on our own server, without cookies and without third parties). We don't accept addresses from disposable email services. So that not unlimited accounts can be created from one connection, we store an irreversible hash of your IP address with the time when an account is created and delete it after 24 hours. Legal basis: Art. 6(1)(f) GDPR (protection against abuse of our free offer).
Creator codes: If you enter a streamer's code when signing up or in the settings, we store it with the date in your account. When you buy, we pass it on to Whop so the streamer receives their commission and you get a discount where offered. What the streamer sees about this in their affiliate area at Whop is decided by Whop. They get no data about you from us. We set no cookie for this and store nothing in your browser, a link with a code only pre-fills the input field. Legal basis: Art. 6(1)(b) GDPR, because you enter the code yourself to use the discount. Storage period: as long as your account exists.
Creator partners: If you get your own code as a streamer, we store your name or channel name, your Whop username for payouts, the code and how many accounts and payments are assigned to it, plus your acceptance of the creator terms. Legal basis: Art. 6(1)(b) GDPR (partner agreement), for accounting records (c). Storage period: until the partnership ends, accounting records until the statutory retention period ends.
API access: If you create an API key, we only store a one-way hash of it, its first characters so you can recognise it, the creation date and the time it was last used. In addition, we keep in memory for at most 24 hours which orders were submitted with which idempotency key and how many requests your account made recently, so that retries are not charged twice and usage limits apply. Legal basis: Art. 6(1)(b) GDPR. Storage period: until you revoke the key or delete your account.
Language: The site picks German or English based on your browser's language setting, without looking up your location. If you switch the language yourself or open a link with a language code (?lang=), we store your choice in a cookie called "lang" on your device (valid for one year). The cookie is strictly necessary to carry out your explicit request (§ 25(2) no. 2 TDDDG) and only contains "de" or "en".
Last used clip settings: When you process a clip, your browser remembers the settings you chose (for example length, sound effects, caption style) in your device's local storage under "lc.clipPrefs.v1", so they are preselected next time. This stays on your device, we don't receive it. You can delete it any time in your browser settings. Legal basis: § 25(2) no. 2 TDDDG, because it only keeps your own choice for the feature you use.
View and channel: Which calendar view you last used ("lc.planView"), which channel you last picked ("lc.lastChannel"), which tab and channel filter you last had in "My clips" ("lc.clipsTab", "lc.clipsAllChannels") and whether you let suggestions be cut right away ("lc.suggestCut") is remembered only by your browser in local storage. It is not sent to us. Legal basis: § 25(2) no. 2 TDDDG.
Discord link (voluntary): If you enter the /link command with a code from your settings in the LazyClipper Discord, we store your Discord user ID together with your account. Our bot uses it to give you the role of your plan. We do not store your Discord name, your messages or your reactions, the bot only reads the name live from Discord when it replies. Only if you also turn on the leaderboard does the bot show your Discord name and the number of your finished clips in the respective month in the Discord. Legal basis: your consent under Art. 6(1)(a) GDPR, revocable at any time via "Disconnect Discord" in the settings or /unlink in Discord. The link is deleted when you disconnect and with your account. Whatever you post in the Discord yourself stays with Discord only, for users in the EU Discord Netherlands B.V. is responsible for it.
VOD analysis (from Starter or for unlocked accounts): If you have a whole VOD analyzed, we first download only its audio track. We detect loud moments on our own server. For Twitch VODs we additionally ask the official Twitch API which moments viewers have already saved as clips (public clip data only: position in the VOD, length, views). We have Groq transcribe the audio track, an AI reads the transcript together with these hints and your wishes and picks the suggestions. If you connected the Twitch bot, your channel's chat activity is taken into account (see Twitch bot). For each suggestion we then download the short excerpt as video so you can watch it before cutting. We delete the audio track right after the analysis, the preview excerpts after 24 hours and the list of suggestions (times, titles, reasons) after 7 days. We keep the word transcript for at most 3 days so a second analysis of the same VOD does not have to transcribe it again. Legal basis: Art. 6(1)(b) GDPR.
Checkout: When you start a purchase, your browser keeps the link to Whop's own checkout page in session storage under "lc.checkoutFallback" for as long as the tab is open, so we can offer it to you if the embedded payment window does not load. This is not sent to us and is gone when you close the tab. Legal basis: Section 25(2) no. 2 TDDDG.
Running VOD analysis: So you can find a VOD analysis you started if you close the window in between, your browser remembers its ID in local storage under "lc.lastAnalysis", for at most three days or until you cut the suggestions. This is not sent to us. Legal basis: Section 25(2) No. 2 TDDDG.
Clip editor draft: So that unsaved changes in the clip editor are not lost, your browser keeps the editing state in local storage under "lc-editor-draft:" with the clip name until you re-cut or discard the draft, for at most seven days. It is not sent to us. Legal basis: Section 25(2) no. 2 TDDDG.
Mascot: Whether the mascot is shown, how often it has appeared on its own today and which token balance you last saw (so coins can hop briefly when your balance goes up) is remembered only by your browser in local storage under "lc.mascot", "lc.mascot.day" and "lc.mascot.tokens". This is not sent to us. Legal basis: Section 25(2) No. 2 TDDDG. You can switch it off in the settings or clear your browser storage at any time.
Introduction tour: We store in your account whether you have seen the introduction, so it doesn't appear again on any device. Your browser also remembers this in local storage under "lc.tour.v1". Legal basis: Art. 6(1)(b) GDPR and, for browser storage, Section 25(2) No. 2 TDDDG. It is deleted with your account.
Channels: If you add more channels (for example for different streamers), we store per channel the name, the handles for the overlay, the chosen default logo and an identifier for the social accounts connected there at our posting service provider. If you delete a channel, we disconnect its social accounts and delete this data. Legal basis: Art. 6(1)(b) GDPR.
Team account: On the Enterprise plan the owner of an account can invite team members. To do so, the owner creates an invitation link and passes it on themselves, we do not send an email for this. If the owner enters an email address, we store it with the invitation so that only this address can join. Every team member has their own user account with their own login. We store which account they belong to, their role (admin or editor) and since when. Team members see and edit the clips, accounts, social connections, templates and posting plan of the account and use its tokens. Everyone in the team sees the email addresses of the owner and the other members. The owner and team admins manage the members (invite, change role, remove), payment and plan stay with the owner. Anyone who is removed or leaves the team works in their own account again, we delete the assignment immediately. Invitations are valid for 7 days, we delete them 30 days after they expire or are accepted. Legal basis: Art. 6(1)(b) GDPR.
Beta access request: If you request beta access through the form on our homepage, we store your email address, whether you are a streamer or a clipper, the platforms and the channel you voluntarily provide, and the language of the page. You can optionally choose how you found us. If available, we also store only the name of the website you came from (for example twitch.tv, never the full address) and a campaign tag from the link (utm_source), to see which channels work. To protect against automated requests, a small calculation runs in your browser (ALTCHA, run by us, no cookies). If we invite you, we send your invite code by email via Brevo. For every new request we notify ourselves by email via Brevo, with role, platforms, channel and how you found us, without your email address. After our decision we delete the request after 6 months at the latest, or right away on request. Legal basis: Art. 6(1)(b) GDPR (steps prior to using the service at your request).
Campaign board and age confirmation: Before you use the campaign board, you confirm once that you are at least 18 years old. For this you enter your date of birth. We only use it to calculate your age and store just the time of the confirmation, not the date of birth. The campaigns on the board are offers from other platforms. We take them from the public list of Content Rewards (contentrewards.com) or add them by hand: title, client, description, pay, budget, platforms and a preview image. We update the list every six hours and do not read out names of individual clippers. If you click "To the campaign", you open their page; from then on their privacy policy applies. We do not send any data about you and do not count clicks. If you adopt a campaign's rules, we create a campaign profile in your account from it (see Campaign profiles). Legal basis: Art. 6(1)(b) GDPR (performance of contract) and Art. 6(1)(f) GDPR (protecting minors in paid jobs).
Role in the tool: If you choose whether you are a streamer, a clipper or both, we store this choice in your account to show you the matching features first. You can change it in the settings, it is deleted with your account. Legal basis: Art. 6(1)(b) GDPR (performance of a contract). If you click "Decide later" instead, only your browser remembers under "lc.roleSkip" until you close the tab that the question is hidden. This is not sent to us (Section 25(2) No. 2 TDDDG).
Caption templates: If you create a caption template in your settings, we store its name, your text, your hashtag list and your choice of count and AI hook in your account, plus a counter of which hashtags were used last. When you use a template while posting, the caption is built from it. With AI hook, the clip transcript goes to Groq (see the recipients table), just like with the normal AI suggestion, but not the template itself. You can delete templates in your settings at any time, and they are deleted together with your account. Legal basis: Art. 6(1)(b) GDPR (performance of contract).
Campaign profiles: When you create a campaign in the settings, we store its name, the length rules, the streamer's handle, the required hashtags and your choices for credit and watermark in your account. If you pick the campaign for a clip, the handle is rendered into the video as an overlay and the rule check is stored with the finished clip. You can delete campaigns in the settings at any time, they are also deleted with your account. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
Clip presets: When you save settings as a preset, we store the name you choose and the selected settings (for example length, sound effects, caption style, speed) in your account. That way they're available on every device. You can delete presets at any time in the clip form, and they are also deleted with your account. Legal basis: Art. 6(1)(b) GDPR (performance of a contract).
Twitch bot: If you connect your Twitch channel in the settings, we store your Twitch ID, your channel name, the Twitch access tokens you granted (encrypted) and your bot presets. Twitch then sends us the chat messages of your channel. We only check each message for whether it starts with !clip or !mark and discard the content of all others immediately without storing it. We only count how many messages arrive in your chat per 10 seconds, without content and without sender, and use these numbers in the VOD analysis of your own channel to find moments when chat was especially active. We delete these counts after 60 days. If you turn on "After the stream", Twitch tells us when your stream ends. We then ask Twitch whether you are live again and which VOD was created last, and start a VOD analysis for it just like one you start yourself. For a !clip or !mark command we store the Twitch name of the person who wrote it, the given title and the time, create a Twitch clip with your token and process it like a clip you submitted yourself. If Twitch does not create the clip, we cut the same moment from the saved VOD of your stream instead. To choose your facecam, we load the current preview image of your stream or latest VOD from Twitch and show it to you without storing it. We store the box you draw for your channel. Legal basis: Art. 6(1)(b) GDPR for you as the streamer. For viewers who write !clip , Art. 6(1)(f) GDPR: your legitimate interest in letting your community save clips for you, and our interest in being able to trace misuse. Storage period: tokens and presets until you disconnect the channel or delete your account. When you disconnect, we also revoke the token at Twitch. The command entries as long as your account exists.
YouTube bot: If you connect your YouTube channel, we store your channel's ID and name, the Google access tokens you grant (encrypted, read-only) and your bot settings. While you are live, we read your stream's live chat via the YouTube API. We only check each message for whether it starts with !clip or !mark and discard all others immediately without storing them. For a command we store the person's display name, the title, the time and the position in the stream and post a short confirmation in the chat as the LazyClipper channel. After the stream we cut the saved moments from your stream video like a YouTube link you submitted. Legal basis: Art. 6(1)(b) GDPR for you as the streamer, Art. 6(1)(f) GDPR for viewers who type a command. Storage period: tokens and settings until you disconnect the channel or delete your account, saved moments as long as your account exists.
Facecam position per channel: So that clips of a channel are cropped correctly right away, we remember for public Twitch and Kick channels where the facecam sits in the frame: the channel name, the position as a rectangle (four numbers between 0 and 1), whether it was detected automatically or corrected by hand, and when. We don't store any images for this. The information applies to everyone who edits clips of this channel. If you mark the facecam yourself before editing, we briefly download the clip for this, take a still image, show it to you and delete the video and the image right away. Legal basis: Art. 6(1)(f) GDPR, our legitimate interest in reliable cropping. If this concerns your channel and you don't want it, write to us and we'll delete the entry and not create a new one.
Messages to our Instagram accounts: If you message one of our Instagram accounts or comment on a post, we read and answer it ourselves directly in Instagram, without an automated assistant. We process your Instagram name, the text of your message or comment and the time. We do not store the conversations outside Instagram. Legal basis: Art. 6(1)(b) GDPR, because you contact us actively and want something from us, otherwise Art. 6(1)(f) GDPR (legitimate interest in answering enquiries). Messages run through Instagram (Meta), where Meta's privacy policy applies.
3. Who receives data
| Recipient | Purpose | Location | Status |
|---|---|---|---|
| Contabo GmbH | Hosting: operation of the server on which accounts, clips and transcripts are stored and processed | Germany | Data processing agreement under Art. 28 GDPR |
| Cloudflare, Inc. | Protection against attacks and overload: all requests to lazyclipper.com pass through the Cloudflare network, which stops attacks and mass requests before they reach our server. Cloudflare technically processes every request, i.e. your IP address, the requested address, browser details and the transmitted content (the connection is encrypted, Cloudflare decrypts it for inspection and re-encrypts it to our server). If Cloudflare checks a request as suspicious, it may set a technically necessary cookie called "cf_clearance" that stores the passed check (Section 25(2) no. 2 TDDDG). Emails and the connection of our render servers do not pass through Cloudflare | USA (global network, requests from the EU are mostly served by data centres in the EU) | Data processing agreement under Art. 28 GDPR (Cloudflare Data Processing Addendum), EU-U.S. Data Privacy Framework and EU standard contractual clauses |
| netcup GmbH | Hosting: additional server on which clips are cut. It receives the clip, its audio and the transcript plus the editing settings, not your account. Source videos stay there for at most 6 hours, the finished clip goes back to our main server | Germany, server in Austria (Vienna) | Data processing agreement under Art. 28 GDPR |
| Hetzner Online GmbH | Hosting: additional servers that we rent by the hour only at times of high load, to cut clips faster. They receive the clip, its audio and the transcript plus the editing settings, not your account. Source videos stay there for at most 6 hours, the finished clip goes back to our main server, and the server is deleted together with its data after a few hours at most | Germany | Data processing agreement under Art. 28 GDPR |
| Migadu-Mail GmbH | Mailbox: receiving and sending emails you write to us or that we answer personally | Switzerland | EU Commission adequacy decision for Switzerland |
| MediaMinds360 - Cremer & Walther GbR (Dein Impressum) | Receiving and forwarding letters sent to the address in the legal notice | Germany | Data processing, agreement in place |
| Brevo (Sendinblue SAS), Paris | Email delivery: automatic emails such as sign-up confirmation codes, password links, confirmations of cancellation and withdrawal, and the purchase confirmation with contract details, terms and withdrawal information. Your email address and the content of the email are transferred | France, stored in France and Belgium | Data processing agreement under Art. 28 GDPR |
| Whop Inc. | Checkout: Whop processes payment for the paid plans and token packs, creates the receipt and remits VAT. Your email address, the chosen plan, an identifier of your account and, if you entered a creator code, that code and the creator's Whop account are transferred. We show the checkout on our site as an embedded window from whop.com. What you enter there, such as your payment details, goes directly to Whop, we do not see it. The window and the Whop script it needs only load on the checkout page, we block an additional analytics script from Whop there. Inside the payment window, Whop may set its own cookies needed for the payment (Section 25(2) no. 2 TDDDG) | USA | Only for a purchase, EU Standard Contractual Clauses for the data transfer. Whop itself is responsible for the payment, Whop's privacy policy applies there |
| Groq, Inc. | Speech recognition/transcription of the clip audio; if you request it, AI suggestions for title, description and hashtags based on the transcript; if you want to revise a clip, your feedback together with the clip's words and timestamps; if you use the microphone, converting your voice recording into text (we do not store the recording, it is only transmitted for this conversion). Also your context text for the clip, the channel name and the game as help for speech recognition, your wishes for the VOD analysis and, if you request a hook suggestion in the editor, the spoken text of the selected excerpt; if you turn on emojis, the spoken text of the clip so the AI can pick fitting emojis; if you create a template, the spoken text of the selected clips so the AI can write short keywords for the ranking or pick the strongest line per clip; if you request a sound tip, the spoken text of the clip and your context text, so the AI can determine the clip's mood (we store the mood with your clip, the sound suggestions only link to TikTok search, TikTok learns of it only when you open a link) | USA | DPA automatically part of Groq's terms of use, EU Standard Contractual Clauses (SCCs) for the data transfer. Zero Data Retention has been enabled for our Groq account since 31 October 2026: Groq does not store inputs and outputs, they are only processed for the respective request |
| Google LLC (YouTube) | Our server fetches public YouTube videos when you submit a YouTube link (we do not send any data about you). Only if you use the YouTube bot: sign-in with your Google account, reading your stream's live chat via the YouTube API and replying in the chat | USA | EU-US Data Privacy Framework (adequacy decision) |
| Twitch Interactive, Inc. | Retrieval of public clip metadata via the official Twitch API. If you use the Twitch bot: sign-in with your Twitch account, receiving the chat messages of your channel, creating clips and replying in chat. If you sign in with Twitch: Twitch confirms your account to us (see "Sign in with Twitch") | USA | Without the Twitch bot only read access to data that is already public. With the Twitch bot, the data you allow Twitch to share when signing in. According to Twitch, transfers to the USA are covered by adequacy decisions or EU Standard Contractual Clauses |
| Kick Streaming Pty Ltd | Retrieval of the public clip or VOD (video and metadata) when you submit a Kick link | Australia | Only retrieval of data that is already public, none of your data is transferred to Kick |
| Have I Been Pwned (Troy Hunt), “Pwned Passwords” service | Checking whether a new password appears in known data breaches, on sign-up, password change and reset. Only the first 5 characters of a SHA-1 hash of your password are sent (k-anonymity), never the password itself, the full hash or your email address. The request is made by our server, your IP address is not included. Legal basis: Art. 6(1)(f) GDPR (protecting your account) | Australia | The start of the hash identifies neither the password nor the person |
| Discord Inc. | Only if you voluntarily link your account with our Discord: our bot passes your plan role to Discord and, if you turn on the leaderboard, the number of your finished clips per month. If you submit a clip with the bot command /clip, our server receives your Discord ID, the clip link and, if you write one, your context for the clip from Discord (processed only for that clip, like in the web tool), and the bot sends you the status and a link to My clips by direct message. The clip itself is not uploaded to Discord. With /balance and /clips the bot shows you your balance, your plan and the status of your latest clips in a message only you can see; this information passes through Discord for that. If you use LazyClipper through the bot (watch a preview, change the section, create the text, post or schedule), a smaller preview of your clip, the texts, the names of your connected social accounts and the scheduled times pass through Discord for that. We create the preview only for that message and delete it on our side right away. In our Discord server the bot reads who reacted with 🏆 in the clip of the week vote, only to count the votes and leave out votes for your own clip. We don't store this | USA | EU-US Data Privacy Framework (adequacy decision) |
| PostPeer (Jonathan Geiger, postpeer.dev) | Only if you actively use it: publishing your clips to social media accounts you connected (TikTok, Instagram, YouTube). We show you the name and profile picture of the connected accounts in the settings; for this our server loads the profile picture from the platform and keeps it in memory for at most one hour. For the posting plan we store, for every post you publish or schedule through us, the clip, the text, the platforms, the time and the status. We delete these entries with your account. To post, we upload the finished clip to PostPeer, where it sits at an unguessable but publicly accessible address until PostPeer deletes it. We also pass on the text, the platforms and the time | Israel | Only after you explicitly connect your own account, can be disconnected at any time. An adequacy decision of the EU Commission applies to Israel. We have requested a data processing agreement from PostPeer |
4. Your rights
Access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20), objection (Art. 21). Right to lodge a complaint with a supervisory authority, e.g. the Berlin Commissioner for Data Protection and Freedom of Information. Write to us at datenschutz@lazyclipper.com.
Anything we do based on your consent (Discord link, training opt-in) you can withdraw at any time. What happened until then remains lawful.
You do not have to give us any data. Without an email address and password, however, we cannot create an account, and without a link or file we cannot edit a clip.
Under § 38 BDSG we are not required to appoint a data protection officer.
Right to object: Where we process data based on our legitimate interest (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation (Art. 21 GDPR). Write to datenschutz@lazyclipper.com.
5. Automated processing
Our service uses automated methods (speech recognition, image analysis, loudness analysis) to edit videos. There is no automated decision with legal or similarly significant effect (Art. 22 GDPR).
← Back