The documents, and what each one answers.
Three documents. They are written to be read rather than to be survived, and each one is introduced below by the question it actually answers.
Terms of engagement
What am I agreeing to, and who owns what we build?
How a build and a run engagement work, what the fees are, what we promise and what we do not, and how either of us ends it. Section 6 is the one most people are looking for: when the build fee is paid, the software is yours, and you can take it and go.
Read itPrivacy Policy
What do you collect about me, and where does it go?
What we collect from this website and from an enquiry, the three tracking services running on this site named individually, what leaves Australia and why, how long we keep things, and how to get a copy or have it deleted.
Read itHow we handle data and contact
What does the software do about the rules, and what is still my job?
The Australian instruments that govern automated calling and messaging, which obligations the software enforces on its own, and which ones stay with the business. It is also where we say plainly that we hold no certification.
Read it
Two things worth saying here
We hold no certification and claim none. Not ISO, not SOC 2, not anything. Listing the laws that apply to this kind of software is not the same as having been audited against them, and any vendor who blurs those two things should be asked to produce the certificate.
The software we build for you is yours. That is in the terms, not just in the sales copy, and it is the reason the run service is a separate monthly commitment you can end with 30 days notice rather than something you are locked into to keep what you paid for.
If something in any of these documents is unclear or looks wrong, tell us and we will fix the document. Get in touch.