Privacy

replaycut is a self-hosted program. It runs on your own PC, and there is no replaycut server, account or telemetry. This page exists because the integrations with YouTube, X and OneDrive ask for a privacy policy of the application that requests access.

What replaycut stores, and where

Your recordings, the cuts, the previews and the shared clips stay in the folders on your PC that you configured.
Settings are a JSON file in your user profile; titles, the seen list and the share history are a database file next to it.
Credentials and OAuth refresh tokens for the integrations you connect (Nextcloud, OneDrive, S3, WebDAV, YouTube, X, Telegram, Discord, webhook) are stored in your PC's credential store: the Windows Credential Manager, or the keyring behind the Secret Service on Linux. They are never written to a file and never sent anywhere but to the service they belong to.

What leaves your PC

Only what you trigger: a share uploads the clip you cut to the storage you chose and posts the link to the notify integrations you switched on. The optional update check asks GitHub once a day for the newest release and sends nothing about you.

Google user data

When you connect a YouTube channel, replaycut asks for the scope https://www.googleapis.com/auth/youtube. It uses that access only to read the channel's name for the settings card, to upload the videos you share, and to delete a video when you delete the clip in replaycut with "also remove from storage". The refresh token stays in your credential store; "Disconnect" removes it. replaycut does not share Google user data with anyone, does not use it for advertising, and does not let humans read it. Its use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

This website

replaycut.de sets no cookies, carries no analytics and no tracker, and loads no fonts or scripts from anywhere else. Nothing you do here is stored.

One request does leave your browser: to show the version, the size and the date on the download button, the page asks the public GitHub API for the newest release. GitHub sees your IP address and your browser's user agent in that request, as it would if you clicked through to the download yourself. The answer is kept in your browser for an hour and nowhere else. Without JavaScript the button simply links to the releases page, and no request is made.

The site is hosted on GitHub Pages, which serves the files and logs the accesses; see GitHub's privacy statement. There is no server of ours involved.

Contact

Questions go to the issue tracker, or to the address in the Impressum.

Last updated 8 September 2026.