This is a previous version, in force until November 10, 2026. The current version is the Privacy Policy.

Kaigen Privacy Policy

Last updated: September 28, 2026

This Privacy Policy explains how 16456383 Canada Inc., doing business as Kaigen ("Kaigen", "we", "us"), collects, uses and protects personal information in connection with our website, the Kaigen closed beta, Kaigen Studio, the Kaigen command-line tools, the Kaigen engine and runtime (together, the "Kaigen Software"), and applications built with the Kaigen Software ("Builds").

We collect as little as we need. The Kaigen Software never collects your AI prompts or transcripts, and does not collect your source code, assets or project contents, except the debug symbols described in Section 2.6 and anything you choose to include in a bug report under Section 2.5.

1. Who is responsible

Kaigen is responsible for the personal information described in this Policy. Our Privacy Officer is accountable for our compliance with it and can be reached at hello@kaigen3d.com.

16456383 Canada Inc., doing business as Kaigen, Burnaby, British Columbia, Canada.

2. Information we collect

2.1 Closed beta applications and demo requests

When you apply for the closed beta or request a demo, you give us:

• your email address;
• your use case, the stage of your project or company, and a short description of what you are building;
• for demo requests, the call time you choose.

Our form also collects automatically: your browser's time zone, the address of the page that referred you to our website, any campaign tags in the website address you used, and your approximate country, derived from your IP address by our infrastructure provider. We use these to schedule calls and to understand how people find Kaigen.

The form uses Cloudflare Turnstile to block automated submissions. Turnstile processes your IP address and browser signals when you submit the form. We do not store them.

2.2 Communications

The content of emails and other messages you send us, including support requests and feedback.

2.3 Usage data from the Kaigen Software

When you use the Kaigen Software, it sends us usage data. Every transmission includes:

• your license ID;
• a machine hash, which is a one-way hash of your device's machine identifier (we never receive the identifier itself);
• a session ID, generated randomly each time the software starts;
• the software version, the build type (development, test or publish) and the platform;
• a timestamp;
• your approximate country, derived from your IP address by our infrastructure provider.

The usage data falls into these categories:

• Environment and hardware: the type and version of the Kaigen tool in use; your operating system and version; your processor, number of cores and memory; your graphics card vendor, model and driver; your display size and scaling; a one-way hash of your project's identifier; and the name and version of any AI coding tool you are running Kaigen from.
• Product usage: when sessions start and end, their duration and exit codes; which Kaigen commands you run, their duration and result; and which editor or AI tool Kaigen Studio opened.
• Build and run outcomes: the type, configuration, target platform, project template, timings and result of each build and run, including the category of any failure and, for runs, whether the application displayed its first frame and how it exited.
• Installations: installations and updates of the engine and toolchain, project creation, the versions involved, and the error message of any failed installation.
• Publishing: the signing method, version, target platforms and bundle identifiers of each published Build, and a one-way hash of its product name.
• License integrity: events indicating a license problem, such as an expired, revoked or invalid license, a license used on a different machine, or a device clock set backwards.

2.4 Activation and license checks

When you activate the Kaigen Software, it sends your License Key, your machine hash and the version of our terms that you accepted. After that, while online, it confirms the status of your license with our servers at most once a day. Each check sends only an access token identifying your license and your machine hash.

2.5 Crash reports and bug reports

Crash reports. If the Kaigen Software crashes, it sends us a crash report containing: the time of the crash; the stack trace, processor registers and fault address; the list of loaded software modules; your operating system, hardware and graphics details; the software version; the one-way hash of your project's identifier; your machine hash; and the log of that session. Before sending, the software replaces the home folder in file paths with a placeholder. Your device keeps copies of your most recent crash reports so you can refer to them when filing a bug report; these are not sent again.

Bug reports. When you choose to file a bug report, it contains what you write, together with your license ID, session ID, machine hash, the one-way hash of your project's identifier, the software version, and your operating system and hardware details. It also includes your most recent crash record; a screenshot of Kaigen Studio, only if you tick the option 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 on your behalf, that tool's name and version and its diagnosis. File paths are processed in the same way as in crash reports.

2.6 Debug symbols

When you publish a Build, the Kaigen Software uploads its debug symbols. These 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, treat them as your confidential information, and delete them on your request or ninety (90) days after your license ends, unless it is renewed or reinstated in the meantime.

2.7 Players of published Builds

Published Builds include Kaigen runtime components. When a published Build runs, including when it is used by people other than its developer, it sends us:

• the developer's license ID and a random session ID that changes every time the Build starts;
• the Build's title, bundle identifier and version, and a one-way hash of its project identifier;
• the device's operating system, processor, memory, graphics card and display;
• how long each session lasted and how it exited;
• a timestamp and the approximate country, derived from the IP address;
• if the Build crashes, a crash report containing technical details of the crash and the last part of the Build's log, with home folder paths replaced by a placeholder.

