Desktop Mac and Windows On-device processing You control the AI bill
Free cost calculator · Lifetime $199
Clippingli Clippingli Local

Legal

Privacy Policy

Clippingli is local-first for master video. We collect what we need to sell a license, run this site, and answer support. Clippingli is the controller. There is no other company and no office address.

Last updated: 12 September 2026. Controller: Clippingli. Contact: privacy@clippingli.com.

1. Who we are

This policy covers clippingli.com (and the same site at dealzinn.com/clipforge) and the Clippingli desktop app. Clippingli is the seller and the data controller. There is no parent company, subsidiary, or other legal entity behind Clippingli. There is no registered office or street address. Privacy contact: privacy@clippingli.com. We operate from Karachi, Pakistan.

This policy does not cover OpenAI, YouTube, AWS as a processor’s own marketing, payment processors’ card vaults, or other third parties you choose to use. Those parties have their own policies.

Related documents: Terms of Use and Refund Policy. If this policy conflicts with the Terms on personal data, this policy controls.

2. What stays on your machine

Source video, captions, and exports are processed and stored on your computer unless you upload them somewhere else. Your OpenAI (or other AI) API key is stored only on that machine. We do not need that key on our servers for normal clipping.

“Local-first” and “the master is not uploaded to us for render” mean we do not take your source file onto a Clippingli render farm. They do not mean nothing ever leaves the device. License checks, optional telemetry, optional agency previews, updates, and AI features (to the provider you configured) do send some data, as below.

3. What we collect

Purchases

When you buy, we receive the buyer email, name if provided, amount/currency if the processor sends it, and a transaction or invoice id so we can issue a key, show it in Admin, refund, and stop abuse. If a payment processor collects the card, they handle card data. We do not want full card numbers on our server.

License checks

The app may confirm the license with us from time to time. That can include the license key and a device identifier so we can activate, block refunded or abused keys, and see last seen time.

Desktop telemetry (jobs)

After a job, the app may send limited usage data (not your master video) so we can support the product and blocked keys. You can turn this off in the app if that option is present.

Installer downloads

Platform (Mac or Windows), time, user-agent, referrer, IP address, and optional source/license fields. Used to count demand and unique downloaders.

Website analytics (first-party only)

Cookies cl_vid (about 400 days) and cl_sid (about 30 minutes). We record page path, title, referrer, language, approximate OS/browser/device, engaged time on a visible tab (capped), download and buy clicks, IP address, and approximate country (CDN header or an IP lookup). We use this in Admin for traffic and abuse. We do not use Google Analytics or ad pixels.

Contact and desk chat

Name, email, and the message you type, plus IP and user-agent. Stored on our host so we can reply in Admin. This site does not use tawk.to.

Waitlist and lead forms

If you ask us to email an installer, a cost brief, or a checkout link: email, Mac or Windows if you choose it, source of the form, optional first-party visitor id, the brief you asked us to send, IP, user-agent, and time. We use this to send that mail and to see which pages led to a license.

Agency preview (optional)

If you create a preview link: preview video files, titles, client name you enter, comments, and a secret token. The source timeline stays on the editor machine. Links are unlisted: anyone with the URL token can watch. Default expiry is 14 days unless you set another period. We may delete files after expiry, when you close the review, or if you ask us to.

Updates and diagnostics

The app may check our update feed. Support mail may include OS version, app version, and error text you paste. Do not paste secrets or API keys.

4. What we do not collect on our servers

  • Your OpenAI API key (it stays on that computer)
  • Your master video for clipping on our servers
  • Full card numbers (the processor holds those when checkout is used)

5. Why we use it

  • Activate, enforce, refund, and revoke licenses
  • Serve installers and updates
  • Understand which pages and downloaders the site has, and reduce abuse
  • Answer support and operate agency preview if you use it
  • Meet accounting and legal duties

Legal bases (where GDPR/UK GDPR apply): contract (license, support), legitimate interests (security, analytics, product operations), consent where we must have it, and legal obligation (tax, disputes). We do not sell personal information. We do not run third-party advertising cookies on this site.

6. AI providers - data that leaves the device to them, not to us as the AI vendor

When you use features that call OpenAI (or another API you configure), the call is made from your computer with your key. We do not operate that API. We do not mark up their tokens as a Clippingli plan. You can stop those calls by not using those features and by removing the key in Settings. The provider’s own privacy policy and terms apply to what they receive.

Those features send the audio and text they need to the provider. They do not send your master video to Clippingli for clipping.

We do not send your OpenAI key to our servers for ordinary clipping. We do not upload the master video file to Clippingli for clipping. Optional agency preview uploads go to our host, not to OpenAI, and are separate (Section 3).

See the OpenAI key guide and Terms, Section 14.

7. Processors and other parties

  • Amazon Web Services - hosting this website, Admin, installers, preview files, inbox, and license database (regions include EU Stockholm for this site)
  • Resend - license and operational email when configured
  • Payment processor - checkout and payouts, when online checkout is enabled
  • ip-api or a CDN country header - approximate country for analytics
  • OpenAI or another AI API - only with your key, from your machine
  • YouTube or other sites - only if you paste a URL into the app, under their terms
  • YouTube embeds on the homepage showcase - only if you play a clip, under YouTube's terms

The public website uses our own form and chat widget, not a third-party live-chat vendor.

8. Cookies

The desktop app is not a cookie store. This website sets first-party cookies cl_vid and cl_sid so we can count unique visitors and engaged time. Contact/chat store what you send on our server; those are not advertising cookies. Playing a homepage showcase clip loads YouTube, which may set its own cookies. You can block cookies in the browser. Downloads still work. Unique-visitor counts will be less accurate.

9. Retention

  • Local files: until you delete them or uninstall.
  • License and order records: while the license is useful for support, refunds, and abuse prevention, then a reasonable accounting period.
  • Site analytics and download logs: to operate the desk; we may aggregate or delete older rows.
  • Contact threads: as needed to reply and meet legal duties. You can ask us to delete a support thread.
  • Waitlist: until launch notice is sent or you ask to be removed, then as needed for proof of notice.
  • Agency previews: until the link expires, you close the review, you ask us to delete, or we discontinue the feature. Default 14 days.

10. Security

We use measures appropriate to a small desktop product and a first-party site (HTTPS, access-controlled Admin, token-gated previews). No host is perfect. You are responsible for the machine, OS accounts, who can open the app, and how you share preview links.

11. International transfers

We operate from Pakistan. Hosting, email, analytics lookups, and AI APIs may run in other countries (including the EU and the United States). Those countries may have different data-protection laws. Where required, we rely on the transfer tools used by us or those vendors (for example the processor’s standard contractual clauses).

12. Your rights

You can delete local jobs in the app, remove your API key in Settings, and uninstall. If you are in the EEA, UK, California, or a similar regime, you may have rights to access, correct, delete, or restrict personal data we hold, to object to some processing, and (where applicable) to portability. Email privacy@clippingli.com. You may also complain to a supervisory authority. We will need enough information to find your records (usually the purchase email).

13. Children

The site and the app are not directed at children under 16, or the higher minimum age in your country. We do not knowingly collect children’s data. Buyers must have capacity to contract. If a child sent us data, write to privacy@clippingli.com and we will delete what we reasonably can.

14. Changes

We may update this policy. The “Last updated” date will change. For a material change we will note it here and, where practical, in the app or by email to the address on the license.

15. Contact

Privacy: privacy@clippingli.com. Support: support@clippingli.com. Legal: legal@clippingli.com. Or Contact.