Legal
Privacy Policy
Last updated: 9 November 2026
The data controller is KREATOR FLOW AI LIMITED, a company registered in England and Wales (company number 16420097).
1. Who we are
KreatorFlow is the AI creation platform at kreatorflow.ai, including the studio, the video editor, the developer API and our connector for AI assistants such as Claude and ChatGPT. It is run by KREATOR FLOW AI LIMITED ("we", "us"), registered in England and Wales under company number 16420097, registered office 128 City Road, London EC1V 2NX, United Kingdom.
We decide how and why your personal data is used, so we are its controller. The one exception is personal data that developers and business customers send us about their own users through the API: there we act for them as a processor (see section 11).
Privacy questions and requests: privacy@kreatorflow.ai
Everything else: support@kreatorflow.ai
Post: KREATOR FLOW AI LIMITED, 128 City Road, London EC1V 2NX, United Kingdom
EU representative (Article 27 EU GDPR): being appointed. Until then, people in the EU can contact us directly at privacy@kreatorflow.ai.
2. The short version
- We collect what we need to run your account, make what you ask for, take payment and keep the service safe.
- Your prompts and media are processed by BytePlus (we are an official partner of BytePlus, a ByteDance company). Our database, file storage and servers are in Malaysia and Singapore.
- We do not use your prompts, uploads, or generated outputs to train AI models without your explicit opt-in consent, and we do not sell your personal data.
- Analytics and advertising cookies only run if you allow them. Marketing emails only go to people who ticked the box to receive them. The one exception is a short reminder if you start a purchase and do not finish it. Every one of these emails has a one-click unsubscribe.
- Anything you post to Explore or your public profile, including its prompt, can be seen by anyone and found by search engines.
- You can download your data or delete your account in Settings at any time.
3. What we collect
Information you give us
- Account: email address, display name, username (your public handle), and optionally a bio, profile picture and cover image. If you sign in with Google, we receive your Google account id, email address, name and profile picture.
- Password: stored only as a salted hash (scrypt), never in readable form.
- Age and country: your date of birth, to confirm you are 18 or over, and your country, which we may pre-fill from your approximate location and you can change. Your date of birth is never shown publicly.
- Sign-up questions: how you heard about us (required), and optionally your goals and a short survey about how you create. We use these to understand which channels work and to tailor your experience and the offers we show you.
- What you create: prompts, settings, uploaded images, videos and audio, saved characters, voice samples you use for voice cloning, video editor projects, and the images, videos and audio we generate for you.
- Public activity: posts you submit to Explore, your public profile, likes, comments and follows.
- Payments: your plan, purchases, credit and token balances and history. Card details go straight to Stripe and never reach our servers. For crypto payments we store the payment and order reference, coin and amount, but not your wallet address.
- Support: messages and attachments you send us (including email replies to our support emails), and conversations with the help assistant on our site (whether or not you are signed in) and with the Kartoonz assistant. When the Help Center can't answer, help chats may be answered by Kaye, an AI assistant run on BytePlus; for a signed-in account they see your plan, credit balance, whether your starter credits were added, and your last few failed generations, so they can explain what happened. They can't change your account.
- Consent records: which policy versions you accepted and when, whether you agreed to marketing emails, your cookie choices, the checkout confirmation about your cancellation right, and the confirmations you give before using someone's face or voice (section 6).
- Developers: API keys (stored only as a hash, with the first and last few characters kept so you can recognise them), webhook addresses, API jobs and their inputs and outputs.
- Affiliates: if you joined our affiliate programme on Rewardful (from 6 November 2026), Rewardful holds your affiliate account, referrals, commission and payout details, and we see them in Rewardful. If you joined our earlier programme (before 6 November 2026), we hold your name, email, promo code and payout account status; bank, identity and tax details are collected by Stripe, not by us.
Information collected automatically
- Sign-in records: for each session, your IP address and browser details, so we can keep your account secure and to answer payment disputes.
- Abuse prevention: to stop people creating many accounts for free credits, we keep hashed (not readable) counts per email inbox, IP address and browser, and a random browser id in a cookie. Throwaway email domains are blocked.
- Usage: pages you visit, the site that sent you, campaign tags in the link, and steps in sign-up and checkout, stored with a daily-changing hashed visitor id rather than your IP address. Our own usage statistics, and our analytics providers only run if you allow analytics cookies.
- Technical logs: errors and failed requests (status, endpoint, timing and ids, never your prompts or API keys) so we can fix problems.
- Referrals: if you arrive through an affiliate link and allow marketing cookies, Rewardful (our affiliate partner platform) records the referral and it is kept in a cookie, so the affiliate can be credited if you buy; when you pay, Rewardful receives that payment's details from Stripe (including your email address and the amount) to work out the commission. For links of affiliates who joined our earlier programme (before 6 November 2026), we record the referral ourselves and, with your consent, keep it in a cookie so the affiliate can be credited if you sign up later.
- Where your visit came from: without marketing cookies, we still note in the page's memory (nothing is stored on your device) the campaign tags in the link you arrived from, the first page and the referring website's name, and save them with your account if you sign up during that visit, to see which campaigns bring sign-ups; ad click ids are only kept if you allow marketing cookies. We also count, as totals only, how many visits arrive from each ad campaign; nothing about you is stored for this.
Information from others: Google (if you sign in with Google), Stripe (payment status, and fraud and chargeback signals), affiliates (the referral code you used), Rewardful (which affiliate referred you), and team owners who invite you to a Business workspace (your email address).
4. Other people in your content
If you upload a photo, video or voice of another person, or name them in a prompt, you are giving us their personal data. You may only do this if you are that person or have their permission, and you confirm this before using a face for face swap or motion transfer or a voice for cloning. We use that content only to make what you asked for and to check it is safe. If you appear in someone's content without permission, email support@kreatorflow.ai with the subject "Takedown" and we will act on it (see our Terms).
5. Why we use your data and our legal basis
UK and EU data protection law requires a legal basis for each use. These are ours:
| What we do | Legal basis |
|---|---|
| Create and run your account, make the images, videos and audio you request, save your library, run the editor, API and connector | Contract (providing the service you signed up for) |
| Take payments, give credits and tokens, send receipts and service emails (sign-up, security, failed payment, renewal reminders) | Contract |
| Keep tax and accounting records | Legal obligation |
| Check you are 18 or over | Legal obligation and legitimate interests (keeping an adults-only service for adults) |
| Safety checks on prompts, uploads and outputs; review of Explore posts; handling reports, takedowns and appeals | Legal obligation (including the Online Safety Act) and legitimate interests (keeping the service and other people safe) |
| Preventing fraud, payment abuse and multiple accounts for free credits; securing sign-in; error monitoring | Legitimate interests (protecting the service, our customers and us) |
| Answering payment disputes (chargebacks): sharing the purchase, your sign-in records, what the account generated, the box ticked at checkout and support messages with Stripe and the card issuer | Legitimate interests (showing what was bought and used) and defending legal claims |
| Showing your public profile and the posts you choose to publish | Contract (you choose to publish) and legitimate interests (a public creator profile, which you can make private) |
| Answering support requests, including staff viewing your account when needed to help or investigate | Contract and legitimate interests |
| Understanding how people find us through your sign-up answers and the campaign details of the link you arrived from | Legitimate interests (improving the product and our marketing) |
| Analytics (our own usage statistics and our analytics providers) | Consent (cookie banner) |
| Measuring our ads | Consent (cookie banner, marketing) |
| Marketing emails and offers | Consent (the box at sign-up, which you can withdraw at any time) |
| A reminder if you start a purchase and do not finish it | Legitimate interests (you were in the middle of buying; you can unsubscribe at any time) |
| Crediting affiliates for referrals and paying them | Legitimate interests (running the referral programme) and contract (with the affiliate); the referral cookie needs your consent |
| Keeping records of the confirmations you give for faces and voices | Legal obligation and legitimate interests (investigating misuse) |
| Using your content to train AI models | Only with your explicit opt-in consent. We do not do this today |
| Responding to legal requests and defending legal claims | Legal obligation and legitimate interests |
Giving us your email address, date of birth and country is required to open an account, and payment details are required to buy. Everything else is optional or only needed for the features you choose to use.
6. Faces and voices
- Face swap and motion transfer: face detection runs in your browser and the photo never leaves your device for that step. On our side we crop and combine images, and BytePlus generates the result.
- Face swap safety check: before a face swap (in the Face Swap studio or in Kitsune), an automated check looks at the images, and at stills from the video, for sexual content and for minors, and blocks the request if it finds either. Motion transfer and other tools rely on the content checks described in section 7.
- Voice cloning: your voice sample is sent to BytePlus, which uses it to create a voice model so it can speak in that voice. The voice model is held by BytePlus, linked to a voice slot in our BytePlus account. We keep a copy of the sample with the voice.
- We use faces and voices only to make what you ask for. We do not use them to recognise or identify anyone, and we do not build face or voice templates for identification.
- You confirm that the face or voice is yours, or that you have the person's permission, before a face swap (in the Face Swap studio or in Kitsune), before a Kitsune motion transfer that uses a photo of a person, and before you clone a voice. We keep a record of that confirmation (date, time, the wording you agreed to and which upload or voice it covers). When you use these tools through an AI assistant, you confirm on kreatorflow.ai, not in the chat.
- When you delete a voice, it can no longer be used, and the voice model held by our AI provider is replaced when its slot is reused. We delete the voice sample and its portrait from our storage. We keep the confirmation record, without any audio, so we can investigate reports of misuse (see section 14).
7. Automated checks and decisions
Some decisions are made automatically:
- Content safety: BytePlus and our own checks can refuse a prompt, upload or result (for example real people, public figures, protected characters, explicit content or minors). Refused generations do not cost credits.
- Sign-up abuse: throwaway email addresses are blocked, and an account may be created without free starter credits if the same inbox, network or browser already received them.
- Bots: automated sign-in and sign-up attempts are blocked.
- Payments: a refund or chargeback automatically reverses the credits or tokens it paid for.
Account suspensions and bans are decided by a person, not automatically. If you think an automated decision is wrong, email support@kreatorflow.ai and a person will review it.
8. Public content
- Your profile (name, handle, bio, pictures, follower counts and the posts on it) is public unless you make it private in Settings.
- Posts you submit to Explore are checked by our team before they appear. Once public, the post, its prompt and its settings can be seen by anyone, recreated by other users, and found by search engines.
- Our public pages can be read by search engines and by AI companies' crawlers, which may use public content in ways we do not control. Content made with unrestricted settings is never offered to search engines.
- To remove a public post, delete it. Likes, comments and follows are visible to other users. You can delete your own comments at any time.
9. Teams (Business workspaces)
In a Business workspace, everything members create, including prompts, is visible to all members of that workspace. Owners and admins can also see each member's email, name, role and credit use, delete content and manage billing. The workspace owner (usually your employer or client) decides who is in the team. If you leave a team or delete your account, the work you made in that workspace stays with the team. This is also true if you own the team workspace and delete your account: its content stays for the other members.
10. Connected AI assistants (Claude, ChatGPT and others)
- You can connect KreatorFlow to an AI assistant using our connector (an MCP server). You sign in on kreatorflow.ai and approve access. The assistant gets a token that lasts one hour and renews for up to 30 days. You can disconnect it at any time in the assistant or by contacting us.
- We only receive what the assistant sends to our tools: your request (such as a prompt), links to media and the options chosen. We never receive your wider conversation, chat history or the assistant's memory.
- When asked, our tools send the assistant your plan and credit balance, your recent creations with their prompts, your saved characters and voice names, and download links that stop working after about 15 minutes.
- We log which tool was used, whether it worked and how long it took, but not your prompts or links.
- What happens to information inside the assistant is covered by that company's own privacy policy (for example Anthropic for Claude and OpenAI for ChatGPT). They are separate controllers, not our processors.
11. Developers and the API
- For your own developer account we are the controller (keys, billing, logs). For personal data you send about other people (for example your users' faces, voices or prompts), you are the controller and we process it for you under our Data Processing Addendum, which forms part of the API terms.
- We send job results, including the prompt, to the webhook address you set. Webhooks are signed so you can check they came from us.
- Prompts and request details of API jobs are cleared 90 days after a job finishes; the job record stays for billing. Outputs and uploads are kept for the period that matches your plan unless you have a Storage Pack.
13. International transfers
We are based in the UK, but our database, file storage, AI processing and servers are in Malaysia and Singapore, and some providers are in the United States. These countries do not have UK or EU "adequacy" status (except US companies certified under the UK-US Data Bridge or EU-US Data Privacy Framework). When your data goes there, we protect it with the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses (and the EU Standard Contractual Clauses for data from the EU), together with an assessment of the risks of each transfer. You can ask us for a copy of the safeguards at privacy@kreatorflow.ai.
14. How long we keep data
| Data | How long |
|---|---|
| Account and profile | While your account is open. About 30 days after you delete your account, we delete or anonymise your personal data, and delete it from our sub-processors where they let us do so; copies a sub-processor keeps are deleted under its own retention terms. Images, videos and projects in your own workspace are deleted. Work in a Business team workspace belongs to the team and stays with it, even if you owned that workspace. We keep the support tickets and payment records listed below. If we closed your account for a serious breach of our rules, we keep a hashed (unreadable) copy of its email address for as long as the ban stands, so it cannot be used to open a new account; we never keep the address itself for this |
| Free-credit abuse check | If your account received free starter credits, we keep a one-way hash (unreadable) of its email address for up to 13 months after you delete it, so the same inbox cannot get free credits again |
| Unsaved generation history | Depends on your plan: 7 days (Free and Lite), 30 days (Creator), 60 days (Pro), 90 days (Max), 180 days (Business). Then the images, videos and audio, and their prompts, are deleted. A billing record of the generation (model, cost and date, without the prompt) is kept with the payment records |
| Saved assets, uploads, characters and editor projects | Until you delete them or your account. From 21 November 2026: if you cancel a paid plan and do not start a new one, the images, videos, uploads and saved characters in your library are deleted 30 days after the plan ends (for plans that end on or after that date). We email you the date when you cancel, and again 7 days and 1 day before. Starting a plan before then keeps everything. Posts you published on Explore stay until you remove them |
| Cloned voices and their samples | Until you delete the voice or your account, or leave the team workspace you made it in. In a team, only the person who recorded a voice can use or delete it |
| Confirmations for faces and voices | While your account is open, then 12 months |
| API job inputs (prompts and request details) | 90 days after the job finishes |
| Sign-in records (IP address and browser) | 12 months after the session ends |
| Usage statistics and sign-up steps | 25 months |
| Support tickets and attachments | 2 years after the ticket is closed |
| Help assistant conversations | 12 months if you were signed out; 2 years if you were signed in |
| Marketing and email sending records | 24 months. If you unsubscribe, we keep a record of that for as long as needed so we do not email you again; it is removed if you opt in again or when your account is deleted |
| Affiliate clicks and referral details | 24 months (browser details of referred sign-ups: 90 days) |
| Payment, tax and accounting records | 7 years, as the law requires |
| Error logs | 30 to 45 days |
| Backups | Overwritten on a rolling basis |
We may keep specific data longer if we need it for a legal claim, an investigation of serious misuse, or because the law requires it.
15. Marketing emails
We send marketing emails and offers only if you ticked the box to receive them. If you start a purchase and do not finish it, we may send a short reminder. Every marketing email and reminder has an unsubscribe link that works in one click, and unsubscribing always wins. Service emails (receipts, security, renewal reminders, failed payments, replies to your support requests) are not marketing and are sent while you have an account.
17. Your rights
You have the right to:
- access your data and get a copy (Settings has a download of your account data, or email us);
- correct inaccurate data;
- delete your data (Settings lets you delete your account, including Google sign-in accounts), subject to records we must keep by law;
- restrict how we use your data, and object to uses based on legitimate interests, including marketing, which we will always stop;
- data portability: receive the data you gave us in a machine-readable format;
- withdraw consent at any time, for example in the cookie banner or with the unsubscribe link, without affecting what we did before;
- ask for a person to review an automated decision (section 7).
Email privacy@kreatorflow.ai to use any right. We may need to confirm your identity. We reply within one month (we can extend this by two months for complex requests, and will tell you if we do). This is free unless a request is clearly unfounded or excessive.
Complaints: please tell us first at privacy@kreatorflow.ai. We will acknowledge your complaint within 30 days, look into it without undue delay and tell you the outcome. You can also complain to the UK Information Commissioner's Office (ICO) at ico.org.uk/make-a-complaint or on 0303 123 1113. If you live in the EU, you can complain to the data protection authority in your country.
18. Security
We use encryption in transit (TLS), salted password hashing, hashed API keys, encrypted webhook secrets, signed short-lived links for uploads and downloads, and HTTP-only session cookies. Access to production data is limited to authorised staff. When staff need to see your account to help you or investigate a problem, they can view it or briefly sign in as you; every such access is logged. If we ever have a breach that puts your rights at risk, we will tell you and the ICO as the law requires. If you think your account has been compromised, email support@kreatorflow.ai straight away.
19. Children
KreatorFlow is only for people aged 18 or over. We ask for your date of birth at sign-up. If we learn that an account belongs to someone under 18, we close it and delete its data. If you think a child is using KreatorFlow, tell us at support@kreatorflow.ai.
20. Changes to this policy
We will tell you about important changes by email or in the app at least 30 days before they take effect. If a change needs your consent, we will ask for it. The dates at the top show the current version.
21. Contact
KREATOR FLOW AI LIMITED (trading as KreatorFlow)
Company number 16420097, registered in England and Wales
128 City Road, London EC1V 2NX, United Kingdom
Privacy: privacy@kreatorflow.ai
Support: support@kreatorflow.ai