Privacy Policy

What we collect

• Waitlist signups — your email address, channel name, and survey answers (audience size, streaming hours, language, and optionally your editing tool).
• Account details from your sign-in provider (email address, and a username if set).
• A hash of your verified email address, normalized to match aliases, to prevent repeated free trials. The trial record tracks how many analysis hours you have used.
• Projects you sync to the cloud — metadata, transcripts, chat, and waveform data.
• Streams you upload or import to the cloud so ClipEZ can work on the footage, and the clips you trim from them — the video files themselves, kept under a per-account storage quota and removed after 30 days without use.
• Usage of cloud AI and transcription features — duration and request metadata, for quota and billing.
• Highlight feedback used to improve suggestions.
• Connected accounts you link — for Twitch, your username and the authorisation held by our sign-in provider; for a YouTube channel, your Google account ID and email address, the channel's ID and title, the permissions you granted, and the OAuth credentials that keep the connection working; for Kick, your user ID, name and email address when provided, channel handle, and the OAuth credentials for a linked channel.
• Product analytics and crash reports, such as page visits and feature use, which may be linked to your account. Mobile analytics is on by default and can be turned off in Settings; website choices are described in our Cookie Policy.
• Advertising measurement data, with your consent, as described below.

Cloud AI features

When you use cloud transcription, your project's audio is sent to Deepgram to be transcribed. When you use AI highlights or chapters, the transcript (and chat, if present) is sent to OpenAI or Google to generate suggestions. These providers process the content only to return results.

Streams you upload

We use cloud processing so that stream footage can be edited from clients that are not suited to handling the source recording. On the desktop, editing runs on your own machine unless you choose cloud features. On mobile, a recording of several gigabytes is rarely practical to store and process on the device, so an uploaded stream remains in our storage, the app streams it back while you select the fragment you want, and the trim is performed on our servers and returned to you as a clip. Browser editing uses this cloud storage and processing too.

We process uploaded video solely to provide these editing features. You can delete an uploaded stream, and the clips made from it, at any time from either app, and we remove a stream that has gone 30 days without use.

Connecting your Twitch account

Twitch is linked through Clerk, the sign-in provider we use, which holds the authorisation on our behalf — we never store Twitch credentials ourselves. With it we read your Twitch user ID and your past broadcasts, with their titles, thumbnails, dates, durations, and links, so the app can list the streams you can import. Your Twitch username is shown under Settings → Account so you can see what is connected.

The video and chat of a stream you import are downloaded from Twitch to your own computer, or to our servers when you choose a cloud import. Either way they reach our cloud storage only if you sync that project or upload the stream for editing from another device.

You can unlink Twitch at any time under Settings → Account, unless it is the only way you can sign in — connect another account or set a password first. Unlinking removes the authorisation, and deleting your ClipEZ account removes it too.

Connecting or signing in with Kick

Kick's consent screen lets us read your basic account and channel information. We use your Kick user ID to connect Kick to your ClipEZ account. If you sign up with Kick, we also send the email address Kick provides to Clerk to create and verify your ClipEZ account. Linking a channel stores its handle and an encrypted token so ClipEZ can keep the connection working. We do not receive your Kick password.

We show completed public recordings from your linked channel. You can also paste a public Kick recording link without connecting an account. When you import a recording, we fetch its video and replay chat. A desktop import is processed on your computer; a cloud import stores and processes the recording and chat on our servers as described above.

You can disconnect Kick under Settings → Account. We request revocation of its token and delete the linked channel details and stored credentials. The Kick user ID association stays with your ClipEZ account so Kick sign-in can still find it; deleting your ClipEZ account removes that association. You can also remove ClipEZ's access in your Kick account settings. We check linked grants daily and remove the channel connection when Kick rejects its token.

Connecting your YouTube channel

Linking a YouTube channel takes you through Google's consent screen, where ClipEZ asks for your basic Google profile (openid, email, profile) and read-only access to YouTube (youtube.readonly). Nothing we request can upload, edit, or delete anything on your channel.

With that access we read your Google account ID and email address, your channel's ID and title, and a list of your completed live broadcasts with their titles, thumbnails, publish dates, and durations. We store those details, and the OAuth credentials behind them, so the app can show your past streams and import the one you pick.

Data we receive from Google APIs is used only to provide the YouTube features you asked for. We do not sell it, use it for advertising, or send it to our AI providers, and we do not use it to develop, improve, or train generalised artificial intelligence or machine learning models. If you go on to analyse an imported stream, its audio and transcript are handled as described under Cloud AI features above.

You can disconnect the channel at any time under Settings → Account. We revoke the authorisation with Google and delete the stored credentials and channel details straight away, and deleting your ClipEZ account does the same. You can also revoke our access from the Google security settings page; if you revoke it there, we delete the YouTube data we hold for you within 30 days.

ClipEZ's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. The integration uses YouTube API Services, so the YouTube Terms of Service and the Google Privacy Policy also apply.

Why we use it and our legal basis

To provide and secure the service and process payments (performance of a contract), to manage the waitlist and contact you about access (your request prior to a contract), to improve the product (legitimate interests), and for advertising measurement (your consent). Our Cookie Policy explains when analytics need consent and how to change your choices.

Advertising measurement

