The agreement, in language you can read.

1. What you own

You own everything the builder produces for you. The code, the content, the design and the database schema are yours, with no licence back to us beyond what we need to run the service you asked for — storing your files, compiling a preview, and serving your published site while you are hosting it here.

We claim no ownership of your output and take no share of what you make with it. You may sell it, relicense it, hand it to a client, or delete it. If you leave, push it to your own repository and nothing about it stops working.

2. What you are responsible for

The content you ask for and publish, including anything you upload. In particular: if you upload an image, a font or a video, you are asserting you have the right to use it. Images the builder sources for you come from libraries with licences that permit commercial use and are attributed where the licence requires it — but an asset you bring is yours to be sure about, and any claim arising from it is yours.

You also keep your account secure. Anything done with your session is treated as done by you.

3. What we will not host

We will suspend a project or an account for any of these, and this list is short because it is meant to be exhaustive rather than decorative:

• Phishing, or any page impersonating a real person, company or public body.
• Malware distribution, or pages designed to exploit a visitor’s browser.
• Content sexualising minors, or non-consensual intimate imagery.
• Fraud: fake storefronts, fabricated reviews, or invented credentials.
• Using the build engine to attack other systems, or deliberately circumventing the metering.

A suspension deletes nothing and is reversible; we record a reason, and we will tell you what it was. If we have got it wrong, say so and we will look again.

4. Credits and what they are

Plans are metered on estimated model spend rather than tokens, and one credit is roughly one build turn on a fast model. Credits are a unit of allowance, not a currency: they are not transferable, not refundable for cash, and they reset at the start of each monthly period rather than accumulating.

The figures are estimates from a local copy of provider list prices, so they can differ slightly from a provider’s invoice. If you want no estimate in the loop at all, add your own provider key and nothing is metered.

5. When a build fails on our side

A turn that failed because of our fault should not cost you credits. If a build errors, hangs, or produces nothing usable because something here broke, tell us and we will put the credits back on your account. We would rather return them on request than argue about whose fault a failure was.

This does not cover a build that worked and that you did not like. Iterating is what the product is for, and each iteration costs what it costs.

6. Billing and cancellation

• Plans are monthly, charged in advance through Razorpay.
• Cancelling takes effect at the end of the period you have already paid for. You keep the plan until then; we do not remove access the moment you click cancel.
• Nothing is deleted when a plan ends. Your projects and published sites stay exactly as they are, under the free plan’s limits.
• If a payment fails, the plan reverts to free limits until it is settled — and the interface will say that a payment failed rather than silently downgrading you.
• If we raise a price, existing subscribers are told before it applies to them, not after.

7. Hosting

Hosting is included in every plan. Shared tiers share capacity, which means somebody else’s traffic spike can be felt — that is the honest description of shared hosting, and the reason the higher tiers offer a dedicated instance. We do not promise a specific uptime figure, because we are not yet in a position to back one with a credit, and inventing a number would be worse than admitting that.

If a published site becomes an operational problem for other customers — genuinely extreme traffic, or use as a file host — we will contact you about moving it rather than pulling it down without warning.

8. Our liability

The service is provided as it is. We will not be liable for lost profits, lost data or consequential loss, and our total liability is limited to what you paid us in the twelve months before the claim.

Said plainly rather than hidden: keep your own copy. The product is built so that you can — push to your repository, keep the database in your account — and doing so is the only real protection against anything here going wrong.

9. Ending it

You can stop at any time. We may end an account for a breach of section 3, or with reasonable notice if we discontinue the service — in which case we will give you time and a way to take your projects with you.

10. Changes to these terms

We will tell account holders about a material change rather than editing the date at the top and hoping. Continuing to use the service after a change means accepting it.

11. Contact

Questions about any of this: get in touch.