1. Who we are
ClippingPilot (“ClippingPilot”, “we”, “us”) is operated by ClippingPilot, 16192 Coastal Hwy, Lewes, DE 19958, USA. We are the controller of the personal data described in this policy. You can reach us at [email protected].
2. Data we collect
Account data
- Name and email address when you sign up.
- Password, if you sign up with one. We store only a salted hash, never the password itself.
- Social sign-in identifiers if you choose to sign in with Google, GitHub or Discord: the provider name and your account ID with that provider, plus the name, email and profile picture they share with us.
- Passkeys, if you add one: the passkey’s public key and a name for it. Your device keeps the private key.
- Profile picture, if you upload one.
- Account status: whether your email is verified, your plan, when the account was created and when it was last active.
- One-time codes for email verification, magic-link sign-in and password resets. They expire after about 30 minutes.
Workspaces, videos and clips
- Workspaces: the names you choose and the videos organized in each workspace.
- The YouTube or Vimeo links you submit, the video ID, how many clips you asked for and the processing status of each video.
- What we produce from them: the clips (MP4 files), clip titles, timestamps, scores, hook lines and the reasons each clip was picked, the AI analysis, and a timestamped transcript of the video’s speech when one is available. A transcript can contain personal data spoken in the video.
Billing data
When you start a Basic or Pro subscription, Stripe collects payment details directly. We do not store your full card number. We store the customer and subscription IDs, subscription status and billing dates needed to manage an actual subscription.
Usage and technical data
- IP address, used to rate-limit sign-in and sign-up attempts and protect accounts. Rate-limit records are short-lived.
- Approximate location (city and country) that our hosting provider, Cloudflare, derives from your IP address. We use it in sign-in notification emails so you can spot a sign-in that wasn’t you.
- Server logs kept by our hosting provider, such as request times, IP addresses and error details, used for security and troubleshooting.
- Product analytics collected with PostHog: the pages you visit, the buttons and links you click, product events (for example pasting a link, opening a pricing plan, submitting a video or downloading a clip), page performance, errors, device and browser details, and approximate location from your IP address. If you’re signed in, these are linked to your account ID, name and email.
- Session replays: PostHog records how pages render and respond while you use our website (mouse movement, clicks, scrolling and page changes) so we can find bugs and confusing screens. Everything typed into form fields is masked in the browser before it’s sent, including passwords and email addresses.
Messages you send us
If you email support or send feedback in the app, we keep your message, our reply and your contact details.
3. How we use your data
- To create and secure your account, sign you in and verify your email.
- To process the videos you submit: fetch the video, transcribe it, pick and cut clips, and store the results for you to preview and download.
- To track your current plan and admitted video usage. Minute credits and automatic failed-run credits are proposed features, not current processing.
- To send service emails: verification codes, sign-in links and codes, password resets, sign-in notifications and important account or billing notices.
- To understand how people use our website and app, fix bugs and improve the product (product analytics and session replays).
- To answer support requests and feedback.
- To prevent abuse, fraud and security incidents, and to enforce our Terms of Service.
- To meet legal, tax and accounting obligations.
We don’t sell your personal data, we don’t use it for advertising, and we don’t use your videos, clips or transcripts to train AI models.
4. Legal bases (EEA, UK and Switzerland)
If GDPR or UK GDPR applies to you, we rely on these legal bases:
- Contract: to provide the service you signed up for, including account, video processing, usage and any enabled billing.
- Legitimate interests: to keep the service secure (rate limits, sign-in alerts, logs), prevent abuse, improve reliability, and understand how the product is used so we can improve it (analytics and session replays). We balance these against your rights.
- Legal obligation: to keep records required by tax and accounting law and to respond to lawful requests.
- Consent: where we ask for it, for example for optional marketing emails. You can withdraw consent at any time.
5. Sharing and subprocessors
We share personal data only with service providers that help us run ClippingPilot, under contracts that limit how they use it, or when the law requires it.
| Provider | What they do | Data involved |
|---|---|---|
| Cloudflare | Hosting, database (D1), file storage (R2), background processing and network security | All account, video and clip data; IP addresses and request logs |
| Contabo | Hosting our default video processing engine | Submitted source video and audio, transcripts, analysis and rendered clips |
| Google Gemini | Highlight selection and visual analysis for our engine | Transcript text and selected video frames needed for analysis |
| MuAPI (muapi.ai), when explicitly enabled | Alternative video processing provider | The submitted YouTube link, video and audio, transcript and clips for videos assigned to that provider |
| Resend | Sending service emails | Your name, email address, and the email contents (for example a sign-in code) |
| Stripe, for enabled subscription checkout | Payments and subscription management | Email, customer and subscription identifiers, and payment information you give Stripe |
| Google, GitHub, Discord | Social sign-in, only if you choose it | Account identifiers and profile details the provider shares |
| Google Tag Manager, Google Analytics | Understanding how visitors use our website so we can improve it | Pages visited, clicks and events, device and browser details, approximate location, and cookie identifiers |
| PostHog (US Cloud) | Product analytics, session replays (with form inputs masked), heatmaps, page-performance and error tracking | Pages visited, clicks and product events, page performance and errors, device and browser details, approximate location from your IP address, and your account ID, name and email if you’re signed in |
| Google Fonts, Fontshare | Serving the fonts our website uses | Your IP address and browser details when your browser downloads the fonts |
Videos are fetched from YouTube or Vimeo, whose own terms and privacy policies apply to the content hosted there. We may also disclose data if required by law, to protect our rights or users’ safety, or as part of a merger, acquisition or sale of assets, in which case this policy continues to apply to your data.
6. Cookies and local storage
We use cookies that are needed for the service to work:
- Session cookie (
nuxt-session): keeps you signed in. It’s encrypted and can’t be read by scripts on the page. - Short-lived security cookies set during social sign-in to protect the sign-in flow.
Because these cookies are strictly necessary, we don’t ask for consent to them. Blocking them will stop you from signing in.
We also use Google Tag Manager to load analytics tools such as Google Analytics, which set cookies (for example _ga) to measure visits and how our website is used. You can block these cookies in your browser settings or with an extension, or opt out of Google Analytics with Google’s opt-out add-on. Blocking them won’t affect how the service works.
We use PostHog for product analytics and session replays. PostHog stores an anonymous visitor ID and settings in a first-party cookie and in your browser’s local storage, both with names starting with ph_ (for example ph_phc_…_posthog), so it can tell visits from the same browser apart. Requests to PostHog go through our own domain (/ingest). When you sign out, the visitor ID is reset. You can clear or block these with your browser settings or an extension; this won’t affect how the service works.
7. How long we keep data
- Account data: for as long as your account is open. After you delete your account, we delete it within 30 days, except where we must keep it for legal reasons.
- Clips and transcripts: stored privately for your workspace until removed through account or content deletion. The 30-day and 90-day retention tiers in the pricing preview are proposals and are not active expiry policies. Download copies you want to keep.
- Video records (link, status, clip titles and reasons): while your account is open, so you can see your history.
- One-time codes and rate-limit records: minutes to hours, until they expire.
- Billing records: as long as tax and accounting law requires. Stripe keeps its own payment records for any enabled checkout.
- Backups and logs: deleted data can stay in backups or provider logs for a limited period, usually up to 30 days, before it is overwritten.
8. Your rights
Depending on where you live, you can ask us to:
- access the personal data we hold about you and get a copy;
- correct data that is wrong or incomplete;
- delete your data;
- restrict or object to certain processing, including processing based on legitimate interests;
- receive your data in a portable format;
- withdraw consent you gave us.
EEA and UK residents can also complain to their local data protection authority.
California residents (CCPA/CPRA) have the right to know what personal information we collect, use and disclose, to delete it, to correct it, and not to be discriminated against for exercising these rights. We don’t sell personal information or share it for cross-context behavioral advertising. You can use an authorized agent to make a request.
To make a request, email [email protected] from the address on your account. We may need to verify your identity, and we reply within 30 days (45 days where the CCPA allows).
9. Deleting your account
Open Account Settings to delete your account, videos, clips and transcripts. Deleting your account ends any active subscription immediately. We keep records required by law, such as billing records. You can also email [email protected] from your account’s email address to request deletion.
10. International transfers
Our providers, including Cloudflare, Contabo, Google Gemini, Resend, Stripe, PostHog (whose US Cloud we use) and MuAPI when enabled, may process data in the United States and other countries outside your own. Where data from the EEA, UK or Switzerland is transferred to countries without an adequacy decision, we rely on safeguards such as the European Commission’s Standard Contractual Clauses or the EU–US Data Privacy Framework, where the provider participates.
11. Children
ClippingPilot isn’t meant for children. You must be at least 16 years old to use it (or 13 in the United States, where permitted, with any consent your local law requires). We don’t knowingly collect data from children below these ages. If you believe a child has given us personal data, contact us and we’ll delete it.
12. Security
We use encrypted connections (HTTPS), hashed passwords, encrypted session cookies, short-lived one-time codes, rate limits on sign-in, and private storage for your clips, which only your account can access. No system is perfectly secure, so please use a strong, unique password or a passkey. If we learn of a breach that affects your data, we’ll notify you and the authorities as the law requires.
13. Changes to this policy
We may update this policy as the service changes. We’ll change the effective date above, and if the changes are significant we’ll tell you by email or in the app before they take effect.
14. Contact
Questions or requests: [email protected].
ClippingPilot, 16192 Coastal Hwy, Lewes, DE 19958, USA.