Skip to content
ClipCocoon
Guides

How Your Videos Stay on Your Device

You don’t have to take our word for it. Here’s how it works, and how to check.

The short answer

ClipCocoon sends the program to your browser instead of sending your video to a server. The tool runs inside your browser tab, reads your video from your device’s memory, and saves the result straight back to your device. A browser security rule blocks the page from sending data anywhere except our own site, our model file server and our anonymous analytics.

What happens when you use a tool

  1. The page loads. Your browser downloads the page and its code from clipcocoon.com, like any website.
  2. You choose a video. The browser hands it to the page’s code in memory. Nothing is sent.
  3. The tool does the work. Your browser’s own video decoder and encoder (the WebCodecs feature built into Chrome, Edge, Safari and Firefox) read and write the video. For captions and silence cutting, a small AI model runs on your device too.
  4. You download the result. The new file is created in your browser’s memory and saved from there. It never existed anywhere else.
  5. You close the tab. The browser clears your video from memory.

What about the AI?

Most “AI video” sites send your clip to a cloud server where the AI runs. Ours works the other way around: the AI model comes to you. The first time you use Auto Captions or the Silence Remover, we ask before your browser downloads the model (about 2 MB for silence detection, 80–110 MB for captions) from models.clipcocoon.com. It’s stored in your browser, so next time it starts in a second or two, even offline.

The rule that blocks uploads

Every page on ClipCocoon is served with a Content Security Policy, a set of rules that your browser enforces, not us. This is the part that controls where the page can send data: 

connect-src 'self' blob: https://models.clipcocoon.com https://analytics.clipcocoon.com

In plain words: the page may only talk to its own site, to files already in your browser’s memory (blob:), to our model file server, which only hands out model files, and to our own cookie-free analytics server, which counts page views and never receives your files or their names. If any code on the page tried to send your video anywhere else, the browser would refuse. Images are restricted the same way, so a file can’t be smuggled out inside an image request either.

Check it yourself

1. Watch the Network tab

  1. On a computer, open any tool and press F12 (Windows) or Option + Command + I (Mac).
  2. Click the Network tab, then use the tool with a test video.
  3. Look for a request about the size of your video going out. You won’t find one.

2. Go offline

Use a tool once so it has loaded, then turn on airplane mode or disconnect from Wi-Fi and use it again. It still works, because nothing needs to go over the internet.

3. Read the security rule

In the Network tab, click the first request (the page itself) and look under Response Headers for content-security-policy. It’s the same rule quoted above.

What does leave your device

To be complete: Cloudflare, our host, processes standard technical data such as IP addresses to deliver the site and the model files, and we count visits and tool use with cookie-free analytics. None of this includes your videos or their names. We don’t show ads at the moment. If we add them, ad networks need their own connections, and we’ll update this page to say exactly what they can and can’t see. Your videos will still never be sent. The full details are in our Privacy Policy.