Terms
Terms of service
How work is scoped, what it costs, who owns what we build, and what happens if either side wants out.
01What these terms cover
These terms apply to this website and to work we do for you unless a signed agreement between us says otherwise. Where a signed agreement and this page disagree, the signed agreement wins.
Using the site means accepting the parts about the site. Nothing on the site is an offer of work by itself. Work starts when we both put a scope in writing and you approve it.
02How work is agreed
Every engagement starts with a written scope: the process being automated, the systems it touches, what counts as done, and the price. You approve it before anything is built.
If the job turns out to be different from what the scope described, and that happens more often than anyone likes, we stop and tell you what changed and what it does to the price. We do not quietly widen the work and bill for it afterwards.
03Money
Build projects are invoiced half at the start and half when the automation is live and you have signed off on it. Monthly work is invoiced at the start of each month.
Invoices are due in fourteen days. Prices exclude any tax we are required to collect and exclude third party costs such as software subscriptions and AI provider usage, which are billed to your own accounts and stay under your control.
If an invoice is more than thirty days late we may pause work until it is settled. We will tell you before that happens, not after.
04What you are responsible for
For an automation to be built, we need access to the systems it runs on, someone at your end who can answer questions about how the process actually works, and permission to use the accounts involved.
You confirm that you are allowed to grant that access, that the data you hand us is data you are entitled to hand over, and that the process we are automating is lawful where you operate. We do not audit that for you.
Where work stalls because access or answers do not arrive, timelines move. We will say so at the time rather than at the end.
05Who owns what
Yours. Your data stays yours throughout, and it stays in your accounts. Once the final invoice for a project is paid, the automations, prompts, scripts and configuration built specifically for you are yours to keep, change, or take to somebody else.
Ours. The general tools, patterns and internal libraries we bring to every job stay ours. You get a permanent licence to keep using them inside what we built for you. That is the normal arrangement and it is what stops every client paying to rebuild the same plumbing.
We will not name you publicly or quote you without asking first, and a no costs nothing.
06AI providers and third party services
Most automations call services we do not run: AI model providers, your CRM, your email, your accounting software. Their terms apply to their part of the chain, and their outages are their outages.
We tell you which providers a build depends on before it is built, and we set them up so your content is not used to train anyone's models. Details of that are on the security and data page.
07What an automation is and is not
Automations run software. They do not exercise judgement, and language models get things wrong. Every system we build for a decision that carries real consequence keeps a human approval step in it, and we will argue for that step if you ask us to remove it.
Nothing we build is legal, financial, medical or tax advice, and it does not make you compliant with anything. Where a workflow touches a regulated area, that stays your responsibility and your lawyer's.
Estimates on this site, including the calculators, are estimates. They are arithmetic on numbers you supplied, not a forecast of your results.
08Support, changes and things breaking
Build projects include thirty days of fixes after go live. If something we built does not do what the scope said it would, we fix it and you pay nothing.
After that window, and for anything caused by a system outside the automation changing under it, an API version retiring or a tool being reconfigured, monthly management covers it. Without monthly management it is billed as new work.
09Ending it
Monthly work runs month to month. Either of us can end it with thirty days of notice, and there is no exit fee. We hand over credentials, documentation and access, and we remove our own access to your systems.
A build project can be stopped at any point. You pay for the work done up to that point and you keep it.
Either of us can end an engagement immediately if the other breaks these terms and does not put it right within fourteen days of being told.
10Liability
We do this work carefully and we stand behind it. What we cannot do is carry unlimited risk for systems that run inside your business, on your accounts, alongside software we do not control.
So: our total liability for any engagement is capped at what you paid us for it in the twelve months before the claim. Neither of us is liable to the other for indirect losses, lost profits or lost data beyond that cap. Nothing here limits liability that the law does not allow us to limit, including for fraud.
11Confidentiality
Anything you tell us about how your business runs stays between us, and the same applies in reverse. That holds during the work and after it ends. We will sign your NDA if you have one.
12Using this website
The writing, code and design on this site are ours. Read it, quote it with a link, send it to a colleague. Do not republish it as your own or scrape it wholesale.
The site is provided as it is. We keep it accurate and current, but we do not promise it will never be wrong or never be down.
13Changes to these terms
We may update this page. The date at the top says when it last changed. Changes apply to work agreed after that date, never retroactively to work already scoped and paid for.
14Law, and talking to a person first
These terms are governed by the law of the state in which Zhorx is established, and any dispute belongs to the courts there.
Before it gets that far: write to support@zhorx.com and tell us what went wrong. Almost everything is fixable that way and we would rather fix it than argue about it.

