Your footage stays on your disk
Cutroom is built local-first. The cutting, the transcription, and the background removal all run on your own machine, so your footage is not bulk-uploaded to a server, ours or anyone else's. What does leave your PC is what you trigger: a generation request, or image-to-video and the voice tools, which upload the specific frame or clip audio you point them at, always to the provider whose key you brought. This page lays out exactly what stays and what moves, plus the licensing checks, what a connected AI can touch, and the one case where Cutroom can be locked out.
Your footage, projects, and exports. Never uploaded.
Frames and audio, locally, to do and check the edit.
Only generation requests, to your provider, on your key.
The work happens on your machine
The AI reads frames to check its own work
When you connect an agent, it does read your frames and audio, because that is how it sees what it is editing and confirms a cut landed right. That reading happens as part of the edit, on your machine. It is not a training feed and it is not stored by us. If that honest exception matters to you, you can edit entirely by hand and no AI reads anything at all.
- The agent reads frames and audio to do and check the edit
- That happens locally, as part of the edit, not as a data feed to us
- Edit by hand and nothing is read by any AI
Reading a frame to edit it is not uploading it.
The agent looks at your footage the way you do, to make the cut. Whether that agent runs locally or in your own cloud account, the source files themselves stay on your disk. The one time a frame does upload is when you ask for image-to-video: it sends that still to your provider to animate. Nothing is handed to us.
Generation goes to your own provider
Here is where bytes leave your PC: when you ask the AI to generate an image, a video, or a voice, or when you reach for image-to-video or the voice tools. Those go to the provider whose key you brought, on your own account, because that is where the model runs. They never route through us. Image-to-video uploads the still you pass, and dubbing, voice isolation, voice change, and cloning upload the clip audio you choose. Everything else stays put.
- Only the generation and voice tools you invoke send anything out
- It goes to your provider, on your key, never through us
- Image-to-video and the voice tools upload the frame or clip audio you point them at
Where generation goes
- Your footage
- Stays local
Your project is a folder, not a cloud account
Cutroom does not keep your work in a cloud you sign into. A project is a plain folder on your disk, and the edit needs nothing outside it: the media you imported, the fast proxies, anything the AI generated, and the edit list all sit inside that one folder. When you import a clip, Cutroom copies it into the project rather than pointing at wherever it came from, and it never changes your originals. Moving to another machine is a copy, not an upload: bring the whole folder across and your media travels inside it. Nothing about the move goes through us.
- A project is one folder on your disk, with its media copied inside it
- Your original files are never modified, wherever you keep them
- To move machines, copy the whole folder; there is no cloud step and nothing routes through us
Your work is on your disk, not our server.
There is no Cutroom project cloud, so a move is just copying a folder. Because Cutroom copied your media into the project and never touched your originals, your footage is safe whether or not a clip finds its link after the move. If a link ever breaks, the file is still right there in the folder.
What the licence check actually sends
Cutroom is a paid app, so it does confirm your licence is real. When you activate, it makes a one-way fingerprint of the machine, a hash that cannot be turned back into your hardware, and binds your signed licence to it. The licence is tied to your account, not capped to one machine, so you can install on as many of your own computers as you like. From time to time the app checks in online to confirm the licence is still good and to refresh it. Each activation and check records its IP address and rough location, the country and city, which we keep for 180 days to catch one key being shared by a crowd. No footage, no audio, and no project data is ever part of that. The app also keeps a small sealed marker on your machine that records the last time it verified online, used only to notice if the system clock was wound back to dodge an expiry.
- The machine fingerprint is a one-way hash; your hardware ids are never sent
- Your licence binds to your account, with no cap on how many of your own machines
- A check keeps only an IP and rough location (country and city) for 180 days, never your media
What a licence check sends
A modified copy can be locked out
Cutroom watches whether its own code has been changed, and it reports that, not your footage. A single odd signal only raises a warning and you keep editing; it takes a real, repeated pattern for a build to lock itself. Because this is a paid app with no per-device limit, we can also block a Cutroom account outright if a licence is pirated, resold, or charged back. A block or a revoke stops Cutroom at its next online check, and that is the whole reach of it: it never touches your Delivvo account, your clients, your invoices, or the files already on your disk. If you think a block is a mistake, open a support request and a person will look.
- The app reports whether its own code was modified, never anything about your footage
- One stray signal only warns; a build locks out only on a real, repeated pattern
- A remote block or revoke stops Cutroom only, never your Delivvo account or your files
Lockout is about the licence, not your work.
Questions about privacy
Not for the editing. The editing, transcription, and background removal all run on your own machine, so your source files stay on your disk. The exceptions are the AI features you turn on: image-to-video uploads the still you pass, and dubbing, voice isolation, voice change, and cloning upload the clip audio you choose, always to the provider whose key you brought. None of it ever routes through us.
A connected agent reads your frames and audio to do the edit and to check its own work, the same way you look at footage to cut it. That reading is part of the edit and is not stored by us or used to train anything. If you edit by hand, no AI reads anything.
When you deliberately ask the AI to generate something, like an image, a video, or a voice. That request goes to the provider whose key you brought, on your own account. Image-to-video, dubbing, voice isolation, voice change, and cloning also upload the specific frame or clip audio you choose. It still never routes through us.
On your machine. If you connect a generation provider for image, video, or voice, you paste your own key and it stays local. Cutroom is not a middleman for it.
No. Your projects, media, and edits live on your disk. There is no cloud project store watching what you make.
Yes. The engines ship inside the app and are set up on first launch, so editing, transcription (Arabic and 90+ languages), captions, and cutout all run with no connection from the very first launch. You only need the network to connect an AI agent, run a generation, or install an even larger optional model. The core editing is fully local.
A connected agent drives the app through its command layer, working on your Cutroom projects and a sandboxed asset library that is yours. It can keep more than one project going, editing one in the background while you work in another. It cannot read your keys, your secrets, or the licensing internals. It can trigger the same generation and upload steps you can, like image-to-video and the voice tools, always on your own provider key. Your provider key is never handed to a connected agent.