RipClip
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 TikTok advertising with the TikTok Pixel, which loads only if you accept Marketing cookies (TikTok 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 #1197, Hendersonville, TN 37075, United States). For anything about your data, email [email protected]. We are the "controller" of the personal data described here.
RipClip runs on a server we operate in the United States, and visitors reach it through Cloudflare's network (see section 5). It is moving to a rented server from Hetzner in the European Union; when it does, and 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 |
| 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 |
| 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 SmartLink page (only if you turn it on) | The handle you choose and the posted clips you list on it. Visitors' views of the page are counted once each in our own database, with no cookie and nothing shared | To show a public page of your clips that you link from your bio; you can turn it off 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 |
| 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 join it) | Your email, whether you also asked for product news, which link brought you (for example a TikTok video), 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 join, and one launch announcement. Each email has an unsubscribe link that removes you, or ask us; the list is deleted once the launch emails are sent, except for people who asked for product news |
| 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), 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 |
| Advertising measurement (only if you accept Marketing cookies) | The TikTok Pixel on ripclip.org and app.ripclip.org tells TikTok which pages were viewed 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. Off unless you accept Marketing cookies; withdraw any time with Cookie settings (see "TikTok Pixel" in section 5) |
| Messages to us | Your name (optional), email and message from the Contact form | To answer you |
| 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 once 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 enter your card on Stripe's own page: your card details go straight to Stripe and we never see or store them. 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.
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 Pixel and its hashed-email matching, and an analytics cookie. 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 Pixel below, and only if you accept Marketing cookies. 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 and one welcome email with tips for getting started. 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.
- 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): only if you accept Marketing cookies. TikTok receives the page views and sign-up and purchase events described under "TikTok Pixel" below, and, only if you consented, a hashed email address (TikTok's privacy policy).
- Resend: if you join the waitlist, 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: if you subscribe or start the free trial, as our payment processor. It receives your email address and the card and billing details you enter on its page, and tells us your plan and whether a payment went through (Stripe's privacy policy).
- Cloudflare: every visit to RipClip passes through Cloudflare's network, which protects the site and delivers it, so Cloudflare sees your IP address and browser details. Cloudflare R2 serves our public landing videos and stores our nightly backup of RipClip's data in a private storage bucket (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).
- 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. It is off by default. It loads on ripclip.org and app.ripclip.org only after you accept the Marketing category in the cookie banner; the essential cookies stay on either way. Once it loads, TikTok receives which pages you view, 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, 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.
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; we set a cookie for that only if you have given analytics consent. 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 [email protected].
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.
- Contact messages: up to 12 months.
- 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 Pixel and the analytics cookie 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" or "share" personal information as California law defines those words.
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 [email protected].
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 TikTok Pixel's cookies (Marketing) and an analytics cookie are set only if you accept them in the cookie banner. 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 (October 6, 2026): we added what we keep and show publicly when you share an editing preset (see "Shared presets" in section 2). If you never share one, nothing changed for you.