Terms of Service
Effective 14 August 2026 · Version 3.0
These Terms of Service form a binding agreement between you and NovaBuild covering your access to novabuild.dev, the agent platform, build sandboxes, previews, deployments and everything else we operate under the NovaBuild name. Read them in full. By creating an account, joining a workspace or using any part of the service you accept them.
Plain language summary
- You own your prompts, your data and the application code our agents generate for you.
- NovaBuild is metered in credits. Free workspaces get a one time grant, paid plans include a monthly allowance, and credit packs can be purchased on top.
- AI output can be wrong, insecure or infringing. You are responsible for reviewing and testing anything you ship.
- Projects on the free plan are public by default. Paid plans can keep projects private.
- We can suspend workspaces that abuse compute, break tenant isolation, or violate the Acceptable Use Policy.
The summary is for orientation only. The numbered sections below are the operative text.
1. Who we are and what this covers
NovaBuild is an AI application builder. You describe software in natural language, a team of model driven agents plans and writes the code, the code runs inside an isolated cloud sandbox, and you can preview, iterate and publish the result. These terms cover the web application at novabuild.dev, all subdomains, the public share pages, the documented HTTP endpoints, and any beta or preview capability we make available to you.
These terms apply together with the documents linked from the sidebar. Where a conflict exists, the order of precedence is: a signed order form or enterprise agreement, then the Data Processing Addendum, then these terms, then the other policies.
If you accept these terms on behalf of a company, you confirm that you have authority to bind that company, and "you" means that company.
2. Definitions
- Account
- The individual login identity you register, secured by email and password or a supported identity provider.
- Workspace
- A tenant boundary that owns projects, members, credits, connected keys and billing. Every project belongs to exactly one workspace.
- Project
- A generated application: its file tree, chat history, agent run logs, settings, previews and deployments.
- Agent run
- One execution of a NovaBuild agent, including planning, tool calls, file edits, sandbox commands and the model tokens consumed.
- Credit
- The unit of metering used across the platform. Credits are consumed by agent runs and other metered operations.
- Sandbox
- The isolated cloud container that installs dependencies, runs the dev server, typechecks and builds your project.
- Your content
- Prompts, files, assets, database contents, credentials and any other material you or your members submit.
- Generated output
- Code, text, configuration, migrations and assets produced by the agents in response to your content.
- Connected account
- A third party service you link, such as a model provider key, a source host, a database or a deployment target.
3. Eligibility and account registration
You must be at least 16 years old, or older where your jurisdiction requires it, and not barred from receiving the service under applicable law, sanctions or export controls. You must register with accurate details and keep them current.
- One human per account. Do not share logins. Add teammates as workspace members instead.
- You are responsible for everything that happens under your account, including actions taken by agents you start.
- Keep your password and recovery email secure, and tell us promptly at security@novabuild.dev if you suspect compromise.
- We may refuse registration, or close an account, where we reasonably believe the details are false or the account is used to evade a suspension.
4. Workspaces, roles and tenancy
Everything in NovaBuild is scoped to a workspace. The workspace owner controls membership, plan, credits, connected keys and default project visibility. Access is enforced in the database with row level security, so a member of one workspace cannot read another workspace's projects, chat history, credentials or credit ledger.
| Role | Can do | Cannot do |
|---|---|---|
| Owner | Everything, including billing, plan changes, key vault, deletion of the workspace | Nothing is restricted |
| Admin | Invite and remove members, manage projects, connect keys, start deploys | Change the plan, delete the workspace |
| Member | Create projects, run agents, deploy to preview environments | See full credential values, change billing, remove other members |
| Viewer | Read projects and previews | Run agents, edit files, deploy |
If a workspace owner leaves an organisation, ownership can be transferred by the current owner in settings, or by us on written request from an authorised administrator of the billing entity.
5. Plans, credits and metering
NovaBuild is metered in credits rather than seats alone. Credits are consumed when compute is consumed on your behalf. That covers model tokens for planning and code generation, sandbox time for installs, typechecks and builds, and production deployments.
How a run is priced
Each agent run is priced from the model used, the number of input tokens, and the number of output tokens, at the per model rate published on the models page in the app. Runs executed against your own provider key are billed at a reduced platform rate, because you pay the model provider directly.
Grants and allowances
- Free workspaces receive a one time welcome grant when they are created. There is no daily or monthly refill on the free plan.
- Paid plans include a recurring monthly allowance that resets at the start of each billing period and does not roll over.
- Purchased credit packs sit on top of the allowance, are consumed after the allowance is exhausted, and do not expire while the account is in good standing.
- Retries that we trigger because of our own platform failure are not charged. Retries you request are charged normally, except where the app explicitly labels an action as free.
Credits have no cash value, are not a stored value instrument, are not transferable between workspaces, and cannot be redeemed for money except where a refund is required by law or by the Billing and Refunds policy.
Model pricing moves. We may adjust credit rates to track provider pricing, and we will show the change in the app before it takes effect for new runs. Credits already purchased are honoured at the balance shown, not at a fixed token conversion.
6. Purchasing credits and payment terms
Subscriptions and credit packs are billed through our payment processor. By purchasing you authorise recurring charges for the plan you selected until you cancel. Prices exclude tax unless stated. You are responsible for VAT, GST, sales tax and any withholding required in your jurisdiction, and for providing a valid tax identifier where relevant.
- Subscriptions renew automatically at the end of each period at the then current price.
- Cancellation takes effect at the end of the paid period. Access continues until then.
- Failed payments are retried. Repeated failure pauses agent runs and deployments until payment succeeds.
- Full refund terms, including the cooling off approach for unused credit packs, are in the Billing and Refunds policy.
- Chargebacks raised without first contacting billing@novabuild.dev may result in suspension while the dispute is resolved.
7. Your content and your data
You keep all rights in your content. We do not sell it, and we do not use it to train foundation models. Content is processed to run the service you asked for: to plan and generate code, to install dependencies, to typecheck and build, to render previews, to deploy, and to bill accurately.
You are responsible for having the rights to everything you submit, including code, images, fonts, datasets and any personal data belonging to other people. Do not upload material you cannot lawfully process, and do not upload special category personal data, payment card numbers, government identifiers or health records into prompts or generated projects.
8. Ownership of generated code
As between you and NovaBuild, you own the generated output produced for your projects, and we assign to you whatever rights we may hold in it, effective on generation. You may use, modify, distribute, sell and open source it.
- Ownership is subject to the licences of any third party or open source packages included in the project. Those licences bind you directly.
- Generated output is not unique. Models can produce similar code for similar prompts, so identical or near identical output may also be delivered to other users. We make no exclusivity promise.
- Where a legal system does not recognise copyright in machine generated material, our assignment only transfers what can be transferred, and we will not assert rights against your use.
- You are responsible for licence compliance in what you ship, including attribution and copyleft obligations.
9. Licence you grant to NovaBuild
To operate the service we need a narrow licence. You grant NovaBuild a worldwide, non exclusive, royalty free licence to host, copy, transmit, display, execute and create derivative works of your content and generated output, strictly to provide, secure, support and improve the service for you.
Two extensions apply only where you choose them. If a project is public, the licence extends to displaying that project on its public share page and allowing other users to remix it. If you submit a project to a public gallery or template collection, the licence extends to featuring it there until you remove it.
This licence ends when the content is deleted, subject to backup retention described in the Privacy Policy.
10. AI output and your review duty
Read this section carefully
Generated code is a draft written by a statistical model. It can contain security vulnerabilities, logic errors, insecure defaults, licence conflicts, inaccurate copy and fabricated references. NovaBuild runs automated guardrails and typechecks, but those are aids, not assurance.
Before you ship anything to real users you must review the code, run your own tests, check access control and data handling, and satisfy any regulatory duty that applies to you. Do not use generated output as the sole basis for legal, medical, financial, employment or safety critical decisions.
You must not represent generated output as reviewed, certified or audited by NovaBuild.
11. Agent autonomy and automated actions
NovaBuild agents act on your instruction. Depending on the autonomy mode you select for a project, agents may write files, install packages, run shell commands inside the sandbox, apply database migrations, call connected services and trigger deployments without asking for a separate confirmation each time.
- Review mode: every proposed change is queued as a diff for your approval before it is applied.
- Guided mode: routine edits apply automatically, while destructive operations and deployments ask first.
- Full autonomy: the agent army runs end to end without approvals until it reports back.
Selecting a higher autonomy mode is your instruction to us to act without further confirmation. You remain responsible for the resulting changes, including credit consumption, data written to connected systems, and anything published.
12. Sandboxes and compute fair use
Sandboxes are shared infrastructure. To keep them fast and available for everyone we apply quotas: a maximum number of concurrent sandboxes per workspace, request rate limits on chat and build endpoints, wall clock limits on individual commands, and an idle reaper that stops machines left unused.
- Do not use sandboxes for cryptocurrency mining, distributed compute for hire, torrenting, proxying third party traffic, credential stuffing, bulk scraping or load generation against systems you do not own.
- Do not attempt to escape the sandbox, reach other tenants, or probe the orchestration layer. Report weaknesses instead under the Responsible Disclosure policy.
- Sandboxes are ephemeral. Anything not stored in your project file tree or in a connected database may be lost when a sandbox stops.
- We may lower quotas without notice where necessary to protect platform stability, and we will restore them once the risk passes.
13. Deployments, domains and hosting
Publishing builds your project inside a sandbox and uploads the build artifact to the connected hosting target. You are the publisher of anything you deploy, and you are responsible for its content, its privacy notices and its compliance with law.
- Custom domains require DNS records you control. We verify the records before serving traffic and may stop serving a domain if verification lapses.
- We may take down deployed content that violates the Acceptable Use Policy or that we are legally required to remove.
- Deployed sites inherit the availability characteristics of the hosting provider. We do not promise uninterrupted delivery on any plan without a signed agreement.
- If you disconnect the hosting provider, existing deployments may stop being served, and rebuilding is your responsibility.
14. Bring your own keys and connected accounts
You can store your own model provider keys, database connection strings, deployment tokens and similar credentials in the workspace key vault. Credentials are encrypted at rest, read only inside server side execution, and never returned to a browser. The interface shows a label, the provider and the last four characters only.
- You confirm you are entitled to use each credential and to let NovaBuild act with it on your behalf.
- Usage under your own key is governed by that provider's terms as well as these terms, and you pay that provider directly.
- Rotate or remove a credential at any time in settings. Removal stops future use but does not undo work already performed.
- We are not responsible for provider outages, provider rate limits, provider content policies, or charges you incur on your own key.
15. Project visibility, sharing and remixing
Projects created on the free plan are public by default. A public project has a read only share page that anyone with the link can open, showing the generated file tree and the live preview. Chat history, agent reasoning logs, credentials, environment variables and credit data are never shown on a public page.
- Paid plans create private projects by default, and visibility can be changed per project at any time.
- Making a project public grants other users permission to remix it, which copies the file tree into their own workspace.
- Never place secrets in project files. Use the key vault or environment settings instead.
- Making a project private again removes future access, but copies already remixed by others remain theirs.
16. Acceptable use and enforcement
The Acceptable Use Policy is part of these terms. It prohibits, among other things, malware, phishing, spam, harassment, sexual content involving minors, unlicensed regulated activity, infringement, and any use designed to break platform isolation or evade metering.
Enforcement is proportionate. Depending on severity we may warn you, throttle a workspace, disable a specific project or deployment, suspend agent runs, or terminate the account. For clear and severe abuse, including content that endangers people, we act immediately and without prior notice, and we may report it to the relevant authority.
17. Third party services and open source
NovaBuild depends on model providers, sandbox runtimes, hosting, email delivery, payment processing and analytics. Those subprocessors are listed on the Subprocessors page. Generated projects also install open source packages from public registries.
We do not control third party services and we are not liable for their acts, outages, pricing or content decisions. Where you connect a third party account, you authorise us to exchange the data needed to perform the action you requested.
18. Privacy and data protection
Our handling of personal data is described in the Privacy Policy. Where you use NovaBuild to process personal data of your own users, you are the controller and we act as your processor under the Data Processing Addendum, which is incorporated into these terms by reference and applies automatically without separate signature.
19. Confidentiality
Each party may receive non public information from the other. The receiving party will use it only to perform under these terms, protect it with at least reasonable care, and disclose it only to people who need it and are bound by similar duties. This does not apply to information that is public through no fault of the receiver, independently developed, or lawfully received from a third party. Disclosure required by law is permitted, with notice where lawful.
20. Feedback and publicity
If you send us feedback, ideas or bug reports, we may use them without restriction or payment. We will not identify you as the source without permission. We will not use your name, logo or project as a public reference without your written consent, except that public projects and gallery submissions may be shown as described in section 9.
21. Service levels, availability and beta features
Unless you have a signed agreement that says otherwise, the service is provided without a contractual uptime commitment. Our operational targets and maintenance approach are described in the Service Levels and Support page.
Features labelled alpha, beta, preview or experimental may change or disappear, may be rate limited more aggressively, and are excluded from any service level target. Do not build a production dependency on them without telling us first.
22. Support
Support is provided by email and in app for all plans, with response targets that vary by plan and are published on the Service Levels and Support page. Support covers the platform itself. It does not include writing your application for you, debugging code you wrote outside NovaBuild, or acting as an on call engineer for your deployed product.
23. Suspension
We may suspend all or part of the service where:
- your use threatens the security, integrity or availability of the platform or another tenant;
- we reasonably suspect fraud, credit manipulation, or evasion of a prior suspension;
- payment is overdue after reminders;
- we are required to act by law, a court, or a provider we depend on;
- the Acceptable Use Policy is breached.
We aim to give notice and a chance to fix the problem, unless doing so would increase harm. Suspension for cause does not entitle you to a refund of the affected period.
24. Term, cancellation and deletion
These terms apply while you have an account. You may cancel a subscription or delete a workspace at any time from settings. Deletion removes projects, files, chat history, agent logs and credentials from the live systems, and the associated credit balance is forfeited.
- Export your project files before deletion. After a workspace is deleted we cannot restore it.
- Following termination we keep an export window of 30 days for account level data, unless you asked for immediate erasure.
- Encrypted backups roll off on the schedule described in the Privacy Policy.
- Sections that by their nature should survive, including ownership, confidentiality, disclaimers, liability, indemnity and governing law, survive termination.
25. Warranty disclaimer
To the maximum extent permitted by law, the service is provided on an "as is" and "as available" basis without warranties of any kind, whether express, implied or statutory, including merchantability, fitness for a particular purpose, title, accuracy and non infringement. We do not warrant that the service will be uninterrupted, that generated output will be correct, secure, original or fit for your purpose, or that defects will be corrected. Nothing in these terms excludes rights that cannot lawfully be excluded, such as non excludable consumer guarantees.
26. Indemnity
You will defend and indemnify NovaBuild against third party claims arising from your content, your generated applications once you deploy or distribute them, your breach of these terms or the Acceptable Use Policy, your use of connected accounts, and your handling of personal data. We will notify you of the claim, let you control the defence for claims that only seek money, and cooperate at your expense. You may not settle in a way that admits our fault or imposes an obligation on us without our consent.
27. Limitation of liability
To the maximum extent permitted by law neither party is liable for indirect, incidental, special, consequential or punitive damages, nor for lost profits, lost revenue, lost data, or the cost of substitute services, even if advised of the possibility.
Our total aggregate liability arising out of or relating to the service is limited to the greater of the amounts you paid to NovaBuild in the twelve months before the event giving rise to the claim, or one hundred United States dollars. These limits do not apply to your payment obligations, to either party's breach of confidentiality, or to liability that cannot be limited by law.
28. Changes to the service and to these terms
We iterate quickly and may add, change or withdraw features. Where a change materially reduces functionality you already rely on, we will give reasonable notice in the app or by email.
We may update these terms. The effective date and version number at the top always reflect the current text. Material changes are announced at least 14 days in advance for paid plans. Continuing to use the service after the effective date means you accept the new version. If you do not accept it, stop using the service and cancel before that date.
29. Governing law and disputes
These terms are governed by the laws of the jurisdiction in which the NovaBuild contracting entity is established, without regard to conflict of law rules, and the courts of that jurisdiction have exclusive jurisdiction. If you are a consumer, you keep the protection of the mandatory law of your country of residence and may bring proceedings there.
Before filing a claim, contact legal@novabuild.dev and give us 30 days to resolve the issue informally. Either party may seek injunctive relief at any time to protect intellectual property or confidential information.
30. General terms
- Entire agreement: these terms and the linked policies are the whole agreement and replace prior discussions.
- Assignment: you may not assign without our consent. We may assign to an affiliate or in a merger or sale of assets.
- Severability: if a provision is unenforceable, the rest stays in force and the provision is read down to the minimum extent needed.
- No waiver: not enforcing a right is not a waiver of it.
- Force majeure: neither party is liable for delay caused by events beyond reasonable control, including provider outages, network failures and government action.
- No agency: nothing here creates a partnership, joint venture, employment or agency relationship.
- Notices: we contact you at your account email. You contact us at legal@novabuild.dev.
- Export and sanctions: you confirm you are not located in an embargoed territory and are not on a restricted party list.
31. Contact
General and legal: legal@novabuild.dev. Billing: billing@novabuild.dev. Security and vulnerability reports: security@novabuild.dev. Privacy requests: privacy@novabuild.dev.
This document is published by the NovaBuild team as general information about the service. It is not legal advice, and it is not a certification or an independent audit of NovaBuild or of any third party. If anything here is unclear, or you need a countersigned copy for procurement, email legal@novabuild.dev.