REELCLIP PRIVACY
Privacy notice
This notice explains how Y.G.I. LLC handles information when you use ReelClip.
Effective date: November 7, 2026
Controller/service operator: Y.G.I. LLC
Privacy contact: [email protected]
What this notice covers
This notice covers the ReelClip website, account and license services, browser-based Web Studio, and desktop application. It does not replace the separate privacy policies of third-party services you choose, such as an AI provider, payment processor, publishing integration, or social network.
Information handled
- Account and sign-in: ReelClip’s account service uses your email address to send a one-time sign-in code. It stores a protected code hash with its creation, expiration, use, and attempt information; a keyed hash of the requesting IP address for abuse controls; and a keyed hash of the session token. Session records include expiration, creation, last-use, and revocation information. Resend delivers sign-in email; Cloudflare Workers and D1 host the account and license service.
- License and subscription: the account database stores account ID/email and license state. If you buy a subscription using Stripe Managed Payments, Sold through Link, LLC acts as merchant of record. ReelClip stores the payment-provider customer/subscription identifiers and plan, status, billing-period, cancellation, and event state needed to grant or end access. ReelClip does not store full payment card numbers.
- AI provider credentials: in the desktop app, OpenRouter and NVIDIA NIM keys are encrypted using operating-system-backed storage and sent from your computer to the selected provider. In Web Studio, an OpenRouter key stays in browser session storage and goes directly from the browser to OpenRouter. An NVIDIA NIM key stays in browser session storage and is sent in each request through ReelClip’s authenticated Worker to NVIDIA; the Worker forwards it for that request and does not save or intentionally log it. Remove either browser key in the Studio or close the tab to clear it.
- Media and AI requests: Web Studio opens a local video in your browser, applies a time selection and optional centered crop, and creates a browser-supported MP4 or WebM clip on your device. ReelClip does not upload or store the source video. OpenRouter BYOK captures up to ten minutes of audio and sends it directly to OpenRouter for transcription and highlight suggestions; ReelClip does not receive that key or media request. NVIDIA NIM captures up to five minutes of English audio, converts it to a WAV file in the browser, and sends it with the timestamped transcript through ReelClip’s Worker to NVIDIA Parakeet and Nemotron. ReelClip does not save the NVIDIA key, audio, or transcript; NVIDIA processes these requests under its terms and may bill or limit your NVIDIA account. Cloudflare Free AI sends captured audio and transcript through ReelClip’s account API to Cloudflare Workers AI. ReelClip records feature, model, audio duration, usage estimate, and request status for daily and monthly caps, and does not retain submitted audio or transcript after processing. Cloudflare’s daily free AI allowance is shared across the account and the service may pause at ReelClip’s caps or Cloudflare’s capacity limit. See OpenRouter’s transcription information, NVIDIA Parakeet API, and Cloudflare Workers AI pricing. AI suggestions may be inaccurate and should be reviewed. Creator AI is a capped, paid Cloudflare AI plan when checkout is available; the same shared daily capacity constraints apply. The desktop app is not yet available to customers.
- Publishing: if you connect publishing, the integration and social platform receive the account authorization, media, caption, and post details needed to carry out the action. ReelClip stores the optional Zernio integration credential locally in the desktop app’s settings and uses it from the main process.
- Website and security logs: Cloudflare processes IP address, request, and security metadata to deliver and protect the website and API. Workers Logs are sampled by the Worker configuration and may contain error details; the current configuration does not intentionally log passwords, sign-in codes, payment credentials, provider keys, or media. Cloudflare log and database recovery windows depend on the plan and product. The desktop app writes diagnostic logs to your device. The site uses first-party campaign measurement hosted in Cloudflare Workers and D1, as described below. It has no configured advertising pixels or third-party analytics SDK.
- Support messages: if you contact support, we receive the email address and information you choose to include. Please do not send passwords, API keys, payment details, or private media unless support specifically needs a safe example.
Campaign measurement and local edit settings
We use a random per-tab visit identifier, restricted campaign labels from marketing links, referral host labels, and milestone events (such as viewing pricing, choosing a plan, opening Checkout, and exporting a clip) to understand the purchase journey. On sign-in, campaign events can be linked to your internal account ID. Stripe Checkout and subscription metadata carry these labels so signed paid invoices can be associated with a campaign. Browser-reported events may be inaccurate; billing totals are gross paid invoices, not profit. We do not include email addresses, video names or content, transcripts, full referring URLs, provider keys, or card details in campaign events. Campaign tags should never contain personal information.
Campaign labels are saved locally for up to 30 days. Visit events and keyed IP hashes used to rate-limit event collection are retained for up to 90 days; paid-invoice attribution may be retained for up to 24 months. A signed-in deletion request removes linked visit events and unlinks retained attribution from your account. Historical anonymous visits cannot be linked for deletion if their visit identifier is no longer available. We honor Global Privacy Control and Do Not Track for campaign collection. You can also turn off campaign analytics below. Billing and account services continue to operate.
Saved projects contain source file identifiers (name, size, last-modified time), trim/framing choices, caption settings and any transcript you choose to save, held only in browser local storage. Brand presets are also stored only on your device. These records are not sent to ReelClip. Reopen the same video to resume; clearing browser storage or using Studio’s remove controls deletes these local settings.
Why information is used
We use information to authenticate you, send sign-in codes, issue and check licenses, administer subscriptions, provide the features you request, respond to support, prevent abuse, secure the Service, and meet legal obligations. We do not currently use the account service to send marketing messages.
Who receives information
We share information needed to operate the Service with Cloudflare for website, account, and (if enabled) Workers AI processing; Resend for sign-in email; and Stripe and Sold through Link, LLC for subscription checkout, payment, and transaction support. These providers handle information under their own terms and privacy notices. If you choose a publishing feature, your computer sends the request to the social platform you selected.
With OpenRouter BYOK in Web Studio, OpenRouter receives your key, audio, transcript, and highlight request directly from your browser. With NVIDIA NIM, ReelClip’s Worker receives the key and request over HTTPS only to forward them to NVIDIA; it does not save or intentionally log the key, audio, or transcript. With Cloudflare Free AI, Cloudflare receives audio and transcript data through ReelClip’s API, which records usage metadata for caps. Browser provider keys are held in session storage. Remove them in the Studio or close the tab to clear them.
Retention and deletion
We keep account information while your account is active. If you request account deletion, ReelClip deletes sign-in codes, sessions, AI job results, and usage rows, anonymizes the account record, and clears payment-provider identifiers from the active subscription record. A limited anonymized record remains so delayed signed payment events cannot restore deleted access. Processed payment event IDs are kept for up to 90 days. The active database may also be present in Cloudflare recovery history for up to 7 days on the Workers Free plan. Cloudflare Workers Logs are retained for up to 3 days on the Free plan. Stripe or Sold through Link, LLC may retain transaction records as required by their terms and law. We keep support email correspondence for up to 24 months after the issue is resolved, then delete it unless it must be retained for a legal, security, or dispute matter. ReelClip does not control provider-side or local device retention.
You can request deletion from the signed-in account page after entering your sign-in email. If you have a paid subscription, cancel it in the billing portal and wait until paid access ends before deleting the account. Files and logs stored on your computer are under your control; uninstalling the app may not remove settings or logs automatically.
Your privacy choices and rights
Depending on where you live, privacy law may let you request access to, correction of, or deletion of personal information, obtain a portable copy, or opt out of certain processing. You may also have the right to appeal a denied request or complain to your privacy regulator. Email [email protected] to make a request or appeal. We may ask for information needed to verify your request and will respond within the period required by applicable law. We do not sell personal information for money or use it for cross-context behavioral advertising.
Children and international use
ReelClip is offered to adults aged 18 or older who reside in the United States. It is not intended for children under 18 or people who reside outside the United States. If you believe a minor has created an account, contact [email protected] so we can review and take appropriate action.
Security
We use technical and organizational measures intended to protect account and service data, including hashed session credentials and one-time login codes. BYOK provider credentials are encrypted with operating-system-backed storage in the desktop app. No system can be guaranteed completely secure. If a security incident affects personal information, we will provide notices to affected people and authorities when applicable law requires them.
Changes and contact
We will update this notice when our data practices change and show a new effective date. We will provide notice of material changes by email or through the Service where required. Questions or privacy requests: [email protected].