Terms of Use
Last updated: June 2, 2026
Welcome to AppForge. By using the platform, you agree to these Terms of Use. These terms apply to the website, user accounts, app-building workflows, provider connections, and related AppForge services.
If you use AppForge on behalf of an organization, you confirm that you are authorized to accept these terms for that organization and that your team users will comply with them.
1. AppForge Services
AppForge is an AI App Factory Platform that helps transform ideas into requirements, design, scaffold, code, QA, and deployment through multi-role AI agent workflows.
The platform may recommend app shells, muai-kits, design tokens, providers/models, cost estimates, and approval checkpoints to improve build quality and reduce rework.
Results may vary based on your inputs, selected providers/models, API keys, templates, kit catalog, integrations, and limitations of external systems.
2. Accounts and Security
Users must provide accurate account information and are responsible for protecting passwords, tokens, API keys, OAuth connections, and other credentials.
Activity under your account is your responsibility unless caused directly by an AppForge system error.
If you suspect unauthorized access, you should change passwords, revoke keys, and contact support promptly.
3. Ownership of Code and Projects
You own the application AppForge generates for you — including the AI-generated feature code created from your idea — with full rights to use, modify, distribute, sell, and re-license it, provided your inputs do not infringe third-party rights.
The scaffold, kits, and build tooling embedded in your application are © MuAI, licensed to you on a perpetual, irrevocable, royalty-free basis for use within your application — but they may not be extracted and redistributed as a standalone template library, app generator, or competing kit collection (see the LICENSE and NOTICE files in your generated app).
Apps generated on the free/preview plan must keep the “Built with AppForge” badge; paid builds may disable it (NEXT_PUBLIC_APPFORGE_BADGE=off).
Every build carries provenance marks — e.g. a digitally signed .appforge/manifest.json and build identifiers in files — proving it was generated by AppForge. These marks transmit nothing back to us.
Pushing code to your GitHub repository does not mean AppForge certifies that the code is suitable for every use case. You remain responsible for review and testing before production.
4. AI-generated Output
AI-generated output may contain errors, omissions, insecure logic, mismatched requirements, or issues unsuitable for certain laws or industry standards. Users must review before real-world use.
AppForge provides checkpoints, QA, readiness checks, and approval flows to reduce risk, but it cannot guarantee that outputs are free from bugs or vulnerabilities.
Users should review business logic, security, privacy, accessibility, performance, licensing, payment flows, and deployment configuration before releasing to end users.
5. User API Keys and Providers
Some features allow users to configure their own providers/models and API keys. Use of your key is governed by that provider's terms, pricing, rate limits, and policies.
You are responsible for costs or usage incurred under your own keys, including tokens, API calls, deployments, storage, third-party services, or quota overages.
You should not place secrets, passwords, private keys, or confidential data into prompts unless necessary and you understand the risks of the selected provider/workflow.
6. Prohibited Use
You may not use AppForge to build or distribute unlawful, deceptive, infringing, privacy-invasive, malware, phishing, spam, or attack-oriented systems.
You may not attempt unauthorized access to another user's account, data, projects, secrets, or infrastructure, or bypass rate limits, payment gates, or security controls.
You may not submit sensitive personal information about others without appropriate rights or a lawful basis for processing it.
7. Billing, Subscriptions, and Payment
Some features may require subscriptions, credits, project fees, or separate charges. Prices and access rights may change according to packages displayed in the system.
Payments may be processed by external providers such as Stripe. Some payment information is governed by the payment provider's own terms and privacy policy.
Trials, discounts, or special packages may include additional terms that apply together with these Terms of Use.
8. Integrations and Deployment
When you connect GitHub, Cloudflare, OAuth, DNS, email, storage, or other external services, you authorize AppForge to act within the scope required for the workflow you choose.
Users are responsible for reviewing repository permissions, environment variables, DNS records, deployment targets, production URLs, billing, and security settings of external services.
AppForge is not responsible for outages, policy changes, quotas, rate limits, suspensions, or errors caused by external services, though it will try to surface helpful status and error information.
9. Service Availability and Changes
We may improve, modify, add, remove, or discontinue features to improve quality, security, provider compatibility, or business fit.
We do not guarantee uninterrupted service, but we aim to maintain stability and recover from incidents when they occur.
Some information may be temporarily unavailable during maintenance, migrations, provider outages, or events outside our control.
10. Limitation of Liability
AppForge is provided to accelerate and improve software development. It does not guarantee business outcomes, legal compliance, security fitness, or suitability for every environment.
Users are responsible for decisions to use outputs, production deployments, services offered to their customers, and the consequences of applications they publish.
To the extent permitted by law, AppForge is not responsible for indirect damages, lost revenue, data loss, downtime, or costs arising from use or inability to use the service.
11. Suspension or Termination
We may limit, suspend, or terminate accounts or projects that violate these terms or create risk to the platform, other users, providers, or third parties.
Users may stop using the service, close accounts, or cancel subscriptions through supported channels, while remaining responsible for charges incurred before cancellation.
12. Changes to These Terms
We may update these terms when the service, AI providers, laws, pricing, or security practices change. The latest update date is shown on this page.
Continued use after updated terms take effect means you accept the revised terms. If you do not accept them, you should stop using the service and contact support about related data or subscriptions.