Terms of Service
Nimos Websites ("we", "us") builds, hosts, and maintains websites from Kelowna, British Columbia, Canada. These terms apply when you engage us or use nimoswebsites.com.
Scope and payment
Every project starts with a written scope: what we build, what it costs, when it's live. That document is the agreement for the work, and the price in it is fixed for the scope it describes. The deposit named on it starts the work, and the balance is due when the site is live on your domain. Anything outside the scope gets quoted before it's built — no surprise invoices.
The agreement
Before work starts you accept these terms, our privacy policy, and the statement of work built from your scope. The acceptance is recorded with the date, the version of each document, and the hash of the text you were shown. Signatures are electronic and are valid under British Columbia's Electronic Transactions Act; you get a copy, and so do we.
What “done” means
Delivery is checked against the published audit at nimoswebsites.com/audit — twelve checks, each of which can be run by someone who did not build the site. If a check fails, we fix it and run the audit again at no charge, without limit. If it passes, the delivery obligation for the agreed scope is met. The audit is evidence, not a guarantee of business results, and it does not remove either side's right to disagree about what the scope said.
Your responsibilities
You confirm the information you give us is accurate and that you have the right to use the content, images, and trademarks you provide. Claims about your business — prices, services, certifications — are yours to verify; we publish what you approve. You are responsible for the legality of your business and its compliance with the laws that apply to it.
Delivery
Once an invoice is paid, the deliverables — code, design, content, and the database — are delivered. There is no separate licence, buyout, or assignment to obtain: payment in full is the transfer. We keep our internal tools and production systems. Third-party components remain under their own licenses.
Hosting, and taking the work
A build runs on infrastructure we manage: our repository organisation, our hosting team, our database. That is the default because it is where we can keep it patched, backed up and fast, and because a site we cannot reach is a site we cannot fix.
There are two ways to hold it, and the choice is yours at handover.
Hosted by us. The site stays on our infrastructure for a monthly hosting rate, agreed in writing before the build starts and cancellable with notice. The rate pays for running the site, not for owning it: the design, the copy and the code belong to you on payment in full either way.
Taken by you. You sign the handover record and the work moves: the repository, the deployment project, the domain records and the database. We start that transfer when the final payment clears. Two of the steps need you to accept an invitation in your own account — nobody can push ownership or credentials into an account that has not authorised it — and we walk those steps with you on a call. Once the last step completes, our maintenance and operational responsibility for that build ends.
Nothing is withheld to keep you. The only reason a handover waits is an unpaid invoice, and the only reason it needs you is that the accounts have to be yours.
Third-party services
Sites run on services such as Vercel, Neon Postgres, Shopify, Stripe, Google, and Resend (email delivery). Their terms govern your use of them; we configure them for you but do not control their outages or policy changes.
We email you about your project. Those messages identify us, carry our address, and include a one-click unsubscribe. We do not send you marketing you did not separately ask for.
No guaranteed business results
We build fast, accessible, well-structured sites and stand behind the work. We do not guarantee specific revenue, traffic, or search rankings.
Service and liability
We check hosted sites on a stated schedule and fix issues we find; any extended service level is written into your scope document rather than assumed. We do not promise round-the-clock monitoring or an instant response — that is a term you negotiate with us, not a claim we publish. To the extent permitted by law, our total liability is limited to the fees you paid for the work in question, and we are not liable for indirect or consequential losses.
Ending the relationship
Either side can end ongoing services with written notice. The code, design and content are delivered, and if you want the accounts moved to you — repository, deployment project, domain records, database — that transfer completes on the handover runbook described above, and the handover record is issued only when every required step is verified. Ending a hosting subscription does not take the work away from you; it moves it.
Clients outside Canada
These terms apply wherever you are. Where your review requires it, we will sign your data processing addendum and standard contractual clauses, or agree one in writing; the governing law can be varied by written agreement in the signed contract.
The documents
This page is the terms. The privacy policy says what we do with personal information. The data processing addendum applies where you need one. The audit is the checklist delivery is measured against. When the work moves to your accounts, the handover record lists every step and the date it was verified. Where a signed statement of work and this page differ about the scope, the statement of work is the record of the scope; where they differ about a term, this page governs.
Governing law
These terms are governed by the laws of British Columbia, Canada. Questions: use the form at nimoswebsites.com.