Privacy policy
Last updated: 18 October 2026
This policy explains what data iaclips (iaclips.ai) collects, what it’s used for, who it’s shared with, how long it’s kept, and how you can ask us to delete it. Your data is controlled by iaclips, a service operated by an individual. For any question about your data, write to hola@iaclips.ai.
What we collect
| What | Where it comes from | What for |
|---|---|---|
| Your Google account: email address, name and account identifier | When you sign in with Google | To identify you, let you into the beta, and email you about your episodes |
| The videos you upload, or the YouTube video you send us as a link | You | To make your clips |
| What we derive from each video: transcript, sentences, candidate stories, rendered clips, thumbnails and captions | Our processing | To show and deliver your clips |
| What you do with your clips: opening, downloading, editing, deleting or marking them as not used, and the reasons you pick | You, using the app | To save your changes, and to measure and improve how we cut |
| Your options when uploading (language, caption and title style, length) and the interface language | You | To process the episode the way you asked and to email you in your language |
| Your plan and credits: your plan, its billing period and status, your payment provider’s customer identifier for you, and the minutes each episode used | You, when you buy or change a plan; our processing | To give you the minutes you paid for and show your balance |
Sign-up check: a salted fingerprint (hash) of the IP address you signed up from and of a random identifier for your device (the iac_dev cookie), never the IP or the identifier themselves |
When you create your account | To keep the free plan to one per person and stop abuse |
| Waitlist: your email, the page where you signed up, the page you came from, and your country (as reported by our network provider) | You, in the form | To let you know when we open |
How you found us: the first page of ours you opened, the site that sent you (its domain only) and the campaign tags in the link (utm_…) |
The iac_ft cookie, when you create your account |
To know which channels bring people to iaclips |
Product analytics. We use PostHog (servers in the United States) to see which pages are visited, where visitors come from, and which steps people reach (signing up, uploading, getting clips, buying a plan). Until you sign in it’s cookieless: nothing is stored on your device for it, and visits are told apart by an anonymous code that changes every day. Once you’re signed in, it uses a cookie and local storage on iaclips.ai and your account’s internal identifier, never your email or name. IP addresses are anonymized: PostHog doesn’t keep them. In the app (not on the public pages) we record session replays, a reconstruction of the screen used to find what gets in your way, with everything you type and all text on screen masked. If you’re in the European Union, the EEA, the United Kingdom or Switzerland, we ask first: until you accept, PostHog only counts your visits without cookies, with no session replays and nothing linked to your account, we don’t set the iac_ft cookie, and our servers send no analytics about you. You can change your choice at any time with the “Cookies” link at the bottom of the site. We don’t use advertising cookies. To opt out anywhere, turn on Do Not Track or Global Privacy Control in your browser: we then don’t load PostHog and don’t send analytics about you.
Cookies
The site uses these cookies, and one entry in your browser’s session storage:
iac_session: keeps you signed in for 30 days. Our database stores only a fingerprint (hash) of it, never the cookie itself.iac_oauth: lasts 10 minutes, only while you sign in with Google, to complete the sign-in securely.iac_lang: remembers the interface language you chose (1 year).iac_dev: a random identifier for your device, set when you sign in (400 days). It’s used only for the sign-up check above: we store a salted fingerprint of it, never the identifier itself.iac_ft: how you first reached the site (the page, the referring site’s domain, the campaign tags), set on your first visit (30 days; in the EU, the EEA, the UK and Switzerland only after you accept). It contains nothing that identifies you; it’s saved with your account if you create one, then deleted.ph_…(PostHog, with a matching local storage entry): only while you’re signed in (in the EU, the EEA, the UK and Switzerland only after you accept), for the product analytics above. It’s removed when you sign out or reject.iac_consent: remembers whether you accepted or rejected analytics cookies (1 year; only where we ask).iac-trimmer-exporting(session storage, not a cookie): on the free video tool, set only while a video is being saved, so that if the page closes before it finishes we can count it on your next visit. It’s removed when the saving ends or when you leave the page. It’s never set while analytics needs your consent and you haven’t accepted, nor with Do Not Track or Global Privacy Control.
Where it’s stored
Everything is stored with our cloud provider: your account and app data in its database, and videos, clips and processing files in its storage.
Who we share it with
To provide the service we use providers of these kinds. Each receives only what it needs for its part of the work.
| Kind of provider | What it receives | What for |
|---|---|---|
| Speech transcription | The episode’s audio | To transcribe it |
| AI models | The transcript text (with timestamps and who is speaking), the episode title, and a low-resolution copy of the video without sound | To pick the stories, decide where each clip starts and ends, remove filler words, write the clip’s title, and see what’s on screen to frame it. The video copy is deleted once that step is done, or after 48 hours at most |
| Cloud and storage | Your account, your videos, your clips and the other data in this policy | To host the site, the database and the files, and to send the notification emails |
| Product analytics (PostHog) | The pages you visit, where you came from, the steps above, your account’s internal identifier once you’re signed in, and the app’s session replays with typing and text masked | To understand how people find and use iaclips |
The transcription and AI model providers don’t receive your email address or your name. Some of our providers are in the United States, so your data may be processed there. Each provider applies its own retention policies to what it receives. Whatever is said or shown in your video reaches them as part of the content, so if the video contains personal data, that data reaches them too.
Processing runs on machines we operate ourselves. While they work on your episode they keep a working copy of the video and of each step’s files, which is deleted automatically 7 days after the job finishes. The original stays in our cloud storage, and if you edit a clip later we take it from there.
To improve the service, we use what you do with your clips (downloads, changes, deletions and their reasons) to build internal tests that we use to compare versions of our system and AI models. Those tests include the transcripts of those episodes, and we only run them with providers we’ve vetted. We don’t use your data to train models.
Also:
- Sign-in with Google: when you sign in with Google, Google tells us your email address, your name and your account identifier.
- YouTube links: if you send us a link, we download the video from YouTube.
- Payments with Stripe: when you buy a plan, you pay on Stripe’s page. Stripe receives your card details and your email address directly, and tells us your plan, its status and whether each payment went through. We never see or store your card number. Stripe handles your payment data under its own privacy policy.
We don’t sell your data or share it with anyone else. We never publish anything of yours without your permission.
The free video tool
On the free video tool (the same on each of its pages: trim video, compress video, video to MP3, video to GIF, MOV to MP4, crop video, change video speed, mute video, and their Spanish versions), your video is read and processed in your browser, on your own device: it is never uploaded to us or to anyone else. What we receive are product analytics events (PostHog, as above) about how the tool is used: the file’s type (MP4, MOV, …), its size and length in ranges (for example “100–500 MB” or “1–5 min”), the names of its video and sound codecs, whether it has sound, the options you used (shape, rotation, mirror, sound, volume, speed, fade in and fade out, quality, format, maximum size, number of parts, how many parts you removed), whether it was copied or re-encoded, whether saving worked or the error’s code, whether the sound had to be left out, how many passes fitting the maximum size took and whether the file still came out over it, how long it took and the result’s size, in ranges. When you save the frame on screen as a picture: that you did, and its format (JPG or PNG). Never the file’s name, its contents or any frame of it.
The browser extension
The iaclips extension for Chrome and Edge collects no data: it has no analytics, sends nothing to us or to anyone else, and stores nothing. It runs only on youtube.com, where it reads the address and title of the video you have open to show its button and the video in its window. When you click its icon in the toolbar, it also reads the address and title of the tab you have open, only to tell whether it is a YouTube video. Its window shows the video’s thumbnail, loaded from YouTube’s image server. When you click its button, it opens iaclips.ai in a new tab with that video’s link filled in, plus tags saying that you came from the extension and from which part of it (utm_source=chrome_extension, utm_medium=extension, and utm_content naming the button, the window or the menu). From there on you’re on our website, and this policy applies as on any other visit.
Technical logs and your IP address
Like any website, our cloud platform’s technical logs include the IP address you connect from. We use them only to find errors and abuse, and they’re deleted automatically after 7 days. To limit repeated waitlist sign-ups we count attempts per IP for 2 minutes, storing only a fingerprint (hash), never the IP itself. The sign-up check keeps a salted fingerprint of the IP you signed up from for 90 days.
How long we keep it
- Your account, episodes (including the original video), clips and actions: for as long as you have an account, or until you ask us to delete them.
- Working copies on our processing machines: 7 days after each job finishes.
- If you delete a clip in the app, it’s no longer shown, but its files stay stored until you ask us to delete your data.
- Uploads that never finished are deleted automatically after one day.
- Technical logs: 7 days.
- The sign-up check’s fingerprints (IP and device): 90 days after you create your account, then deleted automatically.
- Your plan, payments and credit balance: for as long as you have an account. Records of payments and invoices are kept as long as tax and accounting law requires, even after you delete your account.
- The waitlist: until you ask to be removed.
Your rights and how to delete your data
At any time you can ask us for a copy of your data, to correct something, to delete your account and everything in it (videos, clips and actions), or to remove you from the waitlist. Deleting your account cancels your plan; records the law requires us to keep (payments and invoices) are kept only for that. Write to hola@iaclips.ai from your account’s email address, and we’ll do it within 30 days. If you think we’re not handling your data properly, you can also complain to the data protection authority in your country.
Children
iaclips isn’t meant for anyone under 18, and we don’t knowingly collect their data.
Changes to this policy
If we change anything important, we’ll tell you by email or on the site before it takes effect.