Privacy
Last updated 2 September 2026
ClipForge is a private, self-hosted tool. It is not a public service and does not accept sign-ups — accounts exist only by invitation from the owner. It runs on a single server operated by the owner, and there is no analytics, no advertising, and no third party is sent your data for any purpose except the ones listed below.
What is stored
- Your account — email, username, timezone, and a hashed password. Passwords are hashed with argon2id and cannot be read back, including by the owner.
- Video you add — the source file, a low-resolution preview copy, and any clips rendered from it.
- Transcripts — the text and word timings produced from the audio, plus the clip suggestions derived from them.
- Connected accounts — if you connect YouTube, the access and refresh tokens are stored encrypted, along with the channel’s public id and name. They are used to upload clips you explicitly schedule or publish, and to tell your connected channels apart.
- An activity log — sign-ins, project creation and deletion, imports, and administrative actions, with the IP address of the request.
How long it is kept
- Source video is deleted automatically after 7 days.
- Rendered clips are deleted automatically after 30 days.
- Deleting a project removes its record immediately; its files are removed by a nightly job.
- Transcripts and clip settings are kept while the project exists, so a clip can be re-rendered without re-processing the video.
Third parties
- Anthropic or OpenRouter, if an API key is configured. Excerpts of transcript text are sent so the model can rank and describe clip candidates. The video itself is never sent. If no key is configured, nothing leaves the server and ranking falls back to local heuristics.
- YouTube, only if you connect an account. Clips are uploaded only when you schedule or publish them. ClipForge asks for permission to upload, and for read access used for a single thing: reading the name and id of the channel you just connected, so that several connected channels can be told apart. It cannot edit or delete anything on your channel.
- The source of any link you import, which receives a download request from the server.
YouTube API Services
Publishing to YouTube is built on YouTube API Services. By connecting a YouTube channel you also agree to the YouTube Terms of Service, and Google’s handling of the data it receives is governed by the Google Privacy Policy.
What ClipForge holds from YouTube is small and listed above: the tokens from your authorisation, and the id and name of the channel you connected. It stores no video, comment, subscriber or analytics data from your channel, and it reads nothing beyond the connected channel’s own name and id.
You can withdraw ClipForge’s access to your Google account at any time, and without asking anyone, at myaccount.google.com/permissions. Doing so stops any further upload immediately. Disconnecting from Settings deletes the stored tokens here as well; doing both leaves nothing on either side.
Your control
You can delete any project, which deletes its video, transcript and clips. You can disconnect a linked account at any time from Settings, which deletes the stored tokens. To remove your account entirely, ask the owner of the instance — there is no self-service deletion, because there is no self-service sign-up.
Contact
This instance is operated by Fathir Yudhistira. Reach the operator at fathiryudh03@gmail.com.
The Google Cloud project behind the YouTube integration is registered to fatneursaur@gmail.com, which is the address shown on Google’s consent screen when you connect a channel. Both addresses are the same person; they are listed together so the consent screen and this site are visibly the same operator.