You're giving a background app access to your YouTube channel. You deserve a straight answer on what that means — not buried in a privacy policy.
Your YouTube OAuth token and all API keys are stored exclusively in files on your own PC. Klipr has no server that receives or stores them. We literally cannot see them.
In your Klipr installation folder — typically %localappdata%\Klipr\. The files never leave your machine unless you move them yourself.
Visit Google's permissions page, find Klipr, click Remove. Your YouTube access is gone instantly. Or just delete token.json from the install folder. Either works immediately.
Upload videos and read basic video statistics (views, likes) on videos Klipr uploaded. That's the full extent. It cannot delete videos, access your revenue data, or read your private content.
Your YouTube channel continues working exactly as it did before. Your account doesn't depend on us — the clipping, editing and uploading all happen on your PC, using a token stored on your PC. Klipr does run one small service of its own, which checks your license. If we shut down tomorrow that would stop, but you revoke OAuth access, uninstall, and your channel is completely unaffected. Your videos stay up. Your subscribers stay. Nothing is tied to our infrastructure.
When you connect your YouTube account, Google shows you a consent screen listing exactly what Klipr is asking for. Here's what each scope means in plain English:
| Scope | What it allows | Why Klipr needs it |
|---|---|---|
| youtube.upload | Upload videos to your channel | To post clips to YouTube Shorts on your behalf |
| youtube.readonly | Read video statistics (views, likes) on videos you own | To fetch view counts after 48 hours for the analytics dashboard and learning system |
✓ Klipr does not request access to delete videos, manage playlists, read your revenue or monetization data, access your subscribers list, read your private videos, or manage your channel settings. If a future version ever needs additional scopes, you will be prompted to re-authorize and can review exactly what changed.
Every file Klipr creates lives in your installation directory. Here's exactly what each one contains:
YouTube: Two options — either through Google's account permissions page, or by deleting the local token file.
Find Klipr in the list of connected apps
Click Remove Access — done instantly
Or simply delete token.json from your Klipr installation folder. The effect is immediate — Klipr loses all YouTube access on next launch and will prompt you to reconnect if you want to restore it.
When auto-upload is enabled, clip files are sent directly to YouTube via its official API. This goes straight from your PC to the platform — not through any Klipr server.
When AI headlines are enabled, the text transcript of a clip is sent to Groq's API to generate a title. This is plain text — no video, no audio, no personal data. Groq's privacy policy governs their handling.
On each launch, your license key is sent to our licensing provider to confirm it's valid. Only the key itself is transmitted — no personal data, no account info, no usage data.
48 hours after upload, Klipr queries the YouTube API to fetch view and like counts for clips it uploaded. This is a read request using your OAuth token — no data is sent out, only statistics are received back.