CutBench ("we", "us") is a desktop application distributed from cutbench.com. We are based in Portugal. For privacy or data-protection inquiries, contact: mail@cutbench.com.
We do not operate a backend that collects or transmits user data. The only information that ever leaves your computer is:
| Data | When | Where It Goes |
|---|---|---|
| Name, email, primary game, optional GPU tier, optional creator role | You submit the lead-capture form on cutbench.com | Relayed via Web3Forms to our email inbox. Used only to reply to you. Not stored in a CutBench-owned database. |
| OAuth authorization codes | You click CONNECT YOUTUBE or CONNECT TIKTOK in the app | Exchanged with Google / TikTok on your computer. Resulting refresh tokens stay in %LOCALAPPDATA%/ContentMachine/secrets/ on Windows (or the analogous POSIX path). |
| Video file uploads | You click PUBLISH on a selected story | Uploaded directly from your computer to YouTube or TikTok via their official APIs. We never see the bytes. |
%APPDATA%/ContentMachine/config.yaml or the POSIX XDG equivalent.None of this is synchronized to a cloud service.
cutbench.com sets no first-party cookies. Cloudflare, the CDN serving cutbench.com, may set strictly necessary security cookies for security or bot protection. We do not run ad-tech tracking pixels.
CutBench is distributed through Steam. We do not operate a download host and
collect no download analytics. (The former get.cutbench.com
direct-download counter was retired in June 2026.)
youtube.upload, youtube.readonly — to upload videos and read your channel ID for the "connected as" indicator. We never read private videos, comments, or subscriber data.user.info.basic, video.upload — to read your display name/open_id and upload videos to your TikTok drafts. We do not use video.publish (direct-post) scope.You can revoke either connection at any time from Google Account Permissions or TikTok Manage Apps.
"Google user data" means the data CutBench accesses through Google APIs: your YouTube channel ID and basic channel information (via the youtube.readonly scope) and the videos you choose to upload (via the youtube.upload scope).
We do not sell, rent, share, transfer, or disclose your Google user data to any third party. We do not transfer or disclose your Google user data to third parties for purposes other than the ones described in this policy. CutBench runs entirely on your own computer and we operate no backend server, so your Google user data is never transmitted to, processed by, or stored on any server we control.
The only transfer of Google user data is initiated by you: when you click PUBLISH, the rendered video is uploaded directly from your device to YouTube through Google's official YouTube Data API. We never receive or see this data.
The third-party services that power our website — Web3Forms, Plausible, and Cloudflare — never receive any Google user data; they only handle the website contact form and anonymous, aggregate website metrics.
We do not use Google user data for advertising, and we do not use it to develop, improve, or train any generalized or standalone AI/ML models.
How long we keep Google user data, and how it is refreshed. Everything CutBench stores from YouTube stays on your own device, and it is limited to the following:
If CutBench finds that you have revoked its access on Google's side, it deletes the stored token and all stored YouTube data at once. Nothing else from YouTube is stored, and nothing is stored on any server we control.
Security procedures are in place to protect the confidentiality of your data, including the sensitive credentials used to connect your accounts:
%LOCALAPPDATA%/ContentMachine/secrets/ on Windows, the analogous POSIX path elsewhere), with restricted file permissions (0o600 on POSIX, a restricted ACL on Windows) so that only your operating-system user account can read them. They are never synchronized to any cloud and never transmitted to us.You can revoke CutBench's access to your Google account at any time at Google Account Permissions, and DISCONNECT YOUTUBE in the app revokes that access at Google and deletes the channel name and upload records CutBench keeps on this computer. You can also revoke CutBench's access on Google's security settings page at https://security.google.com/settings/security/permissions. To report a security issue, email mail@cutbench.com.
CutBench's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Our use of information received from YouTube APIs also complies with the YouTube API Services Terms of Service. By using CutBench you also agree to the YouTube Terms of Service and acknowledge the Google Privacy Policy.
For the limited personal data we receive (lead-capture form submissions and support emails), you have the right under the EU General Data Protection Regulation (GDPR) to:
Email mail@cutbench.com to exercise any of these rights. We typically respond within 30 days.
Google user data. Requests concerning Google user data (section 6) are fulfilled within 7 calendar days. You do not need to write to us to delete it: DISCONNECT YOUTUBE in the app deletes the locally stored YouTube data immediately. Deleting data from CutBench does not delete anything on YouTube — to delete videos or data on YouTube itself, use YouTube Studio.
We may update this Privacy Policy from time to time. Material changes will be reflected in the "Last updated" date above.
This Privacy Policy is governed by the laws of Portugal and the EU General Data Protection Regulation (GDPR). For users in the European Union, your statutory data-protection rights apply regardless of these terms.
Privacy questions, data requests, security reports: mail@cutbench.com.