Terms of service
What you can expect from us, and what we expect from you. Written to be read rather than to be impressive.
Last updated 30 August 2026.
On this page
- What this agreement covers
- Your account and your access code
- What you may publish
- Plans, limits and what happens at the limit
- Paying, and stopping paying
- Domain names
- Availability, suspension and ending the service
- Your data, and your backups
- Liability
- If somebody comes after us because of you
- Which law applies, and where a dispute is heard
- How you agreed to this, and what we recorded
- The rest
What this agreement covers
DashPloy publishes websites and applications that you, or an AI assistant acting for you, send to us. These terms apply to the dashploy.com control panel, the API and MCP server behind it, and every site served from dashploy.app.
By creating an account or publishing anything through it, you agree to what is written here. If you do not agree, do not publish.
We may change these terms. When a change materially affects you we will say so by email before it takes effect, and the date at the top of this page always tells you when it last changed.
Your account and your access code
You need an account to publish. You are responsible for what happens under it.
Publishing is authorised by an access code that you paste into an AI assistant. Treat it as a password: anyone holding it can publish to, change or delete your websites. If you believe a code has been seen by somebody else, revoke it from the codes page and create a new one — that takes effect immediately.
Some capabilities need a verified account rather than a paid one. Verification exists to make abuse expensive, not to sell you anything, and signing in with Google verifies you straight away.
You must be old enough to enter a contract where you live, and you must not share one account between people who should not see each other’s websites.
What you may publish
Your content stays yours. We do not claim ownership of anything you publish. You give us only the permission we need to run the service: to store your files, serve them to visitors, and keep the copies described in the privacy notice.
You are responsible for having the right to publish what you publish, and for it being lawful where it is read.
These are not allowed, and an account doing any of them may be suspended without notice:
- Pages that impersonate another business or person to collect passwords, card numbers or identity documents.
- Malware, or anything whose purpose is to compromise a visitor’s device or another system.
- Content that is illegal where it is served, including material that sexually exploits children.
- Using the platform to attack, scan or send unsolicited bulk messages to anyone.
- Deliberately working around the limits of your plan, the network restrictions applied to applications, or the account verification checks.
Uploaded and deployed files are screened automatically for a narrow set of signals, mostly phishing pages. That screening is a filter, not a guarantee, and it is not a substitute for your own judgement about what you put online.
Plans, limits and what happens at the limit
There is a free plan and two paid ones: Free (free), Starter ($4.99 a month) and Pro ($14.99 a month). What each includes is on the pricing page, and the same figures are what the platform enforces.
Every plan has monthly allowances — requests, computing time, storage, file writes — and a daily limit on how many times a site may be republished. Requests means individual files fetched by a browser, not page views: one page with ten images is eleven requests.
At the limit, what happens depends on the plan. A free account’s websites stop being served until the period resets or you move up, and visitors see a short page saying so. A paid account is given a grace band above its allowance where sites are still served but more slowly, and only stops beyond that.
Nothing is deleted when you hit a limit, and everything comes back on its own when the period resets. We email you before you get there.
We may change plan prices and allowances. An increase will be told to you by email before it applies to you, and you can cancel rather than accept it.
Paying, and stopping paying
Paid plans are billed monthly in advance through Stripe. We never see or store your card details.
You can cancel at any time. Cancelling stops the next charge; it does not refund the month you are in, and your account stays on the paid plan until that month ends.
If a payment fails we will retry it and tell you. If it keeps failing the account moves to the free plan, which may take websites offline if they are over the free allowances.
Except where the law requires otherwise, monthly fees already paid are not refundable.
Domain names
You can connect a domain you already own, or buy one through us. Connecting is free.
A domain bought through us is registered in your name with a registry through our registrar partner. Registration is final: the moment a registry accepts it the money has left, and there is no way to undo it. For that reason a purchase cannot be cancelled or refunded once the name is registered. If registration fails, you are refunded in full.
Registration and renewal prices are different, often substantially, and we show both together everywhere we quote either — in the dashboard, in the API, and on the invoice. Renewal prices are set by the registry and can change; we will tell you before a renewal at a higher price.
Renewals are charged before the registry’s expiry date, with retries if a payment fails. If every attempt fails the domain will lapse, which is not something we can reverse for you.
Availability, suspension and ending the service
We work hard to keep the platform up and we publish what we know about its health on the status page. There is no uptime guarantee, no service level agreement, and no promise that any particular website will be reachable at any particular moment.
We may take the platform down for maintenance, and parts of it may fail without warning. Where an interruption is planned and long we will try to say so first, but we do not commit to notice, and an outage is not a breach of these terms.
Much of what makes the service work belongs to other companies — Cloudflare serves and stores every published website, Neon holds the database, Stripe takes the payments, and the registrar registers the domains. Their outages become ours, and we have no more control over them than you do. We are not liable for a failure caused by one of them.
We may suspend or remove a website, or suspend or close an account, at any time and without notice — for anything listed above, for generating costs far outside its plan, for a credible abuse report, or because we are legally required to. Where the situation allows it we will tell you first and explain what to change, but we do not promise to.
You can delete a project or your whole account at any time. Deleting a project stops it being served and removes the files, snapshots and logs held for it. Deletion is immediate and irreversible: we cannot get any of it back for you, and neither can anyone else.
We may end the service, or your access to it, with reasonable notice. If we do so and you are on a paid plan, we will refund the unused part of the month.
Your data, and your backups
This is the part people are most surprised by, so it is said plainly: we are not a backup service, and you should not treat us as one.
The copies we keep — the snapshot of each published version, the files behind a live site — exist so the platform can serve and roll back your website. They are there for our purposes, not as your archive. We do not guarantee that any of them is complete, current, recoverable, or there at all when you go looking.
You are responsible for keeping your own copy of everything you value: your source code, your content, the data your application stores, and anything your visitors send you. Keep it somewhere that is not our servers — your own machine, your own repository, your own backup. There is no route anywhere on this platform that hands your source back to you, and you should not build a workflow that assumes there will be.
Data can be lost or corrupted here, and one day some of it will be. Storage fails, a deployment overwrites what was there, deletes cannot be undone, an access code in the wrong hands can wipe a project in a second, and a mistake by you, by your assistant, or by us can destroy work with no way back. To the fullest extent the law allows, we are not responsible for any of that — for the loss, corruption, deletion, disclosure or unavailability of your content or your application’s data, however it happens.
If a backup matters to you, make one before you publish, and keep making them. That sentence is the whole of our advice on the subject.
Liability
The service is provided AS IS and AS AVAILABLE. To the fullest extent the law allows, we make no warranties of any kind — express, implied or statutory — and we specifically disclaim the implied warranties of MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE and NON-INFRINGEMENT, along with any warranty arising from a course of dealing or from the way the service is ordinarily used.
We do not warrant that the service will be uninterrupted, secure, timely, error-free or free of harmful components; that it will meet your requirements; that defects will be corrected; or that anything you publish through it will stay available, intact or recoverable. No advice from us, in any form, creates a warranty that is not written here.
To the fullest extent the law allows, we are not liable for any indirect, incidental, special, consequential, exemplary or punitive damages, or for loss of profits, revenue, business, goodwill, opportunity or data — whether the claim is made in contract, in negligence or otherwise, and even if we were told that such loss was possible. This applies in particular to lost or corrupted data, which is dealt with in the section above.
Where we are liable despite the above, our total liability to you for all claims taken together is limited to the greater of the fees you actually paid us in the twelve months before the event giving rise to the claim, or fifty dollars. That is the cap whether there is one claim or many.
These limits apply even if a remedy written here is found to have failed of its essential purpose, and they carry on applying after your account and this agreement end.
We are not responsible for what other people do. That includes the content, conduct and security of the websites our customers publish, anything that happens to a visitor to one of those websites, and any action taken by an AI assistant holding your access code — an assistant acts for you, so what it publishes, changes or deletes is your responsibility rather than ours.
Nothing here limits or excludes liability that cannot lawfully be limited or excluded, including for death or personal injury caused by negligence, for fraud or fraudulent misrepresentation, or any right you have as a consumer that the law does not let you sign away. Some places do not allow the exclusion of implied warranties or of certain damages, so parts of this section may not apply to you; the rest of it still does, and where a limit cannot be enforced in full it applies as far as the law allows.
If somebody comes after us because of you
You publish under your own name and on your own responsibility. If a third party brings a claim, demand or proceeding against us because of what you published, how you used the service, a right you turned out not to have, a law you broke, or something one of your visitors suffered, you agree to defend us against it and to cover what it costs us — including reasonable legal fees, damages, settlements and fines.
This covers us, anyone working for us, and our suppliers. It does not cover a claim that arises from our own fraud or our own wilful misconduct.
We will tell you promptly about any claim we want covered, and we will not settle one in a way that puts an obligation on you without asking you first. You may run the defence with lawyers we reasonably approve, and we may take part in it at our own expense.
Which law applies, and where a dispute is heard
DashPloy is operated from Edmonton, Alberta, Canada.
These terms, and any dispute arising out of them or out of your use of the service — whether framed as a contract claim, a negligence claim or anything else — are governed by the laws of the Province of Alberta and the federal laws of Canada that apply in it, without regard to conflict-of-laws rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
The courts of the Province of Alberta, sitting in Edmonton, have exclusive jurisdiction, and you and we both submit to them. We may still apply to a court anywhere for an injunction to stop something happening, because that is the remedy that has to be available where the harm is.
If you are a consumer, none of this takes away the protection of the mandatory consumer laws where you live, or your right to bring a claim in the courts your own law gives you access to. A choice of law cannot remove a right your home jurisdiction does not let you sign away, and we are not attempting it.
Any claim must be brought within two years of when it arose, unless the law where you live gives you longer.
Each of us brings a claim on our own behalf. Neither of us joins a claim to somebody else’s as a class or representative action, to the extent the law allows that to be agreed.
How you agreed to this, and what we recorded
You agreed to these terms by ticking the box on the sign-up page before your account was created. That is a deliberate step rather than a line of small print under a button: the clauses above are worth nothing if nobody can show you were shown them.
When you ticked it we recorded the exact sentence you were shown, the version of these terms it referred to, the date and time, the IP address the request came from, and the browser that sent it. We keep that record for as long as it could matter, which means it outlives the account — deleting your account does not delete the fact that you once agreed, and the privacy notice says so in the same words.
When we change these terms in a way that materially affects you, we will ask you to agree again the next time you sign in, and record that in the same way. A correction that changes no obligation — a typo, a clearer sentence — does not interrupt you, and the date at the top of the page still moves.
You can read the current terms at any time from the footer of every page.
The rest
If any part of these terms turns out to be unenforceable, it is narrowed only as far as it has to be, or removed, and everything else stays in force.
Not enforcing something once does not mean we have given it up.
You may not transfer your rights under these terms to somebody else without our agreement. We may transfer ours as part of a sale or reorganisation of the business.
These terms, together with the privacy notice and the plan details on the pricing page, are the whole of the agreement between us about the service, and they replace anything said earlier.
The sections on what you may publish, on your data and your backups, on liability, on indemnity, and this one, carry on applying after your account ends.
These terms are written in English. If we ever publish a translation and the two disagree, the English version is the one that governs.
Questions about this page
Email support@dashploy.com and a person will answer. If something here is unclear, that is worth telling us about.