What this website is
The site is static files served from Cloudflare's network. There is no database behind it, no account to create and no login. The one form on it, the enquiry form, is covered in full in section 05. Nothing else you do here is stored, and nothing about you personally is collected. The one thing that leaves your browser is the anonymous page count set out in section 03.
Fonts are self-hosted rather than loaded from Google. Images, styles and Leapfrog's own scripts all come from this domain. Those scripts are small pieces of interface work (opening the menu, revealing sections as you scroll, drawing the diagrams) and none of them send anything anywhere.
Two scripts on the page were not written by Leapfrog. Both are named in the register above rather than left for you to find, because this page invites you to open the network tab and check, and an unlisted script sitting in it would be a fair reason to doubt everything else here. The first is the page counter, which section 03 covers in full.
The second is Cloudflare's email obfuscation, which is switched on for this domain. It rewrites every email address in the markup into an encoded form and serves a small script from this same domain to decode it again in your browser, so an address harvester scraping the page source gets nothing usable while a person reading the page still sees a working mail link. It reads the page, restores the address, and does nothing else: no network requests, no cookies, no identifiers.
The track record pages carry ordinary links to client websites. Following one takes you to somebody else's site, under their privacy policy rather than this one.
Cookies
This website sets no cookies. There is no consent banner, because there is nothing to consent to, and a banner asking permission to do nothing is theatre.
Cloudflare, which serves the site, may set a small number of strictly necessary cookies at the network layer, typically __cf_bm and cf_clearance, to distinguish human traffic from automated traffic and to keep the site available. They carry no advertising identifier, they are not used to build a profile of you, and they cannot be switched off without switching off the protection they provide.
The page counter described in the next section is the usual reason a site like this would need a cookie banner. It does not use cookies, which is why there is nothing here to ask you about.
Australia has no cookie consent law, so none of this is a legal position being taken. It is simply what the site does. If it ever changes, this page changes before the change ships, not after.
The page counter
Leapfrog uses Cloudflare Web Analytics to count page views. Being exact about that matters, because the word "analytics" stretches from a page counter at one end to a surveillance product at the other, and the two get described in identical language.
It sets no cookies and writes nothing to your browser. It does not fingerprint your device, does not build a profile, and has no way to recognise you when you come back or to follow you anywhere else. What it records is the request that already happened: which page was loaded, the referring site if there was one, and coarse technical facts such as browser, operating system and country. Those go into totals.
It is the one genuinely third-party request this site makes: the script is served from static.cloudflareinsights.com rather than from this domain. That is why it appears in the register above as something Leapfrog did not write.
What it produces, at the other end, is a list of which pages get read and roughly where readers arrive from. That is the whole of it, and it exists so the writing here can be improved from evidence rather than from guesswork.
If you would rather not be counted, any standard tracker blocker stops the script, and every page on this site works exactly the same without it.
When you get in touch
You can use the enquiry form, send an email, or make a call. The form is covered in the next section; by email or phone, what Leapfrog holds is whatever you chose to put in it: your name, your email address, your company, your phone number, and whatever you wanted to talk about.
That is used to reply to you, to scope and quote work, and to do the work. It is not added to a mailing list, because there is no mailing list. It is not used for marketing, and it is never passed to anyone else for theirs. Enquiries that do not turn into work are kept while there is a reasonable prospect of the conversation resuming, and then deleted.
Separately, Cloudflare records the usual network information for every request to this site: IP address, timestamp, the page requested, your browser's user agent. That is how a content network tells a reader from an attack. It sits in Cloudflare's logs for a short retention period, and Leapfrog does not extract, keep or analyse it.
The enquiry form
The form asks for a name, an email address, a company, a phone number and a description of the problem. Only the name, the email address and the description are required. Nothing is asked for that a reply does not need, and there is no field whose purpose is to profile you rather than to answer you.
What happens to a submission is short enough to state completely. It is emailed to the Leapfrog mailbox, and a fixed acknowledgement is emailed back so you know it arrived. Both go through Microsoft 365, which is named below as where Leapfrog's mail already lives. No form service, no marketing platform and no third party receives it, and it is not written to any database. The mailbox is the only copy that exists.
It is then kept on the same terms as any other enquiry: used to reply, to scope and to quote, never added to a list, and deleted once there is no longer a reasonable prospect of the conversation resuming.
The form is protected by Cloudflare Turnstile, which checks that a submission comes from a browser rather than a script. It loads from challenges.cloudflare.com, which makes it the third script on this site Leapfrog did not write. It is a bot check rather than an advertising product: it does not profile you, does not follow you between sites, and in the configuration used here it sets no cookie. Cloudflare offers a mode that issues one; it is switched off, deliberately, so that the first line of the register above stays true.
Without JavaScript the form cannot run at all. The email address and phone number sit underneath it for exactly that reason, and they are not going anywhere.
Before the first consultation
A discovery conversation involves a business explaining how it actually works: where the money goes, which process is held together by one person's spreadsheet, who keeps leaving. That is usually more revealing than anything that ends up in a contract.
So the confidentiality commitment starts before the conversation does, rather than after it. A mutual non-disclosure agreement is issued for e-signing before any consultation takes place. It covers what is discussed, the material shared to explain it, and the fact of the conversation itself. It applies whether or not the conversation leads to any work, and it does not lapse when the conversation ends. It is the first item on the security page for the same reason.
That is a contractual commitment rather than a statutory one, and it is worth being precise about the difference: an agreement binds Leapfrog directly to the business it is talking to, which is narrower, more specific and more immediately enforceable than what the Privacy Act asks of a business this size. It sits on top of everything else on this page rather than in place of it.
Your data during an engagement
This is the section that matters, and the answer is structural rather than a promise.
Every account created for a Leapfrog engagement is registered in the client's name, billed to the client, with the client as the top administrator: the domain, the email tenancy, the hosting, the database, the code repository, the password vault. Leapfrog works inside those systems under its own named account, holding delegated access that the client can revoke in a single action.
The consequence for your privacy is direct. Leapfrog is not the custodian of client data. The client is. There is no Leapfrog-controlled copy of a client database, no Leapfrog vault holding client passwords, no per-client folder inside a Leapfrog account. Break-glass credentials sit on paper, in the client's own office, somewhere Leapfrog cannot reach.
Building a system does mean seeing the personal information inside it: staff records, customer records, whatever the platform handles. That access is:
- Named, never shared. The audit trail shows who did what and when, because the account belongs to one person rather than to a team.
- Limited to what the work requires, and to the period the work requires it for.
- Revocable at any moment, by the client, without rotating a password that other people also knew.
- Not copied out. Where a working copy is genuinely needed to reproduce a fault, it is taken with the client's knowledge, kept on an encrypted machine, and deleted once the fault is fixed.
Leapfrog does not subcontract, so there is no third party and no offshore team with access to a client's systems. Where an engagement carries obligations of its own, such as a client bound by the Privacy Act or by health or financial sector rules, those are handled in the engagement contract, where they can be specific, rather than in a paragraph here.
The architecture behind all of this, including what happens on the day a client wants Leapfrog gone, is set out on the ownership page.
Where information is actually held
Naming the systems is more useful than the usual sentence about trusted third parties.
- Microsoft 365: Leapfrog's email, calendar and documents. Enquiries and client correspondence live here.
- Cloudflare: serves this website, runs its DNS, and provides both the page counter in section 03 and the form's bot check in section 05. Processes IP addresses in network and security logs, as described above.
- Leapfrog's own CRM and client portal: prospect and client contact records, proposals, signed documents and portal requests. It was built in-house and runs on a server Leapfrog administers in an Australian data centre, reached only through Cloudflare, with nightly encrypted backups. Client logins to the portal at
crm.leapfrogautomation.com.auare invited by Leapfrog, never self-registered, and what a client can see there is set out in the engagement contract. - Xero: accounting. Holds client billing contacts and invoice records, kept for the seven years Australian tax law requires. It has no connection to this website and receives nothing from it.
- Google Search Console and Bing Webmaster Tools: verified for this domain. They report which search terms surfaced the site and which pages appeared in results. They report totals rather than people, and they do not identify visitors.
Microsoft, Cloudflare and Xero are global providers, so some of that information is processed on servers outside Australia, under their own privacy commitments. Leapfrog's CRM never leaves the country, or the machine.
Who else sees it
Nothing is sold. Nothing is shared with advertisers, data brokers or marketing platforms. The arrangement that would need explaining here does not exist.
Information is disclosed in three circumstances only: where a client asks Leapfrog to pass something to another supplier working on their system; where the law requires it; and to the providers named above, who process it in order to run their services rather than for purposes of their own.
Getting a copy, a correction, or a deletion
Email hello@leapfrogautomation.com.au and ask. You can ask what Leapfrog holds about you, ask for it to be corrected if it is wrong, and ask for it to be deleted. Expect an acknowledgement within a few business days, and the thing itself done within thirty.
Two limits, stated plainly rather than buried. Records Leapfrog is legally required to keep, invoices mostly, cannot be deleted on request until that period expires. And information held inside a client's own systems belongs to that client, so a request about it has to go to them; Leapfrog will tell you who to ask.
If something goes wrong
If personal information Leapfrog holds is lost or exposed in a way likely to cause serious harm, the people affected and the Office of the Australian Information Commissioner are told promptly and directly, rather than through an update to a status page.
If you are unhappy with how Leapfrog has handled your information, say so to hello@leapfrogautomation.com.au. This is a one-person business, so it will be read by the person who can fix it. If that does not resolve it, you can take the complaint to the OAIC at oaic.gov.au.
Where the law sits
Leapfrog Automation is a small business. Under the Privacy Act 1988 (Cth), small businesses below the three million dollar turnover threshold are generally not bound by the Australian Privacy Principles, and are generally not required to publish a privacy policy at all.
Leapfrog follows them anyway. Partly because that exemption has been under review for years and looks unlikely to survive it. Mostly because a business asking clients to trust it with the systems that run their company should not be leaning on a technicality about its own size.
Where a particular engagement brings Leapfrog within the Act, through contracted services to a Commonwealth agency or work touching health information, the Act applies in full, and the engagement contract says so.
Changes to this policy
This page lives in the same repository as the rest of the site, so every change to it is dated and recorded rather than silent. If something material changes, such as a new system holding personal information or analytics being added to the site, this page is updated before that change goes live.