BatchClips — Privacy

Last updated: 2026-08-16

BatchClips is a desktop application. It runs on your computer, and this document says exactly what does and does not leave it.

Your video never leaves your machine

Downloading, transcription, face detection, title generation and rendering all happen locally. No video, no audio, no transcript, no clip and no still frame is uploaded anywhere.

Speech recognition uses a model that is downloaded once and then runs offline. There is no cloud transcription service involved, and no API key is required.

This is the part that matters most, and it has not changed. What follows is about your account, not your work.

You sign in with Google, and we count what you make

BatchClips Desktop is free. To use it you sign in with a Google account. That means we know who you are, and we keep a count of how much you use the app.

This is a deliberate change. Earlier versions of this app had no accounts and no usage tracking at all, and said so here. If you used one of those, read this section rather than assume it still applies.

What we learn about you

Stored on our server	Why
Your email address	To tell one user from another
Your Google display name	So the list is readable
When you first signed in, and when you were last active	To see who is still using it
How many renders you ran, and on which days and at which hour	To see how busy the app is
How many clips those renders produced	Same
How many machines you have signed in on	To spot a shared account

That is the complete list. There is no field anywhere in the database for anything else.

What we do not learn

Nothing about the videos themselves. Not the file names, not the links you pasted, not the transcripts, not the titles, not the captions, not the thumbnails. The count says *five clips*; it cannot say what was in them.
No IP addresses.
No password. Google handles the sign-in; we never see one.
Nothing from your disk beyond the video you choose and the folder you pick for output — and neither of those is reported.

How the sign-in works

Google returns a signed proof of your email address. We check Google's signature on it, then throw it away and issue this machine a random token of its own. That token is what the app sends afterwards, and only its hash is stored — the same way a password database works, so a copy of our database does not let anyone sign in as you.

Your Google account is never accessed for anything else. The permissions the app asks for are the two smallest ones Google offers: your email address and your name.

What else is sent, and where

To the internet, on your instruction only:

When	Where
You paste a video link	The site you linked to (via yt-dlp)
First run	Hugging Face, once, to download the speech model
First run	Google Fonts, once, to download caption fonts
You press "Check for updates"	`license.batchgpt.store`
You press "Update now" for yt-dlp	GitHub

What is stored on your computer

Everything is under %LOCALAPPDATA%\BatchClips:

your clips, projects, downloads and transcripts
the speech model and caption fonts
application logs (logs\)
your sign-in token (licence.json)

Uninstalling BatchClips leaves this folder in place so your work is not destroyed. Delete it by hand if you want it gone.

Logs record what the app did: file names, video durations, errors and ffmpeg output. They stay on your machine and are never uploaded. If you send one to support, read it first — it will contain the names of files you processed.

Signing out, and deleting your data

Settings → Sign out removes the token from this machine. Your history on the server is unaffected.

To have your account and everything recorded about it deleted from the server, message us on WhatsApp. It is one command at our end, the row is removed outright, and nothing of it is kept.

Contact

WhatsApp: +92 319 3730707

Website: batchgpt.store