Privacy Policy

1. Introduction

Klipr ("we," "our," or "us") is a desktop application that automatically detects viral moments in live streams and creates short-form video clips for upload to social media platforms. This Privacy Policy explains how Klipr collects, uses, stores, and protects information when you use our software.

By installing or using Klipr, you agree to the practices described in this Privacy Policy.

2. Information We Collect

2.1 Information You Provide Directly

• Account credentials and API keys — including YouTube OAuth tokens and any API keys you configure within the application. These are stored locally on your device only and are never transmitted to Klipr's servers.
• Configuration settings — your preferences, streamer lists, threshold settings, and other bot configuration data. Stored locally in a configuration file on your device.

2.2 Information Collected Automatically

• Stream audio and video — Klipr temporarily records segments of live streams you have configured it to monitor for the sole purpose of creating clips. These recordings are stored locally on your device. We do not transmit, store, or access this content on any remote server.
• Chat messages — Klipr reads public chat messages from Kick.com and Twitch.tv in real time solely to detect viewer engagement spikes. Individual chat messages are not stored, logged, or transmitted. Only aggregate scoring data is processed in memory.
• Clip metadata — titles, timestamps, and upload history are stored in a local history log on your device for your reference.

2.3 Information From Third-Party Services

• YouTube — When you connect your YouTube account, Klipr receives an OAuth access token to upload videos on your behalf. This token is stored locally. Klipr does not access any YouTube data beyond what is required to complete uploads.
• Groq API — When you enable automatic headline generation, the audio transcript of a clip is sent to Groq's API to generate a short title. No personally identifiable information is included. Groq's privacy policy governs how they handle this data.

2.4 Diagnostic Data (On by Default — You Can Turn This Off)

Klipr periodically sends a small diagnostic report to help us catch issues and understand how the app is performing, unless you disable this. This is controlled by the "Help Improve Klipr" toggle on the Settings page, which is checked by default. This report contains only:

• A one-way hashed device identifier (the same non-reversible hash used for license validation — not your name, IP address, or hardware serial numbers)
• Your Klipr app version
• Whether your license/subscription is currently active
• YouTube upload quota usage (numbers only, e.g. "3 of 6 used today")
• Whether initial setup (Google/Groq connection) has been completed
• The error code of the most recent upload failure, if any (e.g. "rate_limit_exceeded") — never the full error message or any content related to it

This report never includes clip video/audio, streamer names or URLs, chat content, file paths, OAuth tokens, API keys, or any other credentials. You can turn this off at any time by unchecking "Help Improve Klipr" in Settings and clicking Save — no further reports are sent once it's disabled. This describes the diagnostic report only — license verification is separate, is required, and is described in Section 5.4.

3. How We Use Your Information

Klipr uses the information described above solely for the following purposes:

• To detect viral moments in streams you have configured the application to monitor
• To cut, process, and save video clips to your local device
• To upload clips to your connected YouTube account when you have enabled this feature
• To generate AI-powered headlines for your clips when you have enabled this feature
• To maintain a local log of clips and uploads for your personal reference

We do not:

• Sell, rent, or share your information with any third parties for marketing purposes
• Access, view, or store your video clips on our servers
• Access your YouTube channel data beyond uploading videos
• Use your data to train AI models
• Transmit your configuration or credentials to any Klipr server

4. YouTube API Services

Klipr uses the YouTube API Services to upload clips to your YouTube channel. By using this feature, you also agree to YouTube's Terms of Service and Google's Privacy Policy.

Klipr's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Revoking YouTube Access

You can revoke Klipr's access to your YouTube account at any time by:

1. Visiting myaccount.google.com/permissions
2. Finding "Klipr" in the list of connected apps
3. Clicking "Remove Access"

You may also revoke access locally by deleting the token.json file in your Klipr installation directory.

5. Data Storage and Security

5.1 Local Storage

All data collected and processed by Klipr is stored exclusively on your local device. This includes:

• Your configuration file (config.py)
• YouTube OAuth token (token.json)
• Video clips and processed files (/clips folder)
• Upload history (upload_history.json)

You are responsible for the security of your local device. We recommend keeping your device secured and not sharing your Klipr installation directory with others.

5.2 Protection of Sensitive Data (OAuth Tokens)