Published Builds do not read or store any persistent device identifier. On desktop and mobile, a crash report is written to the device at the moment of the crash and sent and deleted the next time the Build starts, and data that cannot be sent while the device is offline is kept in a short queue and deleted once sent. Web Builds store nothing on the device. We do not receive players' names, contact details, or anything they create in the Build. See Section 10.

2.8 Website and technical data

Our website and services run on Cloudflare. Like any internet service, our infrastructure provider processes IP addresses to deliver our website and receive data from the Kaigen Software. We do not store IP addresses. We store an approximate country derived from them, as described above. We do not use advertising or cross-site tracking cookies.

2.9 Community channels

If you join our Discord server or other community channels, the platform that hosts them processes your information under its own privacy policy. We see the information you choose to share there, such as your username and messages.

3. How we use information

We use personal information to:

• review closed beta applications and schedule demos;
• issue, activate and validate licenses;
• detect and prevent misuse of the Kaigen Software, and verify compliance with our license terms, including identifying unlicensed commercial use;
• diagnose and fix crashes and bugs, including reading crash reports using debug symbols;
• operate, maintain and secure the Kaigen Software and our services;
• understand how the Kaigen Software is used, and improve it;
• understand how people find Kaigen;
• communicate with you about the closed beta, your license, updates and changes to our terms;
• respond to your requests and provide support;
• send you news about Kaigen, if you have consented to receive it; and
• comply with legal obligations and protect our legal rights.

We do not sell personal information, and we do not use it for advertising.

4. Legal bases (EEA, UK and similar jurisdictions)

Where the law requires a legal basis for processing, we rely on:

• performance of a contract, to review your application, provide the closed beta and validate your license;
• legitimate interests, to detect misuse, verify license compliance, diagnose crashes, improve the Kaigen Software, understand how people find us and secure our services, which we balance against your rights and keep to the minimum data necessary;
• consent, for marketing emails, which you can withdraw at any time; and
• legal obligation, where we must process data to comply with the law.

5. Switching off usage data

Developers can switch off usage data by running kaigen telemetry off or by setting the environment variable DO_NOT_TRACK=1. License checks and crash reports continue, as they are required to operate the closed beta, and bug reports are sent only when you choose to file one. These settings do not apply to published Builds. Holders of a commercial license can switch off the data sent by their published Builds.

6. Emails

We send emails needed to run the closed beta, such as your License Key and notices about our terms. We send news, announcements and offers only if you have consented, and every such email includes a way to unsubscribe. You can also withdraw consent by writing to hello@kaigen3d.com.

7. Sharing

We share personal information only with:

• service providers who process it on our behalf, under contracts that require them to protect it and use it only to provide their services to us. These are our hosting, infrastructure, data storage, analytics and bot protection provider (Cloudflare), and our email provider;
• authorities or other parties, where required by law or to protect our rights, users or the public; and
• a successor, if Kaigen is involved in a merger, acquisition or sale of assets, in which case this Policy will continue to apply to your information.

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. 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 the authorities of that country under its laws.

9. Retention

We may keep information longer where the law requires it or to resolve a dispute. On request, we can delete the data associated with your license from all our systems, 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 described in Section 2.7 when it runs. We use this data only to validate licenses, detect misuse, diagnose crashes and understand usage of the Kaigen Software. As the developer, you are responsible for your Build and for informing your players about data collection where the law requires it. Our Closed Beta License Agreement includes text you can use for this. Players who have questions about data Kaigen receives may contact us at hello@kaigen3d.com.

11. Security

We protect personal information with safeguards appropriate to its sensitivity, including access controls, encryption in transit, storing machine identifiers only in hashed form, and replacing the home folder in file paths with a placeholder before crash and bug reports are sent. No system is completely secure, and we cannot guarantee absolute security.

12. Your rights

Depending on where you live, you may have the right to:

• access the personal information we hold about you;
• correct inaccurate information;
• ask us to delete your information;
• withdraw consent where we rely on it;
• object to or restrict certain processing; and
• receive your information in a portable format.

To exercise these rights, email hello@kaigen3d.com. We may need to verify your identity, and we will respond within 30 days. Deleting certain information, such as license records, may end your access to the closed beta.

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, or, if you are in the EEA or UK, your local data protection authority.

13. Children

The Kaigen Software and the closed beta are intended for people who are at least 18 years old or the age of majority where they live. We do not knowingly collect personal information from children who use the Kaigen Software or our services. If you believe a child has provided us with personal information, contact us and we will delete it.

14. Changes to this Policy

We may update this Policy from time to time. We will post the updated version with a new "Last updated" date and, for material changes, notify you by email or within the Kaigen Software.

15. Contact

Questions, requests or complaints about this Policy can be sent to our Privacy Officer at hello@kaigen3d.com.

16456383 Canada Inc., doing business as Kaigen, Burnaby, British Columbia, Canada.