Last updated 16 November 2026
Rippl is a tool that publishes one video to every social platform you connect, and turns long livestreams into short clips. This policy describes exactly what data that involves, where it goes, how long we keep it, and what you can do about it.
Rippl is an early-stage service run directly by its founders. The practices below describe the service as it actually works today, not as we intend it to work at scale.
Rippl is operated by its founders. For any privacy question, correction or deletion request, contact umutboi43@gmail.com. We aim to respond within 7 days.
| Data | Why we hold it |
|---|---|
| Your email address and an optional display name | To identify your account and contact you about the service. |
| Access credentials for platforms you connect — the OAuth refresh tokens and account identifiers issued by YouTube, TikTok and Instagram when you authorise Rippl | To publish on your behalf after you have left the page. Without a stored credential, a scheduled post could not run. |
| Videos you upload, and any video Rippl downloads from a link you supply | They are the input to the pipeline. |
| Audio derived from your video — extracted audio, the isolated vocal track, and the final mixed render | Intermediate and final products of the audio processing. |
| Processing metadata — detected tempo and mood, chosen backing track, timestamps, status, error messages, and the post identifier and link each platform returns | So you can see what happened to each post and we can diagnose failures. |
| Streams you ask us to clip — the stream link, its title, its audio, its public chat replay where the platform keeps one, a transcript of what is said, and the short clips we make | To find the best moments and render them as clips for you. |
| Credits and usage — top-up amounts, the Stripe reference for each payment, and the view counts we read for clips you post | To keep your credit balance and charge for views, as described on the pricing page. |
A session cookie (rippl_session), a random
value that keeps your browser signed in to your Rippl account |
Rippl has no passwords: this cookie is what tells us the browser is you. |
Audio separation and analysis for uploads run on our own servers using open-source models (Demucs for source separation, DeepFilterNet for noise reduction).
When you clip a stream, its speech is transcribed on our own servers (Whisper). To choose the clips and write their titles, captions and on-screen text, we send the transcript text, short excerpts of the stream's public chat, and the stream's title to Anthropic's Claude API. No video or audio is sent. Anthropic processes this under its commercial API terms and does not use it to train its models. Neither do we: your videos are not used to train any model.
We do not sell your data, and we do not share it for advertising. It reaches third parties only where that is the point of the feature:
| Recipient | What they receive | When |
|---|---|---|
| YouTube (Google) | Your rendered video, title and description | When you publish to YouTube |
| TikTok | Your rendered video and caption | When you publish to TikTok |
| Instagram (Meta) | A link to your rendered video, and the caption. Meta downloads the file from that link. The video is placed at a public web address on GitHub Pages for this, so anyone who has that address can view it. | When you publish to Instagram |
| Anthropic | Stream transcripts, chat excerpts and titles (no video or audio) | When you clip a stream |
| Stripe | Your payment, and what you enter on Stripe's checkout page | When you buy credits |
| YouTube, Twitch or Kick | A request for the stream you linked (we download it from there) | When you clip a stream |
| RapidAPI | The public link you asked Rippl to fetch | Only when you supply a TikTok or Instagram link to import |
| Vercel and ngrok | Network traffic between your browser and our server | Always, as our hosting and network providers |
Each platform handles the data it receives under its own privacy policy. Your use of YouTube through Rippl is also subject to the Google Privacy Policy and the YouTube Terms of Service.
Your data is held in a database and on disk on servers we control. Access credentials are stored so that scheduled publishing can run without you present; access to those servers is limited to the founders.
Being straight with you about early-stage security. Each browser has its own Rippl account, and only that browser's session cookie can reach its data. There are no passwords yet, so clearing your cookies or switching browsers starts a new, empty account. Platform credentials are not yet encrypted at rest. Please connect only accounts you are comfortable using with an early-stage service, and revoke access (see below) if you stop using it.
| Data | How long |
|---|---|
| A stream's audio | Deleted as soon as the clips from that stream are finished. |
| Stream video (the short sections downloaded to make each clip) | Deleted as soon as that clip is rendered. |
| Finished clips | 7 days, so you can post or download them; then deleted automatically. Clips you discard are deleted after 1 day. |
| Stream transcripts, chat replay and stream details | Until you delete your data. They make clipping the same stream again much faster. |
| Uploaded and rendered videos, and intermediate audio files | While your account is active, so you can see your post history. |
| Access credentials | Until you disconnect the platform or delete your data. |
| Processing metadata and post history | Until you delete your data. |
| Payment records (amounts and Stripe references) | As long as tax law requires us to keep financial records (six years in Canada), even if you delete your data. They are no longer linked to your email or name. |
If you are in the UK, EU or another region with statutory data rights, these apply to you regardless of this policy, and you may complain to your local data protection authority.
Rippl is not intended for anyone under 13, and we do not knowingly collect their data. If you believe a child has used Rippl, contact us and we will delete the account.
If this policy changes materially we will update the date above and notify invited users by email before the change takes effect.