Your YouTube OAuth access token is the most sensitive data Klipr handles, since it grants permission to act on your connected account. We protect this data as follows:

• Encryption in transit — All communication with Google's OAuth and API endpoints uses HTTPS/TLS encryption. Tokens are never sent over an unencrypted connection.
• No server-side storage — Klipr has no backend servers. Your tokens are never transmitted to, or stored on, any server operated by us. This eliminates the risk of your credentials being exposed through a breach of our infrastructure, because no such infrastructure holds them.
• Local file access control — Your token is stored only in a local file (token.json) inside your Klipr installation folder, protected by your operating system's standard file permissions — accessible only to your own Windows user account.
• Minimum necessary scope — Klipr requests only the narrow permissions required to upload videos and read upload statistics (youtube.upload, youtube.readonly) — never broader account, email, or contacts access.
• No token logging — Application logs record that an upload occurred, never the token value itself. Token contents are never printed, logged, or included in error reports.
• Instant revocation — You can revoke a token's access at any time, either from the platform's own account settings (see Section 4) or by deleting the local token file, which immediately and permanently removes Klipr's access.

5.3 Third-Party API Transmission

The only data that leaves your device is:

• Video files sent to YouTube when you upload a clip (via YouTube API)
• Clip audio transcripts sent to Groq's API for headline generation (when enabled)
• License verification requests sent to our licensing server to validate your Klipr license key
• The diagnostic report described in Section 2.4, unless you've turned it off

5.4 License Verification and Anti-Piracy

Klipr verifies your license key when it starts and periodically while it is running. This request is transmitted to our licensing provider (Gumroad) and to Klipr's own licensing service, and includes:

• Your license key and subscription status
• A one-way hashed identifier for your device
• Hardware serial numbers from your computer (disk drive, motherboard and processor)
• Your IP address, which is recorded by our server when the request arrives
• Your Klipr version

Why we collect this. A Klipr license is for one person. These details let us identify a single license being used across many computers, and block installations that share or resell license keys.

This is required and cannot be turned off while you are using a licensed copy of Klipr. It is separate from the optional diagnostic reporting described in Section 2.4, which you can disable at any time.

How long we keep it. These records are retained for 12 months. Where a license has been blocked for misuse, they are retained for as long as that block remains in force.

We do not sell this information, use it for advertising, or combine it with data obtained from other sources.

6. Third-Party Services

Klipr integrates with or depends on the following third-party services. Their respective privacy policies govern how they handle any data they receive:

Service	Purpose	Privacy Policy
YouTube (Google)	Video upload	policies.google.com/privacy
Groq	AI headline generation	groq.com/privacy-policy
Kick.com	Live stream chat monitoring	kick.com/privacy-policy
Twitch.tv	Live stream chat monitoring	twitch.tv/p/legal/privacy-notice
Gumroad	License verification	gumroad.com/privacy

7. Children's Privacy

Klipr is not directed at children under the age of 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided personal information through our software, please contact us and we will take steps to remove that information.

8. Your Rights

8.1 General Rights

• Access — You may request a copy of any data we hold about you (limited to license and purchase records, as all other data is stored locally on your device)
• Deletion — You may request deletion of your account and any associated records
• Correction — You may request correction of inaccurate data

8.2 European Users (GDPR)

If you are located in the European Economic Area, you have additional rights under the General Data Protection Regulation including the right to data portability and the right to lodge a complaint with a supervisory authority.

Our legal basis for processing data is legitimate interest (operating the software you have installed and paid for) and contractual necessity (fulfilling your license agreement).

8.3 California Users (CCPA)

California residents have the right to know what personal information is collected, the right to delete personal information, and the right to opt out of the sale of personal information. Klipr does not sell personal information.

9. Data Retention

Since all data is stored locally on your device, you control retention entirely. You may delete your clips, configuration, tokens, and history at any time by removing the relevant files from your Klipr installation directory.

Any data held by us (license records, and diagnostic reports unless you've disabled them) is retained for as long as your license is active and for a reasonable period thereafter for support and accounting purposes. You can stop future diagnostic reports at any time by disabling the toggle in Settings.

10. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of this page. Continued use of Klipr after changes are posted constitutes your acceptance of the updated policy.

11. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or your data, please contact us at:

Klipr is not affiliated with YouTube, Google, Twitch, Kick, or Anthropic.