This Privacy Policy explains how Klipgen collects, uses, shares and protects personal data when you use https://klipgen.ai (the "Service"). It is written to meet the requirements of the Personal Data Protection Act B.E. 2562 (2019) of Thailand ("PDPA").
1. Who is responsible for your data
1.1 The data controller is Klipgen, an online service operated by a sole proprietor in Thailand ("Klipgen", "we", "us").
1.2 Contact: email support@klipgen.ai. This is our only contact channel, for privacy questions and for requests to exercise your rights.
1.3 If you need our full identifying details to exercise your rights, or the Office of the Personal Data Protection Committee requires them, we will provide them on request to the extent the law requires.
2. Scope
2.1 This Policy covers personal data about:
- people who visit our website;
- users of the Service; and
- people who contact us.
2.2 It does not cover third-party services you reach through links. Those services have their own policies.
3. Personal data we collect
3.1 Account data, from Google sign-in. We offer sign-in through Google only. When you sign in, Google gives us:
- your name;
- your email address;
- your profile picture link;
- whether your email is verified; and
- your Google account identifier.
We request only the basic "openid", "email" and "profile" permissions. To keep your sign-in linked, we also store the sign-in tokens Google issues.
3.2 Session and technical data.
- When you are signed in, we keep a session record containing a session token, your IP address, your browser's user-agent string and timestamps.
- Our hosting provider records server logs. These include the request, its time, your IP address and browser information, request identifiers, and for errors, your user, project and request identifiers.
3.3 Your content. Your content includes:
- the files you upload (video, audio, images and documents, with their file names);
- your chat messages to the AI editor;
- notes and instruction files written by you or the AI editor;
- project titles, timelines; and
- the previews and exports rendered for you.
Your content may contain personal data about you and other people, such as faces, voices, names, spoken words and text in images or documents.
3.4 Data derived from your content. To edit with your material, the Service analyses it. The analysis produces:
- speech transcripts with word-level timings;
- still frames sampled from video;
- smaller working copies of videos and images;
- AI-written descriptions of scenes, settings and the people visible;
- any text visible in images;
- mood, genre and voice descriptions of audio;
- loudness, beat and level measurements;
- a short AI-written summary and tags for each file;
- page counts or extracted text of documents; and
- the positions of faces and heads in video frames, used to frame shots, for example to keep a speaker centred when reframing.
Face and head detection only locates where a face or head is in the frame. It does not identify who a person is. We do not perform facial recognition and we do not create biometric templates or identifiers.
3.5 AI interaction records. For each step the AI editor takes, we keep:
- the model's reply;
- the tools it used, with their inputs and results;
- token counts and timing; and
- a fingerprint of the request.
These records let you see your project's history and let us run, bill and troubleshoot the Service.
3.6 Billing data. Billing data includes:
- your plan, subscription status and billing periods, and when you accepted the automatic monthly charge;
- top-up purchases;
- the payment method type, and your bank's name if you paid by mobile banking;
- identifiers issued by our payment processor (charge, customer and schedule identifiers), or, for a bank transfer, the bank's transaction reference printed on the slip, with the amount and date of the transfer. We do not store the slip picture you upload: it is sent to EasySlip to be checked (Section 6);
- your credit ledger, which shows credits granted, reserved, spent, expired and revoked;
- whether each payment receipt was emailed to you;
- daily usage counters; and
- in-app notifications.
We do not receive or store your full card number or security code. You enter your card details directly into our payment processor's form.
3.7 Communications. When you email us, we keep your email address, the content of your messages and our replies. If you ask for a refund by bank transfer, we also keep the bank account details you give us.
3.8 Browser storage. Your browser stores interface preferences locally, as described in Section 11.
4. Why we use your data and our lawful basis
| Purpose | Data used | Lawful basis under the PDPA |
|---|---|---|
| Create your account, sign you in and keep you signed in | Account data; session data | Performance of our contract with you (s.24(3)) |
| Provide the Service: store, analyse, transcribe, edit and render your material, and run the AI editor | Your content; derived data; AI interaction records | Performance of contract (s.24(3)) |
| Process payments, subscriptions and renewals; grant, reserve, charge, expire and revoke credits | Billing data; account data | Performance of contract (s.24(3)) |
| Email you a receipt after each payment | Billing data; account data (your email address) | Performance of contract (s.24(3)); legal obligation (s.24(6)) |
| Keep financial and transaction records | Billing data | Legal obligation (s.24(6)); legitimate interests (s.24(5)) |
| Answer support, refund, cancellation and data-protection requests | Communications; account and billing data | Performance of contract (s.24(3)); legal obligation (s.24(6)) |
| Keep the Service secure; prevent fraud, abuse and multiple-account misuse; enforce our Terms | Session and technical data; account, billing and usage data; content when needed for a specific investigation | Legitimate interests (s.24(5)) in protecting our users and the Service |
| Operate, monitor, troubleshoot and control the cost of the Service | Server logs; AI interaction records; AI request logs (Section 6) | Legitimate interests (s.24(5)) in running a reliable Service |
| Establish, exercise or defend legal claims; comply with lawful requests from authorities | Any relevant data | Legal obligation (s.24(6)); legitimate interests (s.24(5)) |
4.1 Consent. We do not rely on consent for any of the purposes above. We do not send marketing emails. Besides replies to your messages, the only emails we send are the payment receipts described in Section 4. If we ever want to use your data in a way that requires consent, we will ask for it first, and you can withdraw it at any time.
4.2 If you do not provide data. Account data and the data needed to process your content and payments are required to provide the Service. Without them, we cannot provide it.
4.3 Sensitive data. We do not intend to collect sensitive personal data, such as health, religious or biometric data. If you choose to upload content that contains it, we process that content only to provide the Service you requested. Please do not upload it unless you need to.
5. How AI processes your content
5.1 Klipgen's editing is performed by AI. When you upload material or chat with the AI editor:
- your material is sent to AI providers to be analysed, for example transcribed and described; and
- the AI editor's model receives what it needs to edit. This includes your messages, your notes, the names, summaries and tags of your files, transcripts, still frames, images, documents, frames rendered from your project and timeline data.
5.2 We do not send your name or email address to the AI providers.
5.3 The AI's decisions are editing decisions about your video, such as which clips, captions and timing to use. They do not produce decisions about you that have legal or similarly significant effects.
6. Who receives your data
We do not sell or rent your personal data. We share it only with the following service providers, which process it for us so that we can provide the Service, and as described in Section 6.2.
| Recipient | Role | What it receives |
|---|---|---|
| Cloudflare, Inc. | Hosting, application servers, databases, file storage, content delivery, logging and email delivery (sending the payment receipts we email you) | All data described in Section 3 that we store, including uploads, derived data, projects, account and billing records, and server logs; and your email address and the content of those receipts. Cloudflare's AI Gateway also logs the requests and responses of the AI model calls we make (chat, transcripts, analysis), for operational and cost monitoring. |
| Anthropic, PBC | The AI editor's model (Claude) | The material listed in Section 5.1. PDF documents are uploaded to Anthropic's file storage so the AI editor can read them. They stay there until your account is erased (Section 8.1). |
| Google LLC | Sign-in (Google OAuth); media analysis (Gemini API); web fonts | Sign-in: the authentication exchange. Gemini: a reduced-resolution copy of each video with its audio, audio files, a reduced-size copy of each image, PDF documents and the text of text documents. Each file we place in Google's file store is deleted right after its analysis is done. Fonts: see Section 11. |
| Speechmatics | Speech transcription | Audio, or the reduced-resolution video copy, of material that contains speech. Speechmatics fetches it through a temporary link that expires after 24 hours, and processes it in its EU region. We delete each transcription job, with the audio Speechmatics fetched and the transcript, as soon as we have the transcript. A job whose result never reaches us is deleted by Speechmatics automatically after 7 days. |
| Modal, Inc. | Rendering previews and exports on GPU machines | For each preview or export it renders: the render job, which holds its identifiers and where its files are kept in our file storage, and the project's compiled timeline, which can include your captions and other text shown in the video; and, read from our file storage for that job, the working copies of your videos and the audio, images and motion scenes the timeline uses. The rendered video is written back to our file storage. Modal keeps none of your content after the job: the files stay only on the temporary disk of the machine that rendered them, which keeps them for further renders only while it runs and is shut down, erasing that disk, 2 minutes after its last render. Modal keeps each job's identifier and the machines' technical logs under its own retention. |
| EasySlip Co., Ltd. (Thailand) | Checking the slip of a bank transfer you pay a top-up with | The picture of the slip you upload. A slip shows the sender's and the receiver's names, their banks and account references, the amount, the date and the bank's transaction reference. EasySlip reads the slip, checks it with the bank and tells us whether it is genuine, new, paid to our account and for the right amount. We send no other data about you. EasySlip's privacy policy gives no fixed period for keeping slip images or verification data: it keeps them for as long as it provides its service to us or as needed for its purposes and then deletes or anonymises them; we cannot delete them for you, and you can ask EasySlip directly. |
| Opn Payments (Omise) | Payment processing, when card payments are offered | Your card details, entered directly into Omise's form. For subscriptions, your email address, your Klipgen user identifier and your saved card, in a customer record we delete when you delete your account. For each charge, its amount, description, payment method and your Klipgen user identifier. |
6.1 Content-delivery providers. Some images and videos on our marketing pages are loaded from other companies' content delivery networks. When your browser loads them, those providers receive your IP address and browser information.
6.2 Other disclosures. We may disclose personal data:
- to competent authorities, when Thai law or a lawful order requires it;
- to protect the rights, safety or property of our users, the public or Klipgen; and
- to a successor that takes over the Service, which must then protect your data as described in this Policy.
7. International transfers
7.1 Several of our providers process data outside Thailand:
- Cloudflare operates a global network. We ask it to place our main database and our file storage in the Asia-Pacific region, but this is a placement preference, not a guarantee. Other parts of the Service, such as the storage of each project and account, may run in any Cloudflare location.
- Anthropic, Google and Modal process data in the United States and other countries.
- Speechmatics processes data in the European Union.
7.2 We transfer personal data abroad under sections 28 and 29 of the PDPA:
- where the transfer is necessary to perform our contract with you, that is, to provide the Service you asked for (s.28); and
- on the basis of the safeguards in these providers' data-processing terms, which bind them to protect personal data and use it only to provide their services (s.29).
7.3 You can ask us for more information about these safeguards by email.
8. How long we keep data
| Data | Retention |
|---|---|
| Account data and Google sign-in tokens | While your account is open. Erased when your account is erased, about 7 days after you delete it (Section 8.1). |
| Sessions | A session ends after 30 days without use, and is renewed daily while you use it. Signing out deletes the session. Deleting your account deletes every session at once. The temporary sign-in record lasts at most 10 minutes. |
| Uploads, derived data, projects, chat, notes, AI interaction records | While your account is open. Deleting an item in the product hides it but does not erase it. This data is permanently erased when your account is erased, about 7 days after you delete it (Section 8.1). This includes PDF copies held in Anthropic's file storage. |
| Rendered previews and exports | 30 days after rendering, then deleted. You get an in-app notice before an export is deleted. A record that the render existed stays in your project history. |
| Copies sent to Google Gemini for analysis | Deleted from Google's file store right after each analysis. |
| Files rendered on Modal | Kept only on the temporary disk of the machine that rendered them, which is erased when the machine shuts down, 2 minutes after its last render. |
| Data processed by Speechmatics | Deleted at Speechmatics as soon as we have the transcript. A job whose result never reaches us is deleted by Speechmatics automatically 7 days after it was created. |
| Server logs | Kept for 7 days under our hosting provider's log retention, then deleted automatically. |
| AI request logs (Section 6) | Kept for 7 days under our hosting provider's log retention, then deleted automatically. |
| Plan, subscription and top-up records, the credit ledger, notifications | While your account is open; the ledger is an unalterable record of your credits. Erased when your account is erased (Section 8.1). |
| Payment records | For each payment: our payment processor's charge identifier, or the bank transfer's transaction reference, what it bought, its amount and the date it was paid; for each refund: its identifier, amount and date. Kept for as long as Thai accounting and tax law requires us to keep records of income, including after your account is erased, without your account identifier (Section 8.2). |
| Erasure record | The account's random identifier and the dates its erasure was requested and completed. Kept after the erasure, as proof that we carried it out (Section 8.3). |
| Communications with us | As long as needed to handle your request and any follow-up. Refund-related messages and bank details are kept for as long as the related billing records. |
| Payment data held by Omise | Kept by Omise under its own legal obligations. Deleting your account deletes the customer record we created at Omise, with your saved card and the email address it holds. You can also ask us to remove your saved card once you have no active subscription. |
8.1 Deleting your account. You can delete your account in the app, under Settings → Account → Delete account, or by email as described in Section 10.2. When you delete it:
- it closes at once: you are signed out on every device, you cannot sign in to it again, your subscription is cancelled and your saved card is removed from Omise;
- about 7 days later, everything it holds is permanently erased: your account data and sign-in tokens, your uploads and everything derived from them, your projects, chat, notes and AI interaction records, your previews and exports, your credit ledger and notifications, and the PDF copies held in Anthropic's file storage. The wait lets work that was already running when you deleted the account finish first, so nothing is written after the erasure;
- an upload you had started but not finished is removed by our storage provider within 7 days of when it started; and
- what remains afterwards is only the payment records described in Section 8.2, the record that the erasure was requested and completed (Section 8.3), and server and AI request logs until they expire as shown in the table above.
Deleting your account cannot be undone. Its unused credits are erased with it. After the erasure, signing in with the same Google account creates a new, empty account.
8.2 Payment records kept after deletion. We keep a record of each payment and refund, as listed in the table above, because accounting and tax law requires us to keep records of income. When your account is erased, your account identifier is removed from these records, so they no longer say who paid. Our payment processor keeps its own records of the same payments under its own legal obligations. A payment that completes after you deleted your account, such as a PromptPay QR code paid later or a transfer whose slip is uploaded later, adds nothing to any account and is refunded in full.
8.3 Erasure record. We keep a record that your account's erasure was requested and completed. It holds only your account's random identifier and those two dates, and nothing else about you: no name, email address or content. We use it to refuse sign-in to the account while it waits to be erased, and to show that we carried out your request.
9. Security
We protect personal data with technical and organisational measures appropriate to the risk. These include:
- Encryption in transit. The Service is served only over HTTPS, and our providers are reached only over HTTPS.
- Encryption at rest on our hosting provider's storage.
- Protected session cookies. Session cookies are secure-only, HttpOnly and first-party.
- Card handling. Card details go to our payment processor's form and never reach Klipgen.
- Access controls. Every account, file, project and render is checked for ownership, so you can access only your own.
- Short-lived links to files, signed for each request.
- Signed notifications. Messages from our providers to the Service are signed and verified.
No system is perfectly secure. If a personal data breach is likely to put your rights and freedoms at risk:
- we will notify the Office of the Personal Data Protection Committee within 72 hours of becoming aware of it, as the PDPA requires; and
- where the risk is high, we will notify you without undue delay.
10. Your rights
10.1 Under the PDPA, and subject to its conditions and exceptions, you have the right to:
- access your personal data and obtain a copy of it, and ask how we obtained data you did not consent to;
- data portability: receive your data in a commonly used, machine-readable format, or have it sent to another controller where technically feasible;
- object to processing based on our legitimate interests;
- erasure: have your data deleted, destroyed or anonymised, including deletion of your whole account;
- restriction of processing;
- rectification, so that your data is accurate, complete and up to date. Changing your name or email in your Google account does not update the copy we hold; email us to correct it;
- withdraw consent, wherever we rely on consent, without affecting processing done before you withdrew it; and
- complain to the Office of the Personal Data Protection Committee (PDPC) of Thailand (www.pdpc.or.th).
10.2 How to exercise your rights.
- Email support@klipgen.ai from your account email and say which right you want to exercise.
- If you write from another address, we may ask you to verify your identity.
- We will respond within 30 days of receiving a verifiable request. If we cannot fulfil a request, for example because the law requires us to keep certain billing records, we will explain why.
- Exercising your rights is free, unless a request is clearly unfounded or excessive.
10.3 You can delete your account in the app at any time (Section 8.1); this permanently erases your content as well. Data export, and requests to erase particular content while keeping your account, are handled on request by email, within the time in Section 10.2.
11. Cookies and similar technologies
11.1 Cookies. We use only strictly necessary, first-party cookies. Because these are needed for the Service to work, they do not require consent.
| Cookie | Purpose | Duration |
|---|---|---|
__Secure-klipgen.session_token | Keeps you signed in | 30 days, renewed daily while used |
__Secure-klipgen.session_data | Short-term signed copy of your session, to speed up pages | 5 minutes |
__Secure-klipgen.state | Protects the Google sign-in process | 5 minutes |
11.2 Local storage. Your browser stores interface preferences locally: theme, last agent used, spend mode, grid size and chat panel width. These contain no personal data and stay on your device.
11.3 No tracking. We use no analytics, advertising, tracking pixels or session-recording tools.
11.4 Third-party requests made by your browser.
- Pages load fonts from Google Fonts.
- The card form loads Omise.js from Omise.
- Some marketing images and videos load from third-party content delivery networks.
These providers receive your IP address and browser information when your browser contacts them.
12. Children
The Service is only for people aged 18 or over. We do not knowingly collect personal data from anyone under 18. If you believe a minor has used the Service, email us and we will delete the account and its data.
13. No sale of personal data
We do not sell, rent or trade your personal data, and we do not use it for advertising.
14. AI training
14.1 Klipgen does not use your content to train AI models.
14.2 The AI providers listed in Section 6 process your content to return results to us. Their handling of that data, including any retention or use, is governed by their terms for API customers.
15. Other people's data in your content
15.1 If your content includes personal data about other people, you are responsible for having a lawful basis to use it, including any consent the law requires. Examples are people filmed or recorded, people named in documents, and voices in audio.
15.2 We process such data only to provide the Service to you.
15.3 If someone contacts us about their data in your content, we may contact you, and we will handle their request as the PDPA requires.
16. Changes to this Policy
16.1 We will update this Policy when our practices change, and we will update the effective date.
16.2 We will notify you of material changes by email to your account email or by a notice on the Service before they take effect.
17. Contact
Klipgen, an online service operated by a sole proprietor in Thailand
Email: support@klipgen.ai
You may also complain to the Office of the Personal Data Protection Committee of Thailand.