Ownership, hosting & security

Three questions every technical buyer asks first. Straight answers below.

Who owns the code?

You. 100%.

When you sign up, we fork our public core repo into your GitHub organization. From that moment, the repo is under your control. Every commit thereafter — whether written by you, your team, or the AI agent working on your behalf — is authored inside your fork. We do not have write access unless you invite us.

If you cancel App-Agent tomorrow, you keep the repo, the deployments, the code, and the running infrastructure. Nothing "goes away." The only thing you lose is our team's ongoing support and the AI agent's write access to your fork (you'd fall back to Free-tier read-only if you want to keep browsing).

Who hosts your code?

You do. Your Cloudflare account (or AWS, or GCP on Enterprise). Not us.

The full stack:

• GitHub org — yours. We recommend you set a "core-maintainers" team so we can review PRs during onboarding.
• Cloudflare Pages — yours. We help you set up the account during your first session; you own the API tokens and can revoke our access anytime.
• DNS — yours. You keep control of your domain.
• Databases — depends on which template you use. Cloudflare D1 stays in your CF account. Supabase / Postgres / SQLite — all yours to set up and own.

We do not run any hosted product. There is no "app-agent.io backend" your production traffic depends on.

Who has access to your data?

By default: only you and whoever you invite to your GitHub org and Cloudflare account.

During onboarding sessions, you typically give us temporary access to review setup, unblock issues, and pair on the first few templates. This is:

• Read-only unless you explicitly grant write during a specific session
• Revocable anytime via GitHub org settings and Cloudflare API token rotation
• Never persisted on our infrastructure — we don't clone your repo, we work in your repo remotely via GitHub

Your customers' data — whatever your product collects — never touches App-Agent servers. It flows from your users → your Cloudflare deployment → your database of choice. We literally don't have the credentials to see it.

Compliance posture

App-Agent itself is not SOC 2 / ISO 27001 / HIPAA certified because App-Agent is not a data processor. Your compliance obligations depend on your hosting provider (Cloudflare has SOC 2, ISO 27001, PCI DSS out of the box) and your data-handling choices, not on us.

If your business is subject to specific compliance requirements (HIPAA, PCI, financial services), Enterprise tier includes:

• Guidance on hosting configuration to meet your compliance regime
• Optional dedicated infrastructure (isolated Cloudflare account, or move to AWS/GCP)
• DPA (data processing agreement) available on request
• No use of your data or code for AI training

What if you cancel?

• Your code, your repo, your infrastructure — all intact.
• The AI agent loses write access to your fork on the day your subscription ends. It can still read on Free tier if you want to keep browsing.
• We keep no persistent copy of your work.
• No data export step needed — nothing to export because we never held anything.
• Templates you've installed keep working; upstream core updates keep being publishable from our end, and you can pull them in at your leisure or ignore.

Effectively: cancellation looks like the AI stops answering your requests. Everything else keeps running.

What if we cancel App-Agent?

Even if the company disappears tomorrow, you're fine. core and the templates are in public / customer-accessible GitHub repos. Your fork, your deployments, your infrastructure — all continue running. You could hire any Nuxt developer to keep iterating on the codebase; it's standard Nuxt 4 with no lock-in dependencies.

What comes next

• Getting started — what happens after you book a call.
• FAQ — remaining common questions.