Your footage stays on your device unless you ask otherwise.
- Editing, playback and export run in your browser — your media files are never uploaded to us to be edited
- Projects are stored on your device, with an optional backup of the edit itself — not your media — to your account
- An account is required: we hold your name, email, a hashed password and your sign-in sessions
- Some assisted features cannot run locally. Those send the part of your project they need to a processing service, and the editor says so before it runs
- Analytics are cookieless and self-hosted, and record pages and product events — never who you are
- We do not sell your data, and we do not train models on it
What we hold
Your account. Your name, email address, a securely hashed password, and the session records that keep you signed in. If you sign in with Google or GitHub instead, we hold the identifier that provider gives us rather than a password.
Your plan. Which plan you are on, your credit balance and the record of what used credits. Payments go through Stripe: we never see or store your card details.
Your projects. These live in your browser, in IndexedDB and the origin private file system. If you turn on backup, a copy of the project's edit and its metadata — names, thumbnails, dates — is kept in your account. Your source media is not part of that backup.
Support messages. What you send us through the contact form, so we can answer it.
Features that send data off your device
Most of CutPro runs locally. Captions can be generated in your browser with a model downloaded to it, and background removal, reframing, silence removal, noise reduction and every effect run entirely on your machine.
Some features cannot. When you choose one, only the part of your project it needs is sent, used to perform that task, and returned:
- Cloud transcription — the audio of the clip you are captioning, to AssemblyAI. The local engine is the alternative and sends nothing.
- The assistant, descriptions and translation — your prompt, and the captions or project details the request is about, to the language model provider.
- Image generation — the prompt you type, to Hugging Face.
- Stock media, sounds and stickers — your search words, to the library you are searching.
Connecting your own provider key sends those requests under your own account with that provider. Keys you store with us are encrypted.
Who else is involved
The short list of services CutPro relies on, and what each one receives:
- Our own server — hosting, plus self-hosted analytics (Umami) and error reports (GlitchTip). Neither leaves our server.
- Stripe — payments and subscriptions. Your card details go to Stripe, never to us.
- Resend — account email, such as a password reset.
- The providers behind the assisted features listed above, each receiving only what that feature needs.
Your choices
- Ask us for a copy of what we hold about you, or for it to be corrected
- Delete your account from your settings: that cancels any subscription and removes the data we hold for it
- Clear your browser data to remove the projects stored on your device
- Choose the local engine, or your own provider key, for the features that offer one
We keep account and billing records for as long as you have an account, and afterwards only where the law requires it.
Changes, and contact
We will update this page when what we do changes, and change the date below when we do. Material changes are announced to account holders before they take effect.
CutPro is made by QuantumBytes. For anything about your data, use the contact page.
Last updated: 23 September 2026