What we collect, and what we do with it
Written to be read, not to be skipped. If anything here is unclear, ask and we will fix the wording.
What the form collects
The enquiry form on this site is the only place we ask you for anything. Every field it sends is listed here. There are no hidden ones.
Your name
So we know who we are ringing. Required.
Phone
Because we ring you back. This is the field we actually use. Required.
For anything that needs writing down, and so we can reach you if the phone number is wrong. Required.
Business name
Optional. It helps us look at what you already do before we ring.
What software you run
Optional. It decides which integration conversation we have first, and whether the honest answer is that we cannot connect to it.
What it should be able to do
Optional. Free text, in your words. Please do not put anything sensitive in here: it is a description of a phone line, not a place for customer records or account numbers.
Anything else
Optional. Free text again, same request.
Sent automatically
The page you sent the form from, the time you sent it, and the campaign tags in the web address if you arrived from an advert. That is how we know which page brought you here. No location, no device fingerprint.
Why we collect it, and who sees it
To contact you about your enquiry and to quote for a voice assistant. That is the whole purpose. Nothing you send is used for anything else.
Your details are not sold. They are not passed to anybody outside the business that operates this service, and they are not traded, rented or shared with a marketing list. You are not signed up to anything by sending the form.
They are stored on our own systems, in New Zealand. The only people who see them are the people here who answer enquiries.
How the form is protected from automated abuse
The form uses a security session, a hidden anti-spam field, server-side validation and a limit on repeated submissions. A failed check shows an error; it is not presented as a successful enquiry. The rate limit uses a hashed version of the connecting IP address, held separately from enquiry content.
Your browser posts to this site's own server, which passes the enquiry on behind the scenes. That means the destination is never exposed in the page, and the form cannot be posted to directly from somewhere else without the secret the server holds.
Google reCAPTCHA protects the enquiry form. It loads when you submit and processes technical browser and network information to assess automated abuse. The form carries a reCAPTCHA notice saying so. Google Privacy Policy and Terms of Service apply to that check.
How long we keep it
Specific rather than vague, because "as long as necessary" tells you nothing.
If you do not become a customer
The enquiry is deleted 24 months after we last heard from you. If you tell us at any point that you are not interested, we delete it then instead of waiting.
If you do become a customer
The enquiry becomes part of your account record and is kept while the account runs. Billing records are then kept for seven years after the account closes, because tax law requires that and we cannot delete them on request.
Server logs
The web server records the usual request lines, including the address your connection came from, and they are rotated off within 30 days. They are used for keeping the site up, nothing else.
Cookies and tracking
An essential session cookie protects the contact form. It is not an advertising cookie. Short-lived request counts help limit automated submissions. Campaign tags may be remembered for the browser session and included when you enquire. Google reCAPTCHA protects the enquiry form. It loads when you submit and processes technical browser and network information to assess automated abuse. The form carries a reCAPTCHA notice saying so. Google Privacy Policy and Terms of Service apply to that check.
The site’s images, fonts and design assets are served from this domain. Optional Google Analytics and any enabled reCAPTCHA security check are exceptions, explained on this page.
If that ever changes, this page changes with it before the change goes live.
Correcting or deleting what we hold
Email logins@d3v.nz and ask. You can ask to see what we hold about you, to have it corrected if it is wrong, or to have it deleted.
We will come back to you within 20 working days, which is what the Privacy Act 2020 allows. Usually it is the same week.
If you are not happy with how we handle it, you can complain to the Office of the Privacy Commissioner.
If you become a customer, calls are a separate matter
This page is about this website. Once a voice assistant is answering your phone, the information involved is your customers' rather than yours, so it is worth stating plainly.
Where the calls are handled
Calls to +64 numbers are answered and held in New Zealand data centres. Calls to +61 numbers are answered and held in Australia. The number decides, and it does not change without you.
What is kept from a call
A recording, a transcript and an outcome, along with the caller's number and whatever they gave the assistant. You can see all of it, export it and have it deleted. It is your customers' information and you are the one who holds it.
What is never captured
Card numbers. Payments are taken by a link sent to the caller by text and paid on the payment page, so nothing about the card is ever spoken, heard or stored. That is a build rule, not a setting.
Last updated 29 August 2026.
Optional Google Analytics
We use Google Analytics on this website to understand page visits and confirmed enquiry counts. It is on by default. These sites serve New Zealand and Australia, where analytics of this kind does not require your prior permission, so we do not interrupt you with a banner to ask. You can switch it off at any time. Local previews send no analytics at all.
“Analytics choices” in the footer turns analytics off, and your choice is remembered in this browser for up to 180 days. Turning it off does not affect the contact form or any planning tool, and it stops this integration sending anything further. Essential form-security cookies work separately.
While analytics is on, Google receives limited technical information about the visit. This implementation sends the page path and title, referring website origin and whether an enquiry was confirmed. It does not deliberately send form answers, names, email addresses, telephone numbers or URL query/fragment text. Advertising personalisation and Google signals are disabled.
Google Analytics uses cookies and processes technical information, which may involve systems outside New Zealand or Australia. See Google’s Privacy Policy. Switching analytics off stops future analytics from this integration; it does not erase information already processed.