Is the generated code mine? Ownership and data governance

A fair question before you generate a single line: if the AI writes the components, who owns the result? The short answer is that the generated code is yours. It is not trapped inside the platform, and it does not depend on a subscription to keep working.

The longer answer matters more. Ownership without governance is just a marketing line. That is why this article separates two things that are often mixed together: what you can do with the code, and how the data that flows through the pipeline is handled. Everything below is backed by our legal documents, which are the authoritative version.

The generated code is yours: the zip is the proof

KitekAI generates React + Tailwind components. When the landing is ready, you can download the zip and host it on any provider. There is no proprietary layer tying your site to our servers.

It helps to understand why this is structural rather than a courtesy. The platform produces a standard static export: components, styles, and assets that run on their own. That means you can version the code in your own repository, modify it, extend it with your tooling, and deploy it to the hosting you already use.

In practice, "the code is mine" breaks down into four concrete capabilities:

• Full download: you get the project zip, not a screenshot or a partial export.
• Real portability: the site works without KitekAI once downloaded.
• Repository control: it joins your Git, review, and CI flow like any other code.
• Hosting autonomy: backend, CDN, or static hosting, your call.

That export is not a black box: the code uses a tight set of packages —react, lucide-react, gsap, framer-motion, axios, clsx, and tailwind-merge— and deployment targets any hosting through a static export. The workflow is the same across archetypes: preview, staging, and deploy, or a direct zip download if you prefer to publish on your own. None of that requires the project to stay connected to the platform to keep running.

No lock-in: what it means in practice

Lock-in appears when your site's value depends on keeping a recurring payment. We work with a pay-as-you-go (PAYG) model and credits that never expire: there is no monthly plan forcing you to stay so your landing keeps running.

This connects to the three KitekAI pillars. Financial Governance makes consumption auditable and removes hidden recurring plans. The Operational Matrix standardizes archetypes and components so the output is repeatable. And the Controlled Environment ensures generation happens inside a defined pipeline, not a black box.

If you ever want to leave, you take the code with you. If you stay, you stay because it works for you, not because you are stuck.

The credit model reinforces that portability. One credit equals one dollar, top-ups come in defined amounts, and credits never expire. There is no subscription that can take your site offline and no monthly plan that conditions access to the code you already generated.

Data governance: retention, encryption, and audit

Governance is the other half of the deal. These are the published facts:

• Data retention: 12 months. That is the platform's defined retention period.
• Encryption in transit: SSL. Information travels encrypted between your browser and our services.
• Per-user and per-org audit. Every organization can trace consumption with granular visibility.

For teams, KitekAI adds features built for working together: multi-user, shared credits, and an admin dashboard. That lets several people generate against the same budget while whoever administers it sees who consumed what. The Consumption Audit module is real-time and 100% traceable.

It is worth specifying the scope of that audit. The record is not limited to a per-account total: visibility is per-user and per-organization, so an administrator can reconstruct who generated each component and against which budget. The module runs in real time and is 100% traceable, even when an organization groups several users and several projects at once.

The complete details, in the legal language that applies, live in the official documents. We recommend reading them before publishing:

• Data governance: https://www.kitekai.co/gobernanza-de-datos
• Privacy policy: https://www.kitekai.co/politica-de-privacidad
• Terms of service: https://www.kitekai.co/terminos-de-servicio
• Technical document: https://www.kitekai.co/documento-tecnico

These pages are the authoritative source. If anything in this article and the legal document differ, the legal document wins.

The enterprise angle: teams, credits, and control

For an organization, the ownership question becomes operational. It is not just "the code is mine," but who inside the team generated what, with how much budget, and under what traceability.

The admin dashboard handles that layer. Shared credits centralize spend; per-user and per-org audit show the detail; and the PAYG model avoids committing to an annual contract just to test the pipeline on a real project.

Shared credits pool spend into a single balance for the whole team, and the admin dashboard exposes the consumption detail without manual coordination. For organizations that bill by project, that combination of multi-user access and audit turns the frontend budget into a traceable line item rather than an estimate.

If your team needs to review this in more depth, the technical document describes the architecture and the AI pipeline explains how components are generated. You can reach us at [email protected] for specific governance cases.

Frequently asked questions

Who owns the code that the AI generates?

The generated code is yours. KitekAI produces a React + Tailwind export that you can download as a zip and host on any provider. There is no proprietary layer keeping your site tied to the platform, so you keep control of the repository and the deployment.

Can KitekAI reuse my code for other projects?

Data handling is governed by our legal pages, which are the authoritative source: data governance, privacy policy, and terms of service. They describe precisely what is stored, for how long, and under what conditions. Any organization-specific question can be answered at [email protected].

How long is my data retained?

The platform's defined retention is 12 months. During that period, data is kept in an environment with SSL transport encryption. If your organization needs a deeper review, the technical document and the data governance page detail the full scope. Retention applies to platform data, not to code you have already downloaded, which lives in your own repository and hosting from the moment you export it.

Do I need a subscription to keep my landing online?

No. KitekAI runs on pay-as-you-go and credits that never expire. Once you download the code, the site can live on the hosting of your choice without a monthly fee. You return to the platform when you want to generate something new, not because your landing stopped working.

Build your landing with full control

If ownership and governance were your blocker, you now have the facts to decide. Generate a landing, review the preview, download the zip, and ship it wherever you prefer.

Start at https://www.kitekai.co/ai-pipeline.