Privacy Policy
RipClip turns your videos into short clips. To do that we have to store your account, the videos you upload and the clips we make. This page explains exactly what we keep, why, and how you can get a copy or delete it. We don't sell your data and we don't show ads. We do two kinds of measuring, both explained below: we record how RipClip is used in our own database, with no outside analytics tool (how RipClip is used), and we measure our own advertising on TikTok, Facebook and Instagram with the TikTok and Meta pixels, which in the US load until you opt out and everywhere else only if you accept Marketing cookies (TikTok Pixel, Meta Pixel). You can choose to share how you use the app for learning (an unticked box at sign-up, and in Settings any time).
1. Who we are
RipClip is run by RipClip (1012 Glenbrook Way PMB 1197, Hendersonville, TN 37075, United States). For anything about your data, email support@ripclip.org. We are the "controller" of the personal data described here.
RipClip runs on a server we rent from Hetzner Online GmbH in its data center in Helsinki, Finland (European Union), and visitors reach it directly. Your account, uploads, projects and clips are stored on that server. Whenever we move it, we'll name the new host and where it is on this page.
2. What we collect
| What | Examples | Why |
|---|---|---|
| Account | Email, display name, username, a salted hash of your password (never the password itself), the date you joined, whether your email is verified, your consent choices | To create your account, sign you in and keep it secure |
| Google sign-in (only if you use it) | Your Google email, name and account ID, sent to us by Google | To sign you in without a password |
| What you upload | Videos, links you paste (such as Kick clips), images, fonts and music | To make, edit and export your clips |
| The "RipClip it" browser extension (only if you install it) | Nothing while you browse: the extension keeps no record of the pages you visit, has no account access and sends nothing on its own. When you press its button on a Twitch or Kick video, your browser opens RipClip with that video's link, which is then handled like any link you paste | To bring that video into RipClip when you ask |
| What we make from it | Transcripts of the speech in your videos, caption timing, clip suggestions, projects, edits and exported clips | That is the service |
| Training our speech-to-text (unless you turn it off) | The speech audio of your videos and its transcripts | To train RipClip's own speech-to-text model, so transcripts get better and RipClip needs fewer outside services. The model learns to turn speech into words; it does not keep or show your videos to anyone. Turn it off any time in Account settings ("Use my videos' speech to train RipClip's speech-to-text"); from then on your videos are left out of the next training. Deleting a video or your account removes it from future training too |
| Posts and connected accounts (only if you use them) | Captions and times of posts you plan, and access tokens for the Instagram, Facebook, Threads, TikTok, YouTube, X or Bluesky accounts you connect (stored encrypted; for Bluesky, the app password you create for RipClip, sealed the same way), and the posting presets you save | To schedule and publish posts you ask us to publish |
| Your public profile | Your display name, username, the month you joined, the bio and links you add, and only the clips you put on it (or that RipClip posted publicly for you, which you can switch off). Visitors' views and plays are counted in our own database under the cookie choice they made | To show a public page of your clips that you link from your bio; you take a clip off, or change the rest, at any time on the Accounts page |
| TikTok profile and statistics (only if you connect TikTok) | Your TikTok display name, username, profile picture, bio, profile link, whether the account is verified, and its follower, following, like and video counts, with one snapshot of the counts per day for the last 90 days | To show your account and its growth on your Accounts and Analytics pages. Shown only to you, never sold or shared, and deleted when you disconnect TikTok or delete your RipClip account |
| YouTube channel statistics (only if you connect YouTube) | Your channel's description, profile link, and its subscriber, total view and video counts, read through the YouTube API Services, with one snapshot of the counts per day for the last 90 days | To show your channel and its growth on your Accounts and Analytics pages. Shown only to you, never sold or shared, and deleted when you disconnect YouTube, when you remove RipClip's access in your Google account (we check once a day), or when you delete your RipClip account |
| Facebook, Instagram, Threads, YouTube and X details (only if you connect them) | For each account you connect: its name, username, ID and profile picture; the video, caption and time of the posts RipClip publishes for you; and, to show how a post is doing, its counts (views, likes, comments, shares, saves, reach), read from the platform for the posts RipClip published. For Facebook, the list of Pages you manage; for YouTube, your channel's name, handle and picture. We do not read your messages, your followers' details, your other posts or videos, or anything about other people | To publish and schedule the posts you ask for and to show their results on your Analytics page. Shown only to you, never sold or shared, and deleted when you disconnect the account or delete your RipClip account (see "Google and YouTube" and "Delete your data" below) |
| Shared presets (only if you share one) | The editing preset you share, its name and category, a short preview made from your own clip (up to 10 seconds, no sound), your username, and how many people used and liked it. Likes and reports you make on other people's presets are kept with your account | To show the preset in RipClip's Community, where every RipClip user can see it with your username and its preview. You can unshare it at any time; deleting your account removes your shared presets, likes and reports |
| Waitlist (only if you joined it; it closed on November 4, 2026, when RipClip opened) | Your email, whether you also asked for product news, which link brought you (for example a TikTok video, or an ad's campaign, ad set and ad), and a one-way code made from your IP address to stop spam sign-ups | To send you one welcome email with a discount code when you joined, and one launch announcement, which has been sent. Each email has an unsubscribe link that removes you, or ask us. With the launch emails sent, the list is deleted, except for people who asked for product news and, until their free month is applied, people who earned a referral reward |
| A stream link for free clips (only if you send one on ripclip.org) | The Kick or Twitch link you paste next to your email, the time, and a one-way code made from your IP address to limit requests | To make 3 clips from that stream and email them to you. Only we see it. Ask us and we delete it |
| How you use RipClip (product analytics) | Events tied to your account: you signed up, projects you created, renders, exports and posts, plan and billing events (a plan started, changed or cancelled, Horizon Units used, whether a payment went through), a developer key or AI connection made or revoked, which tool an assistant called and whether it worked (never what it asked or got back), how well a transcript came out (an average confidence score and a word count, never the words), visits to the address a free-plan watermark can show (counted once each, with no cookie), and errors. Page views on our public pages (ripclip.org and the signed-out app pages) are counted anonymously, without a cookie, and with a cookie only if you gave analytics consent. Kept in our own database; no outside analytics service receives it | To improve the product, keep it reliable, keep billing records and report on the business. Kept 25 months, then only totals are kept. Included in "Download my data" and deleted with your account |
| Your answers to our questions (only if you answer) | RipClip may ask, rarely and in the app, how likely you are to recommend it (0 to 10), how an export went (1 to 5), and, if you cancel a paid plan, why. Every question can be dismissed. We keep your score, the reason you pick, any words you choose to type, and the date, with your account | To improve RipClip and understand why people leave. Never shared outside RipClip, and the words are read without your name next to them. Kept 25 months. Included in "Download my data" and deleted with your account |
| Invite links (only if you use one) | The code of your own invite link; and, for an account made through someone's link, a note of which link it came from. The person who invited only sees how many friends joined, not who. The link gives neither of you anything | To count how invite links are used. Included in "Download my data" and deleted with your account |
| Team workspaces (only if you invite someone or accept an invite) | For a Studio owner: the email addresses they invite, when each invite was made and expires, who joined and when, and whether each member may post. For a member: which teams they are in, when they joined, and which workspace they last picked (a cookie). The owner sees each member's name and email; a member sees the owner's name. Everything in the owner's workspace (projects, clips, uploads, presets, templates, brand kit, posts and the names of connected accounts) is shown to its members; a member's own workspace is never shown to the owner, and nobody in a team sees anyone's password, payment details or social sign-ins. Work done in the team counts as the owner's in our usage records | To let a team work in one workspace on the owner's plan (Terms). Pending invites are deleted after 7 days; the rest is kept while the person is in the team, included in "Download my data" and deleted when they leave, are removed, or delete their account. Deleting the owner's account ends the team |
| Suggestions and bug reports (only if you send one) | What you write, a screenshot if you attach one, and the item's status. Only if you tick "Attach details" on a bug report: the page you were on, your browser and device type, the screen size, the app version, your plan and up to 10 recent error messages from the app (no file names or video content) | To review it, build or fix it, and credit you if we do (Terms). Only RipClip's owner sees it. Included in "Download my data"; the screenshot is listed with your uploaded files; all of it is deleted with your account |
| Preset share links (only if you make one) | A link code for a preset you share by link. Anyone who has the link and a RipClip account can add a copy of the preset's look and settings (not your logo, music, overlays or uploaded fonts) to their own account. This is separate from sharing to the public gallery above | To let you pass a preset to someone. Kept until you delete your account; a link stops working when you delete the preset |
| AI assistants and developer keys (only if you use them) | For each developer key you make: its name, what it may do, your monthly Horizon Unit limit, when it was made and last used, and a one-way code of the key (never the key itself, which is shown to you once). For each AI assistant you connect: the name and callback address the assistant gave when it registered (or that its company publishes at its own web address, which we read once an hour at most and which carries nothing about you), a general label for which assistant it is (for example Claude or ChatGPT), what you allowed, your monthly limit, the time you agreed, and one-way codes of the short-lived passes it holds. We count the Horizon Units each key or connection used. When an assistant reads or changes your RipClip data it does so under your account and your limit; we keep a record that a tool was called and whether it worked, not what was asked or returned | To let you use RipClip from an AI assistant or your own program, keep it within the limit you set, and let you see and cut off every connection on Account > Connect to AI. Shown only to you and never sold. A revoked key or connection stops working at once; its passes are deleted after they expire (90 days at the latest) and its record is deleted with your RipClip account |
| Advertising measurement (Marketing cookies) | The TikTok Pixel on ripclip.org tells TikTok which pages were viewed, how they were used (clicks, time on the page, page load speed) and when someone signs up or buys a plan. If you also consented, your email address, hashed (turned into a one-way code) before it leaves your browser, is sent so TikTok can match the event to an ad | To measure whether our TikTok ads work. In the US on until you opt out, elsewhere off unless you accept Marketing cookies; withdraw any time with Cookie settings (see "TikTok Pixel" in section 5) |
| Meta advertising (Marketing cookies) | The Meta Pixel on ripclip.org, and our server with the same events, tell Meta when a page is viewed, when you open the sign-up form, pick a plan, press Get clips, open the Help chat, make an account, open the payment page, start a free trial or pay for a plan (with the plan's price), with your browser details, your IP address, Meta's cookies and, for those sign-up and plan events, your email address and RipClip account ID as one-way codes (SHA-256 hashes). With your account we keep Meta's browser and ad-click IDs, your browser's name and version, and which conversions your browser still has to report, only while Marketing is on | To measure our Facebook and Instagram ads and help Meta show them to people likely to want RipClip. In the US on until you opt out, elsewhere off unless you accept Marketing cookies; when you switch it off we stop sending and delete the Meta identifiers we kept (see "Meta Pixel" in section 5) |
| The ad or link that brought you (with analytics consent, or from the link itself) | The campaign tags of the link you first arrived from (source, medium, campaign, ad set and ad), the referring site and the page you landed on, kept with your account (or with your waitlist sign-up, if you joined before it closed) | To see which of our ads and posts bring people who sign up, start a trial and pay, and what each costs us. Never shared outside RipClip. Included in "Download my data" and deleted with your account |
| Messages to us | Your name (optional), email and message from the Contact form | To answer you |
| The chat bot for Twitch and Kick (only if a streamer turns it on) | For the streamer: which Twitch or Kick channel you connected (its ID and name), your chat bot settings and monthly Horizon Unit limit, and for Kick the sign-in pass Kick gives us for your channel, stored encrypted. For people chatting in that channel: while the bot is on, Twitch and Kick send us the channel's chat messages so we can spot the !clip command. We keep only messages that are that command: the time, up to 80 characters of the words typed after it, and a one-way code made from the sender's ID (never the name or the ID itself). Every other chat message is dropped the moment it arrives; it is not stored, logged or read by anyone. We also keep when each marked stream started and ended | To mark the moments chat asked for, limit how often one person can mark, reply once in chat, and clip those moments for the streamer after the stream. Not used for advertising and never sold. Turning the bot off stops Twitch and Kick sending us the chat; disconnecting the channel deletes its marks |
| The Help chat (only if you use it) | The questions you type into the Help bubble and its answers, the pages each answer came from, whether you marked an answer helpful, and your account if you are signed in. Before anything is stored we remove what looks like a password, card number, code or key. To answer, our AI model reads RipClip's own help pages and, if you are signed in, your plan, Horizon Units left and your latest jobs. It runs on RipClip's own server: your questions are not sent to any other company. If you press Email support and then Send, the conversation and the email address you give go to our support inbox | To answer your question, and so RipClip's owner can see which questions the help pages don't answer yet and improve them. Not used to train any model. Included in "Download my data" and deleted with your account |
| Technical data | Your IP address, kept in memory for a few minutes to limit repeated sign-in attempts; if you try RipClip without an account, a one-way code made from your IP address (not the address itself), kept with that trial; server error logs | Security, limiting free tries, and fixing problems |
| Abuse prevention (free credits and the free trial) | A random device ID kept in a cookie and in your browser's storage on this device; your email in a standard form (for example without dots or "+" tags in a Gmail address), kept with your account. When you confirm your email we keep one-way codes made from the device ID, that email form, your IP address and its network, and your browser's type and language (not the values themselves) with a note of whether the free credits were given. If you start the free trial, a one-way code made from the card identifier Stripe gives us (never the card number), and whether it is a prepaid card or failed its security-code check; the same one-way device and email codes are also kept to hold the trial to one per device and email | To give the free credits (and their monthly top-up) to one account per person and the free trial once per card, device and email. The IP and browser codes are cleared after 7 days. The device, email and card codes are kept after you delete your account, so deleting and signing up again doesn't refill the free credits; they can't be turned back into your details. Nobody is refused an account or a paid plan because of them |
We only ask for what we need. Your name is optional, we don't ask for your phone number, birthday, gender or address. If you subscribe or start the free trial, you pay on the checkout page of Link, the Stripe service that sells the plan for us: your card details go straight to Link and Stripe and we never see or store them. That page asks for your billing address (to work out tax) and may ask for a phone number; those go to Link, not to us. We keep your Stripe customer and subscription IDs and your plan.
3. Speech recognition and clip picking
If you enable “Improve clip suggestions” on the Accounts page, we keep separate learning evidence: source time ranges you choose, edit versions, publication identifiers and performance observations. We do not copy uploaded video bytes or caption text into that store. Counts you enter yourself are labelled user-reported; missing counts remain unknown. These records are for future research, not automatic model training. The option is off by default. Turning it off deletes your learning records without deleting your projects or posts; account deletion also removes them. A future training release will need an updated explanation and consent covering its use.
Faces. Auto-reframe looks for faces in a clip only to frame it (to centre the crop on the speaker, or to find a streamer's facecam). It detects that a face is there and where; it does not recognise or identify anyone, does not compare faces, and does not make or keep face templates, face prints or face images. The only thing kept is the crop position the clip's style then uses.
Transcripts are made by ElevenLabs Scribe, a speech-to-text service run by ElevenLabs. To make one, we send it the audio of your video (the speech track only, not the picture) and it sends back the words with their timing. If Scribe can't be reached, or its result looks incomplete, we make the transcript on RipClip's own machine with the Whisper model instead, and then your audio isn't sent to anyone. ElevenLabs handles the audio under its own terms and privacy policy and may keep it for a limited time; we don't use ElevenLabs' zero-retention option today. The same goes for text to speech: when you ask the editor to read a text box out loud, we send that text to ElevenLabs, which sends back the voice recording; if it can't be reached, a voice on RipClip's own machine reads it instead and the text isn't sent to anyone. Don't upload recordings that contain things you wouldn't want a speech-to-text service to process (for example health or payment details). Our clip model, Riptide, ranks moments inside your video. We don't use your uploads, transcripts or clips to train Riptide. If that ever changes, we'll ask first and it will be optional. Since November 19, 2026 we use the speech audio of your videos and its transcripts to train RipClip's own speech-to-text model, unless you turn that off in Account settings (see the table above).
4. Why we're allowed to use it
- To provide the service you asked for (contract): your account, uploads, clips and posts.
- Legitimate interests: keeping RipClip secure, fixing errors, preventing abuse of the free credits and the free trial, and improving the product from how it is used in our own database (how RipClip is used).
- Consent: optional product news emails, loading Google's sign-in script before you click it, the TikTok and Meta pixels, the server copy of the Meta events and their hashed-email matching, and analytics cookies. You can withdraw consent at any time.
- Legal obligations: for example tax records for payments.
5. Who we share it with
We don't sell or rent your personal data. The only sharing connected to advertising is the TikTok and Meta pixels below, with Marketing cookies on (in the US until you opt out, elsewhere only if you accept them). Your data otherwise goes only to these services, and only when needed:
- Google: if you choose "Continue with Google", to confirm who you are (Google's privacy policy).
- Instagram / Facebook / Threads (Meta), TikTok, YouTube (Google), X and Bluesky: only for accounts you connect, to publish the posts you schedule and read their statistics. For Bluesky we use an app password you create for RipClip in Bluesky's settings, never your account password, and read only your profile and the likes, replies, reposts and bookmarks of the posts RipClip published. What each one gives us, and what it can do, is listed under "Facebook, Instagram, Threads, YouTube and X details" in section 2; for YouTube see Google and YouTube below. We never receive your password for any of them. Threads collects the video itself, and Instagram a cover picture you upload, from a private one-time link that stops working as soon as the post is published. A cover picture you upload is stored with your account, redrawn without its hidden details (such as the camera or the place it was taken), and sent only to the networks you post it to. Each platform's own privacy policy applies to what you post there.
- Our email provider: to deliver your sign-in codes, one welcome email with tips for getting started, and notices about your plan changing (for example the day before a free trial ends). If you choose "Email me when my clips are ready", it also delivers one short email each time your clips finish while RipClip isn't open, with the video's name and a link to the clips. Turn it off in Account settings or with the link in the email. When a Studio owner invites your address to their team, it delivers one invite email with the owner's name and a link (it isn't marketing, and nothing happens unless you accept). If you asked for product news, we may also send one reminder email around day 3 of a free trial, with the date the trial ends and an unsubscribe link.
- Twitch and Kick (the chat bot): only for a channel whose streamer connected it and turned the chat bot on. We send them the bot's short reply for the chat ("Marked! RipClip will clip it after the stream."), and ask them whether the channel is live and where the stream's video is. They send us the channel's chat and when a stream starts and ends, as described under "The chat bot for Twitch and Kick" above.
- ElevenLabs: to turn the speech in your videos into text, as our processor. It receives the audio track of the video you transcribe and returns the words and their timing. For text to speech it receives the text you type into a text box and returns a voice recording (ElevenLabs' privacy policy). Without it (or when it can't be reached) the transcript and the voice are made on our own machine.
- TikTok (advertising Pixel): with Marketing cookies on (see above). TikTok receives the page views, clicks and sign-up and purchase events described under "TikTok Pixel" below, and, only if you consented, a hashed email address (TikTok's privacy policy).
- Meta (advertising Pixel and Conversions API): with Marketing cookies on (see above). Meta receives the page view, sign-up, plan, Get clips, Help chat, account, checkout, trial and payment events described under "Meta Pixel" below, from your browser and from our server, with hashed email and account IDs (Meta's Privacy Policy).
- Resend: if you joined the waitlist (it closed on November 4, 2026), it delivers the waitlist emails for us, as our processor. It receives your email address and the email's content (Resend's privacy policy).
- Stripe and Link: if you subscribe or start the free trial. Link, a Stripe service, sells the plan to you as the merchant of record. It receives your email address and what you enter on its checkout page (name, card, billing address, a phone number if you give one) and uses them to take the payment, work out and pay sales tax or VAT, send receipts, prevent fraud and answer payment questions, as its own controller under Link's privacy policy and Stripe's privacy policy. It tells us your plan and whether a payment went through.
- Cloudflare: Cloudflare R2 serves our public landing videos from media.ripclip.org, so Cloudflare sees your IP address and browser details when your browser loads one. R2 also stores, in a private storage bucket, our nightly backup of RipClip's data and the videos you uploaded but haven't opened for 30 days (they come back to our server the moment you open them, and deleting the video or your account deletes this copy too) (Cloudflare's privacy policy).
- Neon: Neon hosts the database that runs our job queue and counts Horizon Unit use. It holds your account ID, the details of each job you start (such as the link or file name and your settings) and the units it used, not your videos or clips (Neon's privacy policy).
- Kick and Twitch: when you paste a Kick or Twitch link, we download that public video from the site.
- Google Drive, Dropbox and OneDrive: when you paste a shared link to a file there, our server downloads that file. The service sees our server's request, not you.
- Apple Podcasts: when you paste an Apple Podcasts episode link, we ask Apple's public podcast directory for that episode (Apple receives the show's and episode's numbers from the link, and our server's address, not yours), then download the episode from the podcast's own host.
- Pixabay: when you use the "Stock library" in the editor, our server sends Pixabay the words you search for (you can pick them from your clip's transcript) and the category you open, and downloads the stock video you choose. Pixabay doesn't receive your account or your video. When you hold the pointer on (or press and hold) a stock video to preview it, your browser plays that short preview straight from Pixabay's servers, so Pixabay sees your IP address and browser for that request (Pixabay's privacy policy).
- Openverse, Jamendo, Freesound and Wikimedia Commons: when you use the "Music library" in the editor, our server sends Openverse the words you search for and the category you open, and downloads the song you choose from the site that hosts it (Jamendo, Freesound or Wikimedia Commons). They don't receive your account or your video. When you play a song's preview, your browser streams it straight from that site, so it sees your IP address and browser for that request (Jamendo's, Freesound's and Wikimedia's privacy policies).
- Cloudflare Turnstile: if we switch it on, the email sign-up form shows Cloudflare's check that you're a person. Cloudflare receives your IP address and browser details for that check (Turnstile's privacy policy).
- The AI assistant or program you connect (for example Claude, ChatGPT or Cursor): only if you connect one, and only what you ask it to do. Its answers can include your project names, your clips' titles and times, job progress, a private download link for a clip that stops working after five minutes, and links to a RipClip page that shows a project's or clip's details only to you when you are signed in. It cannot post to your social accounts or read your connected-account sign-ins. The assistant's own company handles what it receives under its own privacy policy, so connect only assistants you trust, and disconnect one any time on Account > Connect to AI.
- Authorities: only if the law requires it.
The full list of outside code and services RipClip uses is on the Credits page.
TikTok Pixel
The TikTok Pixel is a small script from TikTok that we use to measure our own TikTok ads. Outside the US it is off by default and loads on ripclip.org only after you accept the Marketing category in the cookie banner; in the US it loads until you opt out (see Do not sell or share). The essential cookies stay on either way. Once it loads, TikTok receives which pages you view, how you use them (clicks and buttons pressed, time on the page, the page's title and description tags, and how fast it loads), and when you sign up or buy a plan (the sign-up and purchase events), with your browser details, your IP address and the cookies listed on the Cookie Policy. If you also consented, we send your email address hashed (turned into a one-way code in your browser) so TikTok can match the event to an ad; this is used only for matching. The purpose is measuring our ads and helping TikTok show them to people likely to want RipClip, not showing you ads inside RipClip. TikTok handles this data under its own privacy policy, linked above.
To withdraw consent, press Cookie settings at the bottom of any page and choose Essential only. The Pixel then stops loading and we stop sending events. TikTok keeps what it already received under its own policy; to ask TikTok to delete it, use TikTok's own privacy tools.
Meta Pixel
The Meta Pixel is a small script from Meta that we use to measure our own Facebook and Instagram ads and to help Meta show them to people likely to want RipClip. Outside the US it is off by default and loads on ripclip.org only after you accept the Marketing category with the Meta Pixel named in the banner; in the US it loads until you opt out (see Do not sell or share). It reports page views and these moments: opening the sign-up form, picking a plan, pressing Get clips, opening the Help chat, making an account, opening the payment page, starting a free trial and paying for a plan (with the plan's price in US dollars). Because ad blockers often stop the script, our server sends Meta the same events with the same event ID (Meta's Conversions API) and Meta counts each pair once; the server copy is sent only while your Marketing choice is on. Meta receives your browser details, your IP address, its cookies (listed on the Cookie Policy) and, for the account, trial and plan events, your email address and RipClip account ID turned into one-way codes (SHA-256 hashes) before they leave our server. Meta handles this data under its own privacy policy, linked above. We never send what you upload, your clips, captions, posts or connected accounts.
To withdraw consent, press Cookie settings and choose Essential only. The Pixel stops loading, our server stops sending, and we delete the Meta identifiers kept with your account. Meta keeps what it already received under its own policy; use Meta's own privacy tools to ask it to delete that.
How RipClip is used (product analytics)
RipClip records how the product is used in its own database; no outside analytics service is involved and nothing goes to an advertising network. We record: that you signed up, the projects you create, renders, exports and posts, plan and billing events (a plan started, changed or cancelled, Horizon Units used, whether a payment went through) and errors, each tied to your account. On our public pages (ripclip.org and the signed-out app pages) we count page views anonymously, without a cookie, each with where that visit came from (the referring site's name, the link's campaign tags and the landing page; not after you choose "Essential only"); we set a cookie for that only if you have given analytics consent. Our server looks up which country your IP address belongs to in a free country database it keeps itself (IP Geolocation by DB-IP), to start the cookie banner with the right default for where you are (in the EU, EEA, UK and Switzerland, or when the country is unknown, analytics starts off) and to count visits by country. Only the country is kept, never the IP address, and no other company is asked. We do this to improve the product, keep it reliable, keep billing records and report on the business. Usage records are kept for 25 months, after which only totals (no account) are kept. They are part of "Download my data" and are deleted with your account.
Google and YouTube
RipClip uses YouTube API Services to post your clips to your YouTube channel as Shorts and to show how they do. By connecting YouTube you also agree to be bound by the YouTube Terms of Service, and Google's handling of your data is described in the Google Privacy Policy. When you connect, Google asks you to allow two things, and RipClip asks for nothing else:
- Upload videos to your YouTube account (
youtube.upload): so RipClip can upload the clip you choose, with the title, description and visibility you choose, and nothing else. - View your YouTube account (
youtube.readonly): so RipClip can show which channel is connected (its name, handle and picture) and read the view, like and comment counts of the videos RipClip uploaded, for your Analytics page.
We use this data only to provide those two features to you, shown only to you. We do not sell it, do not use it for advertising or to build profiles, do not use it to train any model or add it to the "Improve clip suggestions" learning records, do not share it with anyone but you (and the YouTube API itself), and do not let people at RipClip read it except with your permission, to look into abuse or a security problem, to follow the law, or in aggregate form to run the service. Your sign-in is stored encrypted and the YouTube counts are kept with the post they belong to. RipClip'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.
You can end this at any time, in either place: press Disconnect on RipClip's Accounts page, which revokes RipClip's access with Google at once and deletes the YouTube counts we read; or remove RipClip at security.google.com/settings/security/permissions, and we delete the YouTube data we hold for you within 30 days. Deleting data on RipClip does not delete your videos on YouTube; delete those on YouTube. Questions or complaints about your privacy: email support@ripclip.org.
6. How long we keep it
- Trying RipClip without an account: the video you add and everything you make from it are kept for 24 hours, then deleted automatically. If you create an account within that time, they move into your account instead.
- Clips in your Library: 10 days, then deleted automatically.
- Projects, uploads, presets and templates: until you delete them or your account.
- Your account: until you delete it. Deleting your account removes everything listed in section 2 within 30 days (backups included), except the one-way abuse-prevention codes, which can't identify you.
- Abuse-prevention codes: the IP, network and browser codes for 7 days; the device, email and card codes for as long as RipClip offers free credits and free trials.
- Usage records (product analytics): 25 months, then only totals without an account are kept.
- Your answers to our questions, with any words you typed: 25 months, then deleted.
- Developer keys: until you revoke them or they run out. A connected AI assistant stays connected, with its details and usage, until you disconnect it or delete your account, and it ends on its own after 90 days without use (it is used when it renews its pass). Its passes last 15 minutes, with a renewal pass that lasts 90 days; a used renewal pass is kept until it runs out so a stolen copy can be spotted. A connection that ends stays in your account's history, hidden from the Connect to AI page 30 days after it ends, until you delete your account. Requests to connect that you don't finish are deleted after 10 minutes, and assistants that register but are never connected after 24 hours.
- Chat bot marks (the !clip commands from a connected Twitch or Kick chat): 90 days after the stream, then deleted; at once when the streamer disconnects the channel or deletes their account.
- Contact messages: up to 12 months.
- Help chat conversations: 180 days from the last question, then deleted (or sooner, with your account).
- Sign-in attempt limits: a few minutes, in memory only.
7. Your choices and rights
In Account settings you can, at any time:
- Download your data: a file with your account details, projects, clips list, posts, connected accounts and your usage records.
- Take back marketing or analytics consent with the Cookie settings link at the bottom of any page: the TikTok and Meta pixels, the server copy of the Meta events and the analytics cookies then stop.
- Delete your account: removes your account and everything you made, straight away.
- Disconnect a connected account on the Accounts page: deletes the stored sign-in and what we read from it, and tells TikTok, YouTube and X to end RipClip's access (for Bluesky it ends RipClip's session; also delete the RipClip app password in Bluesky). Facebook, Instagram and Threads have no such call, so also remove RipClip in their settings. Step by step for every platform, and how to ask us to delete your data by email: Delete your data.
- Turn product news emails on or off. Every product email also has an unsubscribe link. Sign-in codes are always sent, because you need them to use your account.
Depending on where you live (for example the EU, UK or California) you also have the right to correct your data, object to or restrict how we use it, and complain to your data protection authority. Email us to use any of these rights; we reply within 30 days. We won't treat you differently for using them. We don't sell personal information.
Do not sell or share my info. What the TikTok and Meta pixels (and our server's copy of the Meta events) send may count as "sharing" for cross-context behavioral advertising under California and other US state laws. In the US they are on until you opt out: press Do not sell or share my info at the bottom of any page and switch Marketing off, or choose Essential only in the cookie banner. Everywhere else it happens only after your yes, and you can withdraw it at any time with Cookie settings. We honor the Global Privacy Control signal: with it on, no advertising pixel loads and nothing is sent to TikTok or Meta, whatever you chose in the banner.
8. Children
You must be at least 13 to use RipClip, and at least 16 in the EU and the UK. We ask you to confirm your age when you sign up. If you're under 18, please use RipClip with a parent's or guardian's permission. If we learn we have data from a child under these ages, we delete it. Parents can reach us at support@ripclip.org.
9. Security
Passwords are stored only as salted PBKDF2 hashes, sessions are signed and marked HttpOnly, access tokens for connected social accounts are encrypted, and every request is checked against the account that owns the data. All traffic uses HTTPS. No system is perfectly secure; if a breach affects you, we'll tell you and the authorities as the law requires.
10. Cookies
We always use the cookies that are needed to keep you signed in and to stop the free credits being claimed twice (a random device ID). The analytics cookies, and outside the US the TikTok and Meta pixels' cookies (Marketing), are set only if you accept them in the cookie banner; in the US Marketing is on until you opt out. See the Cookie Policy for the full list, and the cookie settings link at the bottom of every page to change your choice.
11. Changes
If we change this policy in a way that matters, we'll tell you in the app or by email before it takes effect. The date at the top shows the current version.
Latest change (November 19, 2026): a streamer can connect a Twitch or Kick channel to RipClip's chat bot; what it keeps (only the !clip command, with a one-way code instead of the sender) is under The chat bot for Twitch and Kick. The change before (November 16, 2026): our email provider also delivers notices about your plan changing, such as one email the day before a free trial ends. The change before (November 10, 2026): the waitlist closed on November 4, 2026, when RipClip opened, so joining it is no longer something Meta is told about; what we keep for people who joined is unchanged. The change before (November 9, 2026): in the United States the advertising pixels (Marketing) are now on until you opt out, with a "Do not sell or share my info" link at the bottom of every page (see Do not sell or share); everywhere else they stay off until you accept them, and Global Privacy Control still turns them off. Meta now also receives these moments: opening the sign-up form, picking a plan, pressing Get clips, opening the Help chat and opening the payment page. The change before (November 6, 2026): we now look up your country from your IP address on our own server, with DB-IP's free country database, because visits no longer pass through Cloudflare's network, which used to tell us the country (see product analytics). Only the country is kept. Since November 3, 2026, visits reach our server directly; Cloudflare now only serves our landing videos and stores our backups (see "Cloudflare" in section 5). The change before (November 4, 2026): uploaded videos you haven't opened for 30 days are stored in Cloudflare R2's private storage instead of on our server until you open them again (see "Cloudflare" in section 5). How long we keep them did not change. The change before (November 3, 2026): we added what we keep when you use the Help chat (see "The Help chat" in section 2 and how long we keep it). Its AI runs on our own server, so your questions go to no other company. If you don't use it, nothing changed for you. The change before (October 26, 2026): we added the Meta Pixel and the server copy of its events (Meta's Conversions API), both only with Marketing consent (see "Meta advertising" in section 2 and "Meta Pixel" in section 5); we now keep the campaign tags of the ad or link that brought you with your account and waitlist sign-up; we explain how advertising pixels relate to California's "sharing" and that we honor Global Privacy Control. If you never accept Marketing cookies, nothing goes to Meta. The change before (October 20, 2026): we added what we keep, and who in a team sees what, when a Studio owner invites people to their workspace (see "Team workspaces" in section 2); we also email an invite to the address the owner typed. If you never invite anyone or accept an invite, nothing changed for you. The change before (October 18, 2026): we added what we keep when you send a suggestion or a bug report (see "Suggestions and bug reports" in section 2). If you send none, nothing changed for you. The one before that (October 16, 2026): we added what we keep when you answer the optional questions RipClip may ask in the app (and the reason you give when you cancel), when you use an invite link, and when you share a preset by link (see "Your answers to our questions", "Invite links" and "Preset share links" in section 2); how well a transcript came out and visits to the watermark address now count as usage records; and RipClip may send one trial reminder email to people who asked for product news (see section 5). If you do none of these, nothing changed for you. The change before (October 15, 2026): nothing about what we collect. The Terms now say the free plan's credits come every month; the abuse-prevention codes above are kept for as long as RipClip offers free credits, as before. The change before (October 13, 2026): we added what we keep when you connect an AI assistant or make a developer key, and what the assistant receives (see "AI assistants and developer keys" in section 2 and section 5), and how long a connection lasts (until you disconnect it, or 90 days without use; see how long we keep it). If you never connect one, nothing changed for you. The change before (October 6, 2026) added what we keep and show publicly when you share an editing preset.