Privacy
Last updated
Glenn Rodgers trading as ClipLaunch, 22 Richmond Street, Barnstaple EX32 7DP · hello@cliplaunch.io
This policy explains what personal data ClipLaunch collects, why, who handles it for us, and your rights. We follow the UK GDPR and the Data Protection Act 2018. We don't sell your data, and we don't use it for advertising.
1. Who is responsible for your data
The controller is Glenn Rodgers, trading as ClipLaunch, 22 Richmond Street, Barnstaple EX32 7DP, United Kingdom. Write to hello@cliplaunch.io about anything in this policy.
2. What we collect, and why
- Your account: your email address and name, and your profile picture if you sign in with Google. We use it to sign you in, run your account and send you sign-in links and account emails. Basis: our contract with you.
- Sign-in records: your sessions with the IP address and browser they came from, your agent keys (stored only in a scrambled form) and the agents you connect. We use it to keep you signed in, let your agents act for you, and spot misuse. Basis: our contract with you, and our legitimate interest in keeping accounts safe.
- What you put in: uploads, screenshots, screen and camera recordings, brand kits, prompts, scripts, projects, and public web pages you ask us to capture. We use it to make what you ask for. Basis: our contract with you.
- What you make: images, videos, voices, music, transcripts, captions and renders. We use it to keep them for you until you delete them. Basis: our contract with you.
- Credits and billing: your credit ledger (what each action cost), your plan, your storage use and your auto top-up settings. Stripe holds your card, billing address and any tax ID; we never see your full card number. We use it to charge fairly, show your usage, give refunds, and keep the accounts and tax records the law requires. Basis: our contract with you, and our legal obligations.
- IP addresses on sign-in and other requests. We use it for rate limits and bot checks that stop abuse. Basis: our legitimate interest in keeping the service safe.
- What you write to us. We use it to answer you and act on reports. Basis: our legitimate interest in running the service, or a legal obligation for takedowns.
The studio records your screen, camera or microphone only when you start a recording. Page capture reads public pages only and never signs in to anything. We send no marketing emails.
3. Who handles it for us
These services process data for us, under contracts that limit what they may do with it:
- Vercel hosts the site and the studio, stores your files, runs the page capture service and the bot checks, and routes requests to AI models (AI Gateway). Where: United States.
- Neon runs our database: your account, sign-in sessions, agent keys and the credit ledger. Where: United Kingdom (London).
- Stripe takes payments and holds your card, billing address, any tax ID and your invoices. Where: United States.
- Resend sends sign-in links and account emails. Where: United States.
- Higgsfield generates images and video from your prompts and reference images. Where: United States. Higgsfield may use inputs and outputs to train its models.
- OpenAI, through Vercel AI Gateway transcribes audio, makes voice-overs, times the words in speech for captions, and checks shots and renders. Where: United States.
- Google Gemini makes music (Lyria) and the Kore voice, and suggests shorts, graphics, promo lines and brand kits. Where: United States.
- Deepgram transcribes your recordings for long-form editing. Where: United States.
Higgsfield may train its models on what is sent to it, under its own terms: your prompts, reference images and the images and videos it makes. Deleting a file in ClipLaunch deletes our copy. Copies Higgsfield keeps of what it generated are kept under Higgsfield's own terms, and may be used to train its models. If you'd rather something wasn't used this way, don't send it to image or video generation.
We opt every recording out of Deepgram's Model Improvement Program, so Deepgram doesn't train on your audio and keeps it only as long as it takes to transcribe it. The other services don't use your content to train their models under the terms we use them on.
If you sign in with Google, Google tells us your name, email address and profile picture, under Google's own privacy policy. When you connect an agent such as Claude or ChatGPT, it receives what you ask it to fetch, under its own provider's terms. We share data with others only when the law requires it.
4. Data sent outside the UK
Our database is in London, but the other services above are in the United States, so your data goes there too. This is what covers each transfer:
- Vercel: the UK-US data bridge (the UK Extension to the EU-US Data Privacy Framework).
- Stripe: the UK-US data bridge (the UK Extension to the EU-US Data Privacy Framework).
- Resend: the UK-US data bridge (the UK Extension to the EU-US Data Privacy Framework).
- Higgsfield: standard contractual clauses with the UK Addendum, which we are putting in place with them.
- OpenAI, through Vercel AI Gateway: the UK-US data bridge (the UK Extension to the EU-US Data Privacy Framework) to Vercel, and on from Vercel under its sub-processor terms, since it goes through Vercel AI Gateway.
- Google Gemini: the UK-US data bridge (the UK Extension to the EU-US Data Privacy Framework) for Lyria, which we call with our own key; the Kore voice and the text models go through Vercel AI Gateway, so they are covered by the data bridge to Vercel, and on from Vercel under its sub-processor terms.
- Deepgram: standard contractual clauses with the UK Addendum, which we are putting in place with them.
Write to us for a copy of the safeguards that apply.
5. How long we keep it
- Your account (your email address and name, and picture if you signed in with Google): until you delete your account. Deleting it also deletes your sign-in records and agent keys.
- Your files, brand kits, projects and finished videos: until you delete them or your account.
- The credit ledger: kept for the accounts, and anonymised when you delete your account, so nothing links it to you but the totals still add up.
- Payment and invoice records: 6 years, as UK tax law requires. Stripe keeps its own as well.
- Emails to hello@cliplaunch.io: up to 2 years after the last message.
- Server logs and the database's restore copy: deleted data can stay in server logs for up to 30 days and in the database's 6-hour restore window, then it's gone. Sign-in links and sessions expire on their own.
6. Your rights
You can ask us for a copy of your data, to correct it, to delete it, to limit how we use it, to object to how we use it, or to have it in a form you can take elsewhere. Your usage history downloads as a file from the Billing page, and you can delete your account in Settings. For anything else, write to hello@cliplaunch.io. We answer within a month.
If you're unhappy with how we handle your data, please tell us first. You can also complain to the Information Commissioner's Office, the UK regulator, at ico.org.uk.
8. Age
ClipLaunch is for people 18 or over. We don't knowingly collect data about anyone younger; if we find we have, we delete it.
9. Keeping it safe
Your files are private to your account, data travels encrypted, and agent keys are stored only in a scrambled form. Pages from other websites are captured by a separate service that holds none of our secrets. No system is perfectly safe; if a breach puts you at risk, we will tell you and the ICO as the law requires.
10. Changes to this policy
When this policy changes, the date at the top changes too. We email you at least 30 days before a change that affects existing users takes effect. A change needed for security or by law can take effect at once. The terms explain the rest of how ClipLaunch works.