Privacy policy

Bitgate runs clipsdk and is responsible for the personal data described in this policy. You can reach us at kevin@bitgate.com.

The videos you send are a special case. You decide what is in them and what we do with them, so for personal data inside those videos, such as the faces and voices of the people speaking, you are the controller and we process it for you, on your instructions.

• Account data: the name and email address of the Google account you sign in with, and the workspace name you choose.
• Billing data: your top-ups with their amounts, dates and status, and your receipts. You pay on Stripe's checkout page, so your card details go to Stripe and never reach us.
• Usage data: your jobs, source minutes, clip counts and settings, and request logs with IP addresses and times.
• Content: the videos you upload or link, and what we make from them: clips, transcripts, captions, titles, scores and reasons.
• Messages: what you write when you email us.

• To run your jobs and your account, because that is our contract with you.
• To bill you and keep financial records, because of that contract and our legal duties.
• To keep the service secure, stop abuse and enforce limits, which is our legitimate interest in a safe service.
• To answer your questions and send emails about jobs, billing, security and changes, as part of our contract.

We do not sell personal data, we do not use it for advertising, and we do not use your videos or outputs to train AI models.

• Uploaded source videos and everything made from them: 7 days after they are created, then deleted.
• Request logs: 30 days.
• Account data: while your account is open. We delete it after you close the account, except what the law makes us keep.
• Billing records: 7 years, as Dutch tax law requires.
• Emails: as long as we need them to help you.

We use a small number of providers, under contracts that limit what they may do with the data:

• Cloudflare hosts the website, the API and the dashboard, stores uploaded videos and outputs, and runs the AI models that transcribe and rank your videos.
• Google runs the dashboard sign-in through Firebase Authentication and tells us your name and email address. We never see your Google password.
• Stripe processes top-ups and receives the details it needs to take a payment.
• Clicktag (clicktag.io), our own cookie-free analytics, counts visits to this website and a few steps in the dashboard.

Cloudflare runs a global network, so data may be processed outside the European Economic Area. Where that happens, we rely on safeguards the GDPR allows, such as the European Commission's standard contractual clauses. We share data with others only when the law requires it, for example under a court order.

This website sets one cookie, clipsdk_session. The dashboard sets it when you sign in with Google and it keeps you signed in for up to 30 days. Scripts can't read it, we use it for nothing else, and logging out ends the session. The login and signup pages load Google's sign-in scripts to open the Google window.

The website and the dashboard load one script from Clicktag so we can count visits and see which pages work. It sets no cookies and saves nothing in your browser's storage. For each page you open, it sends the page path, the site that sent you here, campaign tags such as utm_source, your browser's user agent, your screen and window size, language and time zone, and how long you stayed and how far you scrolled. The country in our reports comes from your time zone, not your IP address.

To count unique visitors, Clicktag hashes the UTC day, the site, your IP address, your user agent and a random salt that is replaced every UTC day and deleted when the day ends, so the hash can't follow you from one day to the next or from one site to another. To tell new visitors from returning ones, the script checks in with Clicktag about once a day and your browser's HTTP cache keeps the answer, which holds only the dates of your first and last visit to this site. If your browser sends Do Not Track, no pageviews or events are sent.

In the dashboard we also count a few steps as events: signing up or logging in, creating an API key, submitting clips, starting, finishing or canceling a top-up (with its amount), and your first job. Events never include your name, email address or order numbers.

The dashboard keeps a few small notes in your browser's local storage: whether you dismissed the getting started steps or sent a test webhook, the clip defaults you save in Settings, and which top-ups and first job it already counted, so a reload doesn't count them twice. They stay in that browser.

All traffic to clipsdk is encrypted. Access to personal data is limited to the people who need it to run the service, and content is deleted on the fixed schedule above. If a breach puts your data at risk, we will tell you and the authorities as the law requires.

Under the GDPR you can ask to see, correct, delete or export your personal data, or object to or limit how we use it. Email kevin@bitgate.com and we will answer within one month. You can also ask us to delete your videos and clips before the 7 days are up.

If you are not happy with our answer, you can complain to a data protection authority, such as the Dutch Autoriteit Persoonsgegevens.

clipsdk is not meant for anyone under 18, and we do not knowingly hold account data about children.

We post updates on this page and change the date at the top. For changes that matter, we email account holders before they apply. The terms of service cover the rest of how clipsdk works.