With your consent, Google Ads, Reddit and TikTok help us measure whether our ads lead to visits, downloads and signups. They receive activity data, page URLs, ad identifiers, browser details and your IP address. We do not share your email, ClipEZ account ID or project contents for this purpose, or use Google remarketing.

On iOS, ClipEZ asks for Apple’s tracking permission before TikTok receives app install and app open events for ad measurement. If you decline, the TikTok SDK does not start. You can change this permission in iOS Settings. We do not send your account details, streams or transcripts; previously sent events cannot be recalled.

On the website, you can change advertising consent separately from analytics in Cookie preferences at any time.

Service providers and advertising partners

These providers help us run ClipEZ and measure our ads. Some process data on our behalf; others, including Google Ads, also act as independent controllers under their own privacy terms.

• Clerk — authentication, account management, and the waitlist.
• Stripe and Link — subscriptions and payments, including merchant of record services. They receive account and purchase details needed for checkout, tax, receipts, and billing support. We receive payment and subscription status, not your full card number.
• Apple — billing for plans and top-ups bought in the iOS app through the App Store. Apple is the merchant for those purchases; we receive the purchase and renewal status, never your payment details.
• Google — billing for plans and top-ups bought in the Android app through Google Play, and the Google Play services the Android app relies on to run. Google is the merchant for those purchases; we receive the purchase and renewal status, never your payment details.
• RevenueCat — validates App Store and Google Play receipts and reports subscription status for the iOS and Android apps (your ClipEZ user id and purchase history).
• Expo, Apple Push Notification service and Firebase Cloud Messaging (Google) — deliver the notifications you opt into in the mobile app. We store an Expo push token for the device, and Expo hands each notification to Apple on iOS or to Firebase Cloud Messaging on Android; the token is removed when you sign out or delete your account.
• Convex — application database and file storage.
• Deepgram — cloud transcription (audio, when you use it).
• OpenAI and Google — AI highlight and chapter generation (transcripts, when you use it).
• Vercel — website and API hosting (server logs include IP addresses).
• Cloudflare — hosting for app downloads and updates, storage of the stream and clip video you upload, and the servers that trim your clips.
• PostHog — product analytics.
• Reddit — advertising measurement with your consent.
• TikTok — mobile app install and app open measurement with your consent. See its Privacy Policy.
• Google Ads — advertising measurement with your consent. See how Google uses information from sites and apps and its Privacy Policy.

Some providers process data in the United States; transfers rely on their EU-approved safeguards (standard contractual clauses or an adequacy framework).

How we protect your data

We use technical and organisational measures designed to protect personal data against unauthorised access, disclosure, alteration, and loss. Traffic between the app, our servers, and the providers listed above is encrypted in transit, and the database and file storage we use encrypt data at rest.

Credentials for connected accounts get an extra layer. The access credentials behind a linked YouTube or Kick channel are encrypted before they are stored, with a key held only in our server environment and never in anything we ship to your device. They are decrypted only on our servers, at the moment we call the provider on your behalf, and they are kept out of our application logs, our product analytics, and the data export you can download.

Access to production data is limited to the systems that need it and to the operator of ClipEZ, and every request that reaches your data is authenticated against your signed-in session. No system can be completely secure, but we keep these safeguards proportionate to the data we hold, and we will notify affected users and the authorities of a personal data breach where the law requires it.

Your rights

You can access, export, and delete your data yourself under Settings → Account, in the app or on the web. Download your data exports everything we hold about you as a JSON file; Delete account permanently erases it, and our account deletion page sets out the steps and what each one erases. You can also email privacy@clipez.app to make either request. If you joined the waitlist without an account, email the same address and we'll remove your entry. You may also contact us to exercise any rights you have under applicable law, including access, correction, deletion, and objection.

Where we rely on your consent you can withdraw it at any time. If you think we have handled your data wrongly you can complain to your local data protection authority; ours is the Czech Office for Personal Data Protection (Úřad pro ochranu osobních údajů), uoou.gov.cz.

Retention

We keep your data while your account is active. Deleting your account erases your cloud data (synced projects, artifacts, uploaded streams and clips, usage, feedback, and connected accounts) and your waitlist entry with its survey answers. Cloud video removal runs after the account is deleted, and failed storage deletions are retried. Waitlist entries for people without an account are kept until we grant or decline access, or until you ask us to remove yours. Clerk, Stripe/Link, Apple and Google retain authentication and billing records under their own terms; payment records may be kept as long as tax and accounting law requires.

To prevent repeated free trials, we retain the normalized email hash after account deletion. This record contains no raw email address, account ID, projects, or usage history and is used only to check whether an email has already claimed a trial.

Disconnecting a connected account deletes its stored credentials and channel details and requests revocation of its authorisation with the provider. A Kick user ID association remains for sign-in until you delete your ClipEZ account or ask us to remove it.

Account deletion also requests removal of analytics linked to your account. Contact privacy@clipez.app for help with deletion requests.

Google, Reddit and TikTok retain measurement data under their own privacy terms. Withdrawing consent or deleting your ClipEZ account does not automatically erase that data; use their privacy controls or contact us for help.

Cookies

See our Cookie Policy for cookie uses, consent choices and withdrawal.

Changes

We may update this policy; material changes will be reflected by the date above.