ClipSparkSoft

Privacy Policy

Last updated September 20, 2026

Privacy commitments (read this first)

  • Your videos stay on your device. ClipSpark imports, transcribes, edits, and exports locally. We do not upload your video files to ClipSpark servers or other third-party clouds.
  • We do not collect extra personal privacy data. We do not collect contacts, precise location, ID numbers, card numbers, or browsing history, and we do not scan or upload other files from your disk.
  • Your account is only for Google sign-in. Google is used to prove who you are so you can log in and receive subscription entitlements. We do not read Google Drive, Gmail, YouTube, contacts, or other Google data.
  • We do not train models on your content. We will not use your videos, audio, or transcripts to train AI models.
Table of contents

1. Introduction

This Privacy Policy explains how we handle information when you use ClipSpark (the Windows desktop app, this website, and related services). The operator is Peng Zhang, an individual developer operating ClipSpark (“we”). Use of the service is also subject to the Terms of Service.

ClipSpark is built so that video stays local and the account is only used for Google sign-in. Except for the limited account and technical data listed here, we do not collect your personal privacy information to provide the service.

2. What we do not collect or upload

  • Video files: not uploaded to ClipSpark servers or sent to third-party clouds. Import, transcription, and editing run on your computer.
  • Transcription: local Whisper on your device only. We do not use cloud transcription and do not upload audio or video for that purpose.
  • Footage and project files: we do not collect, copy, or store your videos, project files, or exported clips to “improve the product” or for ads.
  • Extra identity data: no phone numbers, mailing addresses, government IDs, contacts, precise GPS, biometrics, or financial account numbers.
  • Other Google data: sign-in scopes are limited to identity (openid / email / profile). We do not request Drive, Gmail, Calendar, or YouTube content.

3. Limited information we process

To let you sign in and use subscriptions, we process only the following. This is not for advertising profiles or data sales.

Category Examples Source and purpose
Google sign-in identifiers Email, display name, Google / Firebase UID Email is handled by Firebase Auth (Google sign-in) and by Creem at checkout. Used to sign in, keep a session, bind subscription entitlements to the same account, and send service notices when practical. Not used for marketing profiles.
Subscription status Plan, status, subscription ID, Creem customer ID, renewal dates Returned by Creem so we can enable Pro and handle entitlements after failed charges or chargebacks. We do not store card numbers. Billing-related email is handled by Creem.
Usage and account preferences Videos processed and clips generated in the current period, period markers, and onboarding choices you save (for example creator role or platforms) Used for plan quotas and product onboarding. No video files.
Technical data (via processors) IP address, device or app version, request time, and similar Google, Firebase, Creem, Sentry, and similar processors may handle this during sign-in, payment, API calls, or crash diagnostics for security, billing, and troubleshooting. We do not build location or ad profiles and we do not collect browsing history.
Crash diagnostics (optional) App/OS version, stack traces, minidumps that may include memory snippets, UID after sign-in; email may be included after sign-in Sent to Sentry only when configured, to fix crashes. No video files.
Feedback you send Your description and an optional local log zip Leaves the device only after you click Send feedback. Logs do not include video by default.
AI analysis you start Transcript text (not video) Sent only when you click AI highlight analysis. Default: Google Gemini via ClipSpark’s proxy. If you add a DeepSeek key, it goes to DeepSeek. The video file stays on your device. We do not keep transcripts to train models or to build a content library. Model providers or cloud logs may keep short technical records under their own policies. Your account only increments usage counts; we do not store the video.

Local preferences (theme, transcription language, window layout) stay on your computer and are not uploaded as a personal profile.

4. How we use information

  • Complete Google sign-in and keep your session.
  • Recognize subscription status, quotas, and billing-portal access, including paid entitlements after failed charges or chargebacks.
  • Run AI highlight analysis when you request it (transcript only).
  • Handle support feedback and crash fixes when you trigger them.
  • Send service notices (for example price, Terms, Privacy Policy, or security updates). The website and in-app notices are the primary channels. If we can obtain an email from Firebase Auth or Creem, we will try to email you, but we do not guarantee every user will receive an email. We do not send marketing or advertising email.
  • Prevent abuse and fraud, protect the service, and enforce the Terms.
  • Comply with law (for example tax records or valid legal process).
  • Analyze de-identified or aggregated usage (for example how widely a feature is used) to improve the service. This does not include video files and cannot identify you.

We do not: sell personal information; train models on your videos or transcripts; give your content to ad networks; or use Google sign-in to scrape data beyond identity.

5. How we share information

We do not sell your personal information. To provide login, billing, and features you start yourself, we may share the minimum necessary information (never video files) with:

  • Google (OAuth) and Firebase Auth / Firestore / Cloud Functions (account and subscription status).
  • Creem (payments and tax; card data is handled by Creem). See the Creem Buyer Terms and Creem Privacy Notice.
  • Sentry (crash diagnostics, no video).
  • Resend (feedback or crash-alert email you or the system send).
  • When you start AI highlight analysis: by default we send transcript text only to Google Gemini through ClipSpark’s server proxy. If you enter your own DeepSeek API key in Settings, transcript text is sent from your device to DeepSeek; the key stays on your computer. That is a third-party service you choose to use.
  • Competent authorities where legally required.
  • Business transfer: if we merge, are acquired, sell assets, or wind down and transfer the service, necessary account and subscription data may transfer to the recipient, who must remain bound by this policy or equivalent protections.

6. Retention

  • Google sign-in identifiers and subscription status: while your account exists. After you delete your account, we stop using this data to provide the service. Email is handled by Firebase Auth and Creem, which may keep it for a period under their own policies and the law (for example tax). We cannot guarantee immediate, complete deletion from those third-party systems.
  • Crash diagnostics: kept only as needed to fix issues, then deleted or de-identified, and for no more than 90 days.
  • Feedback email and attachments: kept for support for no more than 90 days.
  • Local logs: kept on your device for the last 3 calendar days (including today) and purged when the app starts; they are not uploaded automatically. If you tap Send feedback, a recent log zip may be attached.

7. Local storage and cookies

This website uses browser localStorage to remember theme (light/dark) and language (zh/en). These are not advertising cookies, and we do not run ad or analytics pixels on the site.

Desktop settings stay on your machine. You can clear site data in the browser or reset settings in the app at any time.

8. Your rights and choices

Where GDPR, UK GDPR, CCPA, or Singapore PDPA apply, you may have the rights below. Before we act, we may need to verify your identity (for example the same Google account, or proof you control the relevant email). We will not discriminate against you for exercising these rights.

  • To know: what personal data we process, for what purposes, and with what types of processors.
  • Access and portability: a copy of personal data we hold about you, in a commonly used format where applicable.
  • Correction: correct inaccurate personal data.
  • Deletion: request deletion of personal data except where the law requires us to keep it (for example tax records). You may also request deletion of your ClipSpark account.
  • Restriction or objection: restrict or object to certain processing where the law allows.
  • Withdraw consent: where processing is based on consent, you may withdraw it; that does not affect processing already done.
  • Complain to a data-protection authority where you live.

We do not make decisions that produce legal or similarly significant effects based solely on automated processing (for example credit or employment decisions). Checking plan quotas is rule enforcement needed to provide the service, not that kind of decision.

For California residents: we do not sell personal information and we do not “share” it for cross-context behavioral advertising. We aim to respond within 30 days for EEA/UK requests and for requests from other regions. Appeals are described under Deletion and appeals below.

9. Children

The service is not directed to anyone under 18, and we do not knowingly collect personal information from children under 18. If we learn or have reason to suspect a user is under 18, we will look into it and, where appropriate, delete the related personal data and/or account. If you believe this has occurred, contact us.

10. International transfers

Processors such as Google, Firebase, Creem, and Sentry may handle login, subscription, or diagnostic data outside your country (for example in the United States or the EU). Video files are not transferred. For EEA/UK users, transfers rely on the European Commission’s Standard Contractual Clauses and each processor’s own transfer tools. We do not appoint a separate EEA/UK representative; send rights requests to clipsparkco@gmail.com.

11. Security

Keeping video on-device reduces cloud-leak risk by design. For account and subscription data we use reasonable access control and least privilege. No online service is perfectly secure.

12. Deletion and appeals

  • Deletion requests: clipsparkco@gmail.com, subject Data Deletion Request.
  • Privacy appeals: clipsparkco@gmail.com, subject Privacy Appeal.
  • Response target: 30 days for EEA/UK users and for requests from other regions.

13. Changes

We may update this policy and will change the date on this page. For material changes we will post a notice on the website and may show an in-app notice. The website and in-app notices are the primary channels. If we can obtain an email from Firebase Auth or Creem, we will try to email you, but we do not guarantee every user will receive an email. Unless mandatory law requires otherwise, continued use after an update means you have been informed of the revised policy.

14. Contact us

Operator: Peng Zhang, an individual developer operating ClipSpark
Address: China / Shandong / Qingdao
Support: clipsparkco@gmail.com
Legal: clipsparkco@gmail.com