Kaigen Privacy Policy
Last updated: November 15, 2026
This Privacy Policy explains how 16456383 Canada Inc., doing business as Kaigen ("Kaigen", "we", "us"), collects, uses, shares and protects personal information in connection with our websites, accounts, billing, company workspaces, game hosting, community channels and other online services (the "Services"), Kaigen Studio, the Kaigen command-line tools, the Kaigen engine and runtime (the "Kaigen Software"), and applications built with the Kaigen Software ("Builds"). Capitalized terms not defined here have the meanings given in the Kaigen Terms of Service.
1. Who is responsible
1.1 Kaigen is responsible for the personal information described in this Policy, except where Section 1.3 applies.
1.2 Our Privacy Officer is responsible for our compliance with this Policy: Gabriel Dechichi, Privacy Officer, privacy@kaigen3d.com, 16456383 Canada Inc., 329 Howe Street, Unit 233, Vancouver, British Columbia V6C 3N2, Canada.
1.3 Company workspaces. When a company uses a Company Plan, we process the personal information of its members that the company or its identity provider gives us (including through single sign-on and directory sync), and the company's audit log, on the company's behalf and under its instructions. For that information the company is responsible, its own privacy notice applies, and requests should go to the company. Our Data Processing Addendum governs that processing.
2. Information we collect
2.1 Your Account
- Sign-up and profile: your email address, and the answers you give when you sign up: what you build, the stage of your project or company, and a short description of it.
- Sign-in: a keyed hash of each email sign-in code (deleted when it expires), and counters, stored as keyed hashes of your email address or IP address, that stop code guessing and sign-in abuse.
- Sign-in providers: if you sign in with Google, X or Discord, the account identifier that provider gives us.
- Passkeys: the public key of each passkey and the name you give it.
- Web sessions: your browser's user agent and your approximate country, so you can see and end your sessions.
- Signed-in devices: each device's name (its hostname), a public key, the IP addresses it was first and last seen from, and its approximate country, so you can see and revoke devices and we can spot stolen sign-ins.
- Command-line sign-in requests: the requesting device's hostname, IP address and approximate country, which we show you so you can check a request before approving it, kept for about an hour.
- Continuous-integration tokens: a one-way hash of each token, its name and who created it.
2.2 Plans and billing
- Payments: our payment provider, Stripe, collects your name, email, billing address, payment card and, for businesses, VAT number. Card details stay with Stripe. We store your Stripe customer identifier and the status, plan and history of your subscriptions, invoices, refunds and payment disputes.
- Eligibility declarations: which declaration you accepted at checkout, the versions of our terms you accepted, when, and a keyed hash of your IP address.
- Founder offers: which closed-beta licence key and Account claimed the offer, the plan, and whether you chose to be listed by name on our Founding Members page.
- Academic programme: your school email address, full name, institution and, if you choose, how you will use Kaigen.
2.3 Company workspaces
- membership, role and seat of each member;
- the company's audit log: who did what and when, with the country and browser user agent, and the IP address for Enterprise customers or a keyed hash of it for other companies;
- single sign-on identities: the identity provider's user identifier and email;
- directory sync records: names, emails and group memberships the company's directory sends us.
2.4 Hosted games and play pages
- Publishers: each published game's files, title and owning Account, and, for games published on the Free plan, a monthly count of page loads.
- Players: when someone opens a play page, our infrastructure provider processes their IP address to deliver it. We do not ask Players to sign in, and we do not set advertising or tracking cookies on play pages. Each Hosted Game is provided by its publisher, who is responsible for any data the game itself collects.
2.5 The Kaigen Software
Usage data. When you use the Kaigen Software, it sends us usage data. Each transmission includes your account or licence identifier, a one-way hash of your device's machine identifier (we never receive the identifier itself), a session identifier generated each time the software starts, the software version, build type and platform, a timestamp, and your approximate country. The data covers:
- environment and hardware: the Kaigen tool and version; operating system; processor, cores and memory; graphics card, model and driver; display size and scaling; a one-way hash of your project's identifier; and the name and version of any AI coding tool you run Kaigen from;
- product usage: when sessions start and end, their duration and exit codes; which commands you run, their duration and result; which editor or AI tool Kaigen Studio opened; and which plan limits you reached;
- build and run outcomes: the type, configuration, target platform, template, timings and result of each build and run, including the category of any failure and whether the application displayed its first frame;
- installations: installations and updates of the engine and toolchain, project creation and versions, and the error message of any failed installation;
- publishing: the signing method, version, targets and bundle identifiers of each published Build, and a one-way hash of its product name; and
- licence integrity: events showing a plan or licence problem, such as an expired, revoked or invalid credential, use on a different machine, or a device clock set backwards.
Plan and licence checks. When you sign in or activate, and while online, the Kaigen Software confirms your plan with our servers, sending your device credential or licence token, your machine hash, and the version of our terms you accepted.
Crash reports. If the Kaigen Software crashes, it sends us the time of the crash, the stack trace, registers and fault address, loaded modules, your operating system, hardware and graphics details, the software version, the hash of your project's identifier, your machine hash, and the log of that session. Before sending, it replaces your home folder in file paths with a placeholder. Your device keeps copies of recent crash reports so you can refer to them.
Bug reports. When you file a bug report, it contains what you write, your account or licence identifier, session identifier, machine hash, project identifier hash, software version, operating system and hardware details, and your most recent crash record; a screenshot of Kaigen Studio, only if you choose to attach one; up to three recent session logs and your project's settings file, only if you choose to include your project; and, if an AI coding tool files the report for you, that tool's name, version and diagnosis.
Debug symbols. When you publish a Build, the Kaigen Software uploads its debug symbols, which contain the function names and source file paths of your code, but not the code itself. We use them only to read crash reports from your Build and treat them as your confidential information.
What the Kaigen Software does not collect. It does not collect your source code, assets or project contents, except as described above (debug symbols, and what you choose to include in a bug report). It does not collect the prompts or transcripts of AI coding tools you run yourself.
2.6 Kaigen AI (when available)
When we make Kaigen AI available:
- the prompts and files your AI tool sends through Kaigen AI are passed to the AI model provider you choose so it can respond, and we record the number of tokens used and the cost;
- we may record your Kaigen AI sessions (your prompts, the model's replies, and the tool calls made, in each case through Kaigen AI), keep them in identifiable form for a short period (Section 9) to operate, secure and support Kaigen AI, and, as Section 3.3 describes, use them after removing information that identifies you to improve and develop Kaigen, Kaigen AI and our models.
We will tell you before Kaigen AI session recording starts. It does not apply to AI tools you run outside Kaigen AI.
2.7 Players of published Builds
Published Builds include Kaigen runtime components. When a published Build runs, including when people other than its developer use it, it sends us: the developer's account or licence identifier and a random session identifier that changes every time the Build starts; the Build's title, bundle identifier, version and a hash of its project identifier; the device's operating system, processor, memory, graphics card and display; how long each session lasted and how it ended; a timestamp and approximate country; and, if the Build crashes, a crash report with technical details and the end of the Build's log, with home folder paths replaced by a placeholder.
Published Builds do not read or store a persistent device identifier. On desktop and mobile, a crash report is stored on the device until it is sent at the next start, and data that cannot be sent while offline is kept in a short queue until sent. Web Builds store nothing on the device. We do not receive Players' names, contact details, or anything they create in the Build.
2.8 Communications, community and sales
- Communications: the content of emails and other messages you send us, including support requests, reports of content, and feedback.
- Community: if you join our Discord server or other community channels, we see what you share there, such as your username, profile and messages. We may match your community membership to your Account or sign-up, for example by the time you joined, to support you and understand who uses Kaigen.
- Understanding who signs up: with the consent you give when you sign up, and to decide whether and how to offer you a plan, support or a call, we may review publicly available information about you and your organization, such as its website, published games and products, press coverage, funding announcements, and public professional or social profiles (for example LinkedIn or X). We keep notes of what we find and of our contact with you. You can withdraw this consent at any time at privacy@kaigen3d.com.
- Calls and meetings: if you book a call or meeting, the time you choose and notes from it.
2.9 Website and technical data
Our websites and services run on Cloudflare, which processes IP addresses to deliver them. Beyond the items listed in this Section 2, we do not store IP addresses; we store an approximate country derived from them. Our sign-up and sign-in pages use Cloudflare Turnstile, which processes your IP address and browser signals to block automated abuse. We use cookies and similar storage only to keep you signed in, secure the Services and remember your preferences. We do not use advertising or cross-site tracking cookies.
We count visits to our websites without cookies. When a page on kaigen3d.com or studio.kaigen3d.com loads, we record the page, the referring site, how the page was opened and your approximate country, with a daily visitor code: a one-way hash of your IP address and browser user agent combined with a random value that we replace and delete every day. We do not store the IP address or user agent for this. Once the day's value is deleted, the code cannot be linked to you or to your visits on other days. We use these counts only in aggregate, under our legitimate interest in understanding how many people visit and sign up.
3. How we use information
3.1 We use personal information to:
- create and secure Accounts, sign you in, and show and revoke your sessions and devices;
- provide the Services and the Kaigen Software, including plans, billing, trials, company workspaces and hosting;
- process payments, calculate taxes, prevent payment fraud, and handle refunds and disputes;
- verify eligibility for plans, trials, offers and programmes, and enforce our terms, including identifying unlicensed use, plan misuse and Splash removal;
- detect, prevent and investigate abuse, security incidents, fraud and illegal content;
- diagnose and fix crashes and bugs, including by reading crash reports with debug symbols;
- understand how the Services and the Kaigen Software are used, and improve them;
- understand who signs up and how people find Kaigen, and decide whether and how to contact you about plans, support, feedback or a call;
- communicate with you about your Account, plans, billing, security, changes to our terms, and notices the law requires;
- send you news and offers, where you have consented or the law otherwise allows;
- handle reports of content, copyright notices and takedowns;
- when available, provide Kaigen AI and use session data as described in Section 3.3; and
- comply with legal obligations, and establish, exercise or defend legal claims.
3.2 We do not sell personal information, and we do not share it for cross-context behavioural advertising.
3.3 Kaigen AI sessions (when available).
- We remove information that identifies you from session data before using it to improve or develop Kaigen and our models, including names, email addresses, account identifiers, file paths that identify you, and credentials found in it. We will not try to re-identify you from it.
- Personal Plans: session data is used for these purposes by default. You can turn this off at any time in your Account settings, which applies to sessions after you turn it off.
- If you live in the European Union, the European Economic Area, the United Kingdom or Quebec: we use session data for these purposes only if you turn it on.
- Company Plans and Enterprise: we use session data for these purposes only if a company administrator turns it on.
- We do not share session data with third parties for their own model training without your separate consent.
4. Legal bases (EEA, UK and similar laws)
Where the law requires a legal basis, we rely on:
- contract: to provide your Account, plans, hosting, billing and the Kaigen Software;
- legitimate interests: to secure the Services, prevent fraud and abuse, enforce our terms, verify eligibility, diagnose crashes, improve our products and contact business users about Kaigen, which we balance against your rights and keep to what is necessary;
- consent: for marketing emails, for usage data where Section 5 requires it, for reviewing public information about you when you sign up (Section 2.8), and for Kaigen AI session data where Section 3.3 requires it, each of which you can withdraw at any time; and
- legal obligation: for tax, accounting, legal requests and notices the law requires.
5. Your choices about usage data
European Union, European Economic Area, United Kingdom and Quebec. The first time you use the Kaigen Software, we ask whether you agree to share usage data. We collect usage data only if you agree, and you can change your choice at any time in Kaigen Studio's settings or with the kaigen telemetry command.
Elsewhere. You can switch usage data off at any time in Kaigen Studio's settings, by running kaigen telemetry off, or by setting the environment variable DO_NOT_TRACK=1.
Everywhere. Plan and licence checks and crash reports continue whatever you choose, because they are needed to provide the Kaigen Software, protect it against misuse and keep it working. Bug reports are sent only when you file one. These settings apply to the Kaigen Software on your device, not to Builds you publish.
6. Emails
We send emails needed to run your Account and plans, such as sign-in codes, receipts, trial and renewal reminders, security alerts and notices about our terms. We send news and offers only where you have consented or the law otherwise allows, and every such email lets you unsubscribe.
7. Sharing
7.1 We share personal information only with:
- service providers who process it for us under contracts requiring them to protect it and use it only to serve us (Section 7.2);
- services you or your company choose, which receive information under their own privacy policies: sign-in providers (Google, X, Discord), company identity providers (such as Okta, Microsoft Entra or Google Workspace), GitHub (for leaked-token alerts), Discord (for our community) and, when Kaigen AI is available, the AI model provider you choose;
- your company, if you are a member of a company workspace: its owners and administrators can see your membership, role, devices and the company's audit log;
- the public, for what you choose to make public, such as Hosted Games, and your name on our Founding Members page if you opt in;
- professional advisers, such as lawyers, accountants and auditors, under duties of confidentiality;
- authorities and others, where required by law, or where necessary to protect our rights, our users or the public, including in response to reports of illegal content; and
- a successor, if Kaigen is involved in a merger, acquisition, financing or sale of assets, subject to this Policy.
7.2 Service providers.
| Provider | What it receives | Purpose |
|---|---|---|
| Cloudflare | All data on our websites and servers, including IP addresses | Hosting, storage, delivery, security, bot protection (Turnstile), email sending |
| Stripe | Name, email, billing address, payment card, VAT number | Payments, tax, invoices, fraud prevention |
| Google LLC (Gmail) | Email addresses and message content | Business email |
We keep the current list of service providers that process company workspace data at kaigen3d.com/legal/subprocessors.
8. International transfers
We are based in Canada, and our service providers may store and process information in Canada, the United States and other countries, including outside Quebec and outside your own province or country. Where information about people in the EEA or UK is transferred outside those regions, we rely on appropriate safeguards, such as adequacy decisions or standard contractual clauses. Information stored in another country may be accessible to its authorities under its laws.
9. Retention
| Information | Retention |
|---|---|
| Account and sign-up answers | While your Account exists; deleted within 90 days after it is closed, except as below |
| Email sign-in codes | Until they expire (10 minutes) |
| Sign-in abuse counters | 1 day (rate counters); about 8 days after the last failed attempt (wrong-code counters) |
| Web sessions | 7 days idle, 30 days at most |
| Signed-in devices | While active (they expire after 90 days idle or 365 days); records kept 12 months after revocation or expiry |
| Command-line sign-in requests | About 1 hour |
| Continuous-integration token records | Until revoked, and 12 months after |
| Billing, subscription, invoice, refund and dispute records | 7 years after the transaction, for tax and legal purposes |
| Eligibility declarations and terms acceptances | While your Account exists, and 7 years after your last Paid Plan ends |
| Founder offer records | While the offer applies, and 2 years after |
| Academic applications | 24 months after our decision, or while your Academic access lasts if longer |
| Hosted Games | While published; files deleted within 30 days after they are unpublished or your Account is closed |
| Free plan page-load counts | 24 months |
| Company membership | While you are a member; deleted within 90 days after you are removed or the Company Plan ends |
| Company audit logs | Rolling 12 months while the Company Plan is active (or as agreed in an Enterprise Agreement); deleted within 90 days after it ends |
| Single sign-on and directory sync records | While the connection exists; deleted within 30 days after it is removed or the workspace is deleted |
| Raw usage data archives and usage analytics | 90 days |
| Crash reports and bug reports | 12 months |
| Records of rejected data submissions, used to investigate licence misuse | 12 months |
| Machine, publishing and download records | 24 months |
| Closed-beta licence records | While the key is active, and 24 months after |
| Debug symbols | Until you ask us to delete them, or 90 days after your Account is closed |
| Communications, sales research notes and call notes | While we have a relationship with you, and 24 months after our last contact |
| Kaigen AI token and cost records (when available) | 7 years, with billing records |
| Kaigen AI session data (when available) | Identifiable session data: up to 30 days. De-identified session data: until no longer needed for the purposes in Section 3.3 |
| Marketing consent | Until you withdraw it, and records of it 3 years after |
We may keep information longer where the law requires, to resolve disputes, or to enforce our agreements. When you delete your Account, we delete or de-identify your information within 90 days, except what we must keep under this table or the law, and except usage analytics, which cannot be deleted individually and expire within 90 days.
10. Developers and players of Builds
If you distribute a Build, it sends the data in Section 2.7 when it runs. We use that data only to validate licences, detect misuse, diagnose crashes and understand use of the Kaigen Software. As the developer, you are responsible for your Build and for informing its users where the law requires. Schedule B of the Kaigen Software Licence Agreement includes text you can use. Players with questions about data Kaigen receives may contact us at privacy@kaigen3d.com.
11. Security
We protect personal information with safeguards appropriate to its sensitivity, including access controls, passkeys for company administrators, encryption in transit, storing sign-in codes, tokens and some IP addresses only as keyed or one-way hashes, device credentials tied to device security hardware where available, and replacing home folders in file paths before crash and bug reports are sent. No system is completely secure. If a breach of security creates a real risk of significant harm to you, we will notify you and the authorities as the law requires.
12. Your rights
12.1 Depending on where you live, you may have the right to access, correct, delete or receive a portable copy of your personal information, to withdraw consent, to object to or restrict certain processing, and to ask how it was used or shared.
12.2 To make a request, email privacy@kaigen3d.com. We may need to verify your identity, and we will respond within 30 days, or the period the law requires. If a company workspace controls the information (Section 1.3), we will refer you to the company. Deleting some information, such as sign-in or billing records, may end your access to the Services.
12.3 If you are not satisfied with our response, you may complain to the Office of the Privacy Commissioner of Canada, the Office of the Information and Privacy Commissioner for British Columbia, the Commission d'accès à l'information du Québec, or, in the EEA or UK, your local data protection authority.
12.4 We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you. We use automated checks to block abuse and fraud, and you may contact us if you believe one affected you wrongly.
13. Children
The Services are not directed to children. You must be at least 16 to create an Account. We do not knowingly collect personal information from children under 16 who use the Services or the Kaigen Software, and our hosting does not allow games directed to children under 13. If you believe a child has given us personal information, contact us and we will delete it.
14. Changes to this Policy
We may update this Policy. We will publish the updated version with a new "Last updated" date and, for material changes, notify you by email, through the Services or within the Kaigen Software before they take effect.
15. Contact
Questions, requests and complaints: Gabriel Dechichi, Privacy Officer, privacy@kaigen3d.com. 16456383 Canada Inc., doing business as Kaigen, 329 Howe Street, Unit 233, Vancouver, British Columbia V6C 3N2, Canada.
