npm run admin (site.config.json).Privacy Policy
ClipLabs is a video editor that runs in your web browser. This policy explains what happens to information when you use cliplabs.dev. It is written to meet the EU/UK GDPR, Türkiye’s Personal Data Protection Law No. 6698 (“KVKK”) and comparable laws.
1. Who is responsible
The data controller is [operator name (legal name of the person or company)], [postal address]. Contact: [contact e-mail address].
Users in Türkiye: please also read the KVKK Information Notice.
2. The short version
- Your videos, audio, images, project and settings are processed on your own device. We do not receive them and cannot see them.
- We do not use accounts, cookies, analytics, advertising or tracking.
- Like every website, our hosting provider sees your IP address and basic request data in server logs.
- Some features download AI models and runtime files directly from third-party servers (section 5).
- Only if you choose a cloud AI provider (Claude, Gemini, OpenAI) are your text commands and a text summary of your project sent to it, using your own API key (section 6).
3. What stays on your device
Your media files are stored in your browser’s IndexedDB. The project timeline, your settings (including any API keys you type in) and a few preferences are stored in localStorage. Downloaded AI models are kept in the browser’s cache and origin-private file system. None of this is sent to us. Because we have no access to it, we cannot recover it for you; export your finished videos and keep your own backups.
You can delete everything at any time with your browser’s “Clear site data” function. Details are on the Storage page.
4. Information we process, purposes and legal bases
| Information | Purpose | Legal basis | Retention |
|---|---|---|---|
| Server logs collected by our hosting provider ([hosting provider (e.g. Cloudflare, Inc.)]): IP address, date and time, requested URL, HTTP status, browser/user agent. | Delivering the website, security, abuse prevention, troubleshooting. | Legitimate interests (GDPR Art. 6(1)(f); KVKK Art. 5(2)(f)). | Up to 30 days, as configured with the provider. |
| Messages you send us (e-mail address and content). | Answering your request. | Legitimate interests / steps at your request (GDPR Art. 6(1)(b),(f)). | As long as needed to handle the request and a reasonable period afterwards for legal defence. |
We do not sell personal data, do not use it for advertising and do not make automated decisions about you.
5. Third parties your browser contacts directly
When you first use a feature that needs a model or runtime file, your browser downloads it from the servers below. Those servers see your IP address and browser details, but never your files. We set a strict referrer policy so they do not learn which page you were on, and our Content-Security-Policy limits where the page may connect.
- Hugging Face (huggingface.co and its download domains) — speech-recognition and text-to-speech model files (Whisper, Kokoro, Piper voices). Contacted the first time you use captions or voiceover. Privacy policy.
- jsDelivr (cdn.jsdelivr.net) and cdnjs (cdnjs.cloudflare.com, operated by Cloudflare) — open-source runtime files for face/background detection (MediaPipe) and for the Piper voice engine. jsDelivr policy · Cloudflare policy.
- Google Cloud Storage (storage.googleapis.com) — MediaPipe face-detection and person-segmentation model files. Privacy policy.
These providers act under their own privacy policies and may be located outside your country (for example in the United States).
The MediaPipe library contains an optional usage-metrics feature that would contact Google servers (odml.pa.googleapis.com). We block it with our Content-Security-Policy, so no such telemetry leaves your browser.
6. AI providers and servers you choose
Cloud AI (optional). If you select Claude (Anthropic), Gemini (Google) or OpenAI in Settings and enter your own API key, then each chat command is sent directly from your browser to that provider. It contains your typed command, a text summary of your project (track names, clip and file names, durations, caption text) and your API key as credential. Video, audio and image files are never sent. We do not see these requests. Their processing is governed by the provider’s terms and privacy policy (Anthropic, Google, OpenAI). Avoid putting personal data in file names or commands unless you accept this.
Local or self-hosted servers (optional). Ollama, LM Studio, Jan, ComfyUI, XTTS, Chatterbox and F5-TTS run on addresses you configure. Prompts and, for voice cloning, a short audio sample are sent to that server. If it is on your computer the data stays there; if you enter a remote address, the data goes to whoever operates it.
API keys are stored in clear text in your browser’s localStorage. Anyone with access to your browser profile can read them. Use restricted keys with spending limits and remove them on shared computers.
7. Voice cloning and biometric data
Voice recordings can be personal data and, in some jurisdictions, biometric data. Cloning is performed in your own environment; we never receive the recording. You are responsible for having the speaker’s permission and any legal basis required. The app asks you to confirm this before every cloning session. See also our Terms of Use.
8. Cookies and similar technologies
We do not set cookies. We use browser storage only to provide the functions you ask for (saving your project and preferences). The Storage page lists every item.
9. International transfers
Our hosting provider and the third parties in section 5 may process data in countries outside the EEA, the UK or Türkiye. Where the law requires it, transfers rely on adequacy decisions, standard contractual clauses or equivalent safeguards provided by those parties (for Türkiye: KVKK Art. 9).
10. Your rights
Depending on where you live you may have the right to access, correct, delete or restrict the use of your personal data, to object to processing, to data portability, and to complain to a supervisory authority. In Türkiye these rights are set out in KVKK Art. 11 (see the KVKK notice); in the EU/UK you can contact your national data-protection authority; in California, we do not sell or share personal information.
To exercise a right, e-mail [contact e-mail address]. Server logs may not identify you, so we may ask for details such as your approximate access time and IP address.
11. Children
ClipLabs is not directed at children under 16. If you are under 16 (or the age of digital consent in your country), use it only with a parent’s or guardian’s permission.
12. Security
The site is served over HTTPS with a strict Content-Security-Policy and other security headers. Your content is not stored on our servers, which removes the largest risk. No method is perfectly secure; please protect your device and API keys.
13. Changes
We may update this policy. The date at the top shows the latest version; material changes will be announced on the site.
14. Contact
[operator name (legal name of the person or company)] · [postal address] · [contact e-mail address]