For material that cannot go to somebody else’s server: unreleased work, an NDA, a patient, a client, a case. The file is read where it sits, the render happens in the tab, and nothing is sent anywhere.
It is worth being precise, because the phrase is used loosely. In cutvid there is no server to upload to. The application is a set of static files; once the page has loaded there is no API it talks to, no bucket the media is copied into, and no account the work is attached to.
Open the network panel in the browser’s developer tools and cut something. After the page and its assets have loaded, there are no further requests: no upload, no telemetry, no analytics beacon. Or load the page once, turn the network off, and keep editing: the work carries on because there was never anything on the other end of it.
Most tools that promise no upload are a single-purpose trimmer. This one has a timeline with ripple trim and sync-locked tracks, nested sequences, keyframes on an anchor, 33 transitions, chroma key, LUT grading, titles that kern, a per-clip audio chain, transcription with speakers, captions, screen and camera recording, and an MP4 at the end.
What it does not do:
No account, no install, nothing uploaded. The first edit takes as long as a page load.