Kineticlip — Privacy Policy
Version: 1.1 Last updated: 7 August 2026 Applies to: Kineticlip for Windows, version 1.0.0 and later.
The short version
Kineticlip runs on your computer. It has no user accounts and no analytics. We never receive your recordings, your transcripts, your clips or your settings — there is no server of ours for them to go to.
We do run exactly two small endpoints, and they are named here rather than buried in §4, because saying "no servers of ours" while running them would not be true:
- Licence checking. If you enter a licence key, the key and your Windows computer name go to our own validation endpoint, which asks Lemon Squeezy. Nothing is sent unless you enter a key.
- Bug reports. If you press Report a bug, what you typed — and your email address if you fill that in — is sent to our feedback endpoint. Nothing is sent unless you press send.
Your recordings — the raw video and audio you feed in — never leave your PC, in any mode. There is no server of ours for them to go to.
A finished clip is different, because sending it somewhere is the point of the app. It goes only where you send it: to YouTube or TikTok when you click publish, and to your own Discord server automatically if you turn on Discord notifications. Those are your accounts on your services; we never receive a copy.
Some things do leave your PC, and every one of them is either something you turned on or something the app needs to fetch:
- Software and models the app downloads on first launch (Python libraries, the speech model, the local AI engine, a font).
- Update checks: to our own website, which answers with the latest build id, and to GitHub Releases for the update file itself.
- The caption font: if you open the caption font picker or the Review preview, a stylesheet for the Bangers font is fetched from Google. Not on every launch — only on those screens.
- Optional cloud AI: the text of what was said in a clip, sent to Anthropic or OpenAI, whichever you pick — off by default, behind a consent screen you have to read and tick.
- Discord notifications: if you set them up, the finished clip is posted to your own Discord automatically when it is ready. That is the one thing that sends a clip out without you clicking anything.
- Publishing: the finished video goes to YouTube, TikTok or X when you click publish for that platform.
- A bug report, if you press Report a bug and send one. See §6.
- Your licence key, if you enter one. Kineticlip is free and fully working without a key — a key only takes the watermark off the clips you export — so nothing goes anywhere until you paste one in. After that, the key and your Windows computer name go to our validation endpoint, which checks it with Lemon Squeezy. §4 has the detail.
The watermark itself sends nothing. It is drawn onto the video on your own PC by the same program that burns in the captions, and the part of Kineticlip that makes your clip never contacts the licence server at all — it reads a small file on your disk (§2). A clip has never been sent anywhere to decide whether to mark it.
The rest of this document is the detail.
1. Who is responsible
Alex R., an individual established in the State of New York, United States, contact Alexcrocrox@gmail.com.
Kineticlip stores your recordings, clips, transcripts and settings on your own machine, and we hold no copy of any of them. The only things that reach us are the two you send deliberately: a licence key you entered (with your computer name, so you can tell your activations apart) and a bug report you pressed send on (with your email address if you filled it in). If you want either removed, email the address above and say so; §8 explains how to delete everything on your own PC.
2. What stays on your computer, and where
Scroll this table sideways to see every column.
| What | Where |
|---|---|
| Your settings, including API keys and sign-in tokens | %APPDATA%\Kineticlip\config.toml, and youtube_tokens.json / tiktok_tokens.json / x_tokens.json in the same folder |
| The clip database (clip list, titles, transcript paths, ratings, publish history) | %APPDATA%\Kineticlip\autoclipper.db |
| Logs | %APPDATA%\Kineticlip\logs\ |
| A record of app crashes: time, app version, Windows version, the error message and stack, with credentials and your username stripped out | %APPDATA%\Kineticlip\crashes\crashes.jsonl (capped at 256 KB, 3 files) |
| Your licence key, whether this computer may export without the watermark, and the date that answer stops being trusted | %LOCALAPPDATA%\AutoClipper\entitlement.json — an ordinary text file. Your key is in it in the clear. The part of Kineticlip that makes your clip reads this instead of asking the internet, which is why a render never waits on, or fails because of, a licence check. |
| An identifier for this install, used for the licence's device count | %LOCALAPPDATA%\AutoClipper\instance-id — a randomly generated identifier, made once on this PC. It is derived from nothing: it says nothing about you, your hardware or your Windows account. It lives outside the settings folder so a reinstall does not spend a second one of your three activations. |
| Work-in-progress files: transcripts, cut segments, part-rendered video | %APPDATA%\Kineticlip\work\<clip>\ |
| Finished clips, and clips you rejected | %APPDATA%\Kineticlip\ready\ and …\rejected\ |
| The AI runtime: Python libraries and the speech model | %LOCALAPPDATA%\AutoClipper\ |
| The local language model and the small engine that serves it | %LOCALAPPDATA%\AutoClipper\ as well. That folder keeps the old project name; it is several GB, and renaming it on an upgrade risked losing it, so it was left alone. |
| Your original recordings | Wherever your capture software put them. Kineticlip reads them and does not move or modify them. |
Credentials are stored in plain text, including your licence key. Your Anthropic or OpenAI API key, your Discord bot token or webhook URL, the YouTube / TikTok / X sign-in tokens, and your licence key all sit in ordinary files in the folders above. Nothing here is encrypted at rest. Windows file permissions keep other user accounts out, but any program running as you can read them. So: do not share those folders, and do not put them in a cloud-synced location you share. The app's Report a bug button strips credentials out of anything it sends (§6).
3. Transcription and the AI stages run on your machine
- Speech to text runs entirely locally, on your graphics card if you have a supported NVIDIA one and on your processor otherwise. It uses a model downloaded once during setup. No audio, video or text is uploaded at this step, in any mode.
- Picking the highlight, choosing music and writing the title run by default on a language model stored on your machine, served by a small local engine that only listens on
127.0.0.1(your own computer, not the network). The code refuses to point that engine at anything other than your own machine. - Cutting, mixing and burning in captions are done by FFmpeg on your machine.
This is enforced in the code, not just intended: the cloud client cannot even be constructed while the app is in local mode, and there is an automated test (backend/tests/test_llm_local_is_local.py) that runs the AI stages in local mode with every non-loopback network connection blocked and requires them to succeed.
4. Everything that leaves your computer
Scroll this table sideways to see every column.
| What is sent | To whom | When | Can you turn it off? |
|---|---|---|---|
| A request for the Python runtime and libraries | python.org, PyPI, download.pytorch.org | Once, during first-launch setup | No — the app needs them. You can install once and stay offline after. |
| A request for the speech model | Hugging Face (Systran/faster-whisper-large-v3, or the smaller model on CPU-only machines) | Once, during setup | No |
| A request for the local AI engine and model | GitHub (llama.cpp release), Hugging Face (the GGUF model) | Once, during setup | No, if you want local AI |
| A request for the caption font file | github.com (Google Fonts repository) | Once, during setup | No |
| A request for the Bangers caption-font stylesheet | fonts.googleapis.com | When the caption font picker or the Review preview loads — not on launch. Google sees your IP address on those requests. | Not today. It affects only the caption preview screens. |
| Your app version, and a request for the latest build id | Our website (kineticlip.io/api/version) | On launch, then every 6 hours while the app is open | No. There is no switch to turn update checks off. We see your IP address and the build you are running each time one is made, and nothing else. |
| A request for the update file itself | GitHub Releases | Every 6 hours while the app is open | No. GitHub sees your IP address. |
| Your licence key, and your Windows computer name | Our own licence endpoint (xhtaadkdvrgsqjxsowbc.functions.supabase.co/validate-license), which checks the key with Lemon Squeezy (api.lemonsqueezy.com) | Only if you enter a key. Nothing is sent before that, and Kineticlip is free and fully working without one. When you paste a key in, it is sent to be checked and, the first time, registered against this computer. The name that registration is given is your Windows computer name, sent as it is — if that is "Alex-PC", that is what is sent and what you will see listed against your licence. After that it is re-checked while the app is open and online, at most about once a week. Making a clip never sends anything: that part of the app reads the file in §2 instead, so it works offline and cannot be held up by a licence server. If a check cannot get through, your clips stay watermark-free for 14 days from the last one that did. | Yes — don't enter a key. Then nothing is sent, everything still works, and your exports carry the watermark. Once a key is in, checking it is how the watermark stays off, so it is not separable from the thing you bought. Nothing else about you is sent. |
| What you typed in the bug report, your email address if you filled it in, the app version, your Windows version, the anonymous install id from §2, and the tail of the logs if you ticked that box | Our own feedback endpoint (xhtaadkdvrgsqjxsowbc.functions.supabase.co/submit-feedback) | Only when you press send in Report a bug | Yes — don't use it. Nothing is sent otherwise, and the log tail is a separate tick box you can read before sending. |
| The words spoken in your clip, as text; the name of the folder the recording was saved in (Kineticlip treats that folder name as the game); and the clip's length | Anthropic, or OpenAI — whichever you pick | Only in optional cloud AI mode, once per clip, at the highlight / music / title steps | Yes. Off by default. Turning it on requires reading a disclosure screen and ticking a box, and one click switches back. |
| The finished clip video file, plus its title and rating buttons | Your own Discord server | Automatically when a clip finishes, if you configured a Discord webhook or bot. Posting to Discord is the last stage of the pipeline, not something you click. | Yes — set Discord notifications to off in Settings, or leave the webhook/token blank. |
| The finished clip video file, plus the title, description and tags you approved | YouTube or TikTok | Only when you click publish for that platform | Yes — don't connect them, or don't publish. |
| The finished clip video file, plus the text of the post | X (Twitter) | Only when you connect an X account and click Post to X for that clip | Yes — don't connect X, or don't post. |
| Ratings and clip statistics | Your own Discord server | When you or your viewers use the Discord commands you set up | Yes |
Notes on the cloud AI row, because it is the one that surprises people:
- The video and the audio are never sent. Only text.
- It runs on your own Anthropic or OpenAI API key, and that company bills you directly. There is no cost to us and no way for us to see or refund it.
- What Anthropic or OpenAI does with the text is governed by their terms and privacy policy, not this one. We have no visibility into or control over it. If your clips contain other people's voices — party chat, a co-streamer, a family member in the room — their words are in that text too. That is worth thinking about before you switch it on.
- The consent you give is recorded with a version number (currently version 1). If the description of what gets sent materially changes, that number goes up and you are asked again rather than silently carried over.
- Clips already processed are not re-sent when you switch modes.
4a. Links the app shows you
Some screens contain links — mostly setup instructions and the terms of the services you can connect. Clicking one opens your normal web browser and visits that page as you, exactly as if you had typed the address. Kineticlip attaches nothing: no identifier, no clip data, no licence key. Nothing happens until you click.
The links are to: console.cloud.google.com, www.youtube.com, policies.google.com (also published at www.google.com/policies/privacy), myaccount.google.com, console.anthropic.com, platform.openai.com, discord.com, support-dev.discord.com, developers.tiktok.com, developer.x.com, www.nvidia.com, developer.nvidia.com, github.com, ffmpeg.org and the checkout page at kineticlip.lemonsqueezy.com.
4b. What YouTube requires us to tell you
If you connect a YouTube channel, four things are worth stating plainly, and YouTube's developer policies require us to state them:
- Kineticlip uploads through YouTube API Services. That is the official Google interface for putting a video on your channel.
- You agree to be bound by the YouTube Terms of Service (<https://www.youtube.com/t/terms>) when you use that connection.
- Google handles your Google-account data under the Google Privacy Policy (<https://policies.google.com/privacy>, also published at <http://www.google.com/policies/privacy>). That is Google's document, not ours, and it governs what Google does with your account.
- You can revoke Kineticlip's access to your channel at any time, and in two independent ways: click Disconnect on the Publish tab, which asks Google to cancel the token and then deletes our copy of it; or remove Kineticlip yourself from the Google security settings page, <https://myaccount.google.com/permissions>, which works even if Kineticlip is uninstalled. Either way the only thing we ever held — the sign-in token and your channel name — is on your PC and goes with it. Deleting a clip in the Gallery deletes the video id and link we stored for it.
The same applies in spirit to TikTok, X and Discord: those connections are your own developer apps on your own accounts, under those companies' terms.
4c. Discord message content is never sent to an AI
If you use the Discord features, nothing written in your Discord server is read by Kineticlip's AI stages, cloud or local. The AI only ever sees the words spoken in your own recording, transcribed on your PC. In webhook mode — the default — Kineticlip reads nothing at all from Discord; it only posts. Discord's developer policy forbids using message content to train or prompt AI models, and Kineticlip has no code path that could.
5. What we do not do
- No analytics. No usage tracking. No event logging to anyone.
- No automatic crash reporting. Crashes are written to a local file (§2) so the app can tell you it crashed and so the details are there if you choose to attach them to a bug report (§6). Nothing about a crash is transmitted unless you press send yourself.
- No advertising, no ad networks, no profiling.
- No selling or sharing of anything. The only things we ever receive are a licence key you entered and a bug report you sent, and neither is passed to anyone except Lemon Squeezy for the key check.
- No account, no sign-up, no email required to use the app. (A licence key is not an account — see §4.)
If any of that changes in a future version, this document must change with it, in the same release.
6. Bug reports you choose to send
At the bottom of the left sidebar there is a Report a bug button. It opens a box you type into. What you send is transmitted to our feedback endpoint when you press send — it is not saved to a file for you to attach, and nothing goes anywhere until you press send.
What goes: your message; your email address, but only if you fill that field in; the app version and build; your Windows version; the anonymous install id from §2; and — only if you tick the box — the tail of the log files. The box shows you the log tail on screen before it goes, so you can read exactly what you are sending.
What is deliberately kept out or masked: API keys, bot tokens, webhook URLs and OAuth tokens (matched by shape, so a credential we did not think of is still caught), your video files, and your clip titles.
We keep what you send for as long as it takes to answer you and fix the problem. Ask at the address in §1 and it will be deleted.
7. How long things are kept, on your machine
- Work-in-progress files (transcripts, part-rendered video — a few hundred MB per clip) are deleted automatically once a clip has finished or been rejected and a 48-hour grace period has passed. The clean-up runs about once an hour. The grace period exists so "Reprocess" on yesterday's clip is still fast.
- Logs rotate at 10 MB per stage and keep 3 old files, so they cannot grow without limit. The crash record is capped the same way, at 256 KB across 3 files.
- Finished clips, rejected clips, and the clip database are kept until you delete them. Kineticlip never deletes your original recordings.
- Uninstalling does not delete your data, on purpose — so reinstalling or updating does not lose your clip history. §8 tells you how to remove it.
8. How to remove everything
- Uninstall Kineticlip from Windows Settings → Apps.
- Delete
%APPDATA%\Kineticlip— settings, API keys, sign-in tokens, database, logs, crash records and clips. If you upgraded from an early build, check for%APPDATA%\AutoClipper v4as well — that is the folder it used before, and it is moved rather than copied. - Delete
%LOCALAPPDATA%\AutoClipper— note the old name; this folder is not called Kineticlip. It holds the Python runtime, the speech model, the local AI model (several GB), yourentitlement.jsonwith your licence key in it, and theinstance-idfile. - Optional but worth doing: revoke the app's access on the services you connected — Google account permissions, TikTok, X, your Discord server, and your Anthropic or OpenAI API key.
Your original recordings are untouched; delete them yourself if you want them gone.
9. Children
Kineticlip is not designed for or directed at children. See the EULA for the minimum age to buy a licence.
10. Where your data physically is
On your computer, in your country. The exceptions are the flows above: cloud AI text goes to Anthropic or OpenAI (both US companies), publishing goes to the platform you chose, and the two small endpoints in §1 — the licence check and the bug reporter — are hosted for us in the United States. Downloads come from those companies' own CDNs. Kineticlip has no database of your clips anywhere and no region for them, because it never receives them.
11. This is a description, not a compliance claim
This document describes how the software behaves. It is not a statement that we or you comply with any particular privacy law. If you need to know how the GDPR, the UK GDPR, the CCPA or anything else applies to your situation — for example because you record other people's voices, or run a business — ask a qualified adviser.
12. Changes
If the software's behaviour changes, this document changes in the same release, and the version and date at the top move. Material changes to what leaves your machine also raise the in-app consent version, so you are asked again rather than assumed to agree.
Questions: Alexcrocrox@gmail.com.
Related: [Licence agreement](/eula) · [Refund policy](/refund). The full list of third-party licences ships inside the app.