The short version
- This website runs no analytics or advertising trackers. It collects only what you choose to give us, such as an early-access sign-up.
- Client files are stored in New Zealand, with an encrypted backup copy of the database kept in Australia.
- We are not the owner of your clients' information — your practice is. We handle it on your instruction and for no purpose of our own.
- Nothing you put in Clerq is used to train AI models or for product analytics.
That summary is accurate but not complete. The detail is below.
Two different things, and the difference matters
This statement covers two situations that people often blur together, and the answers are different in each.
- Visiting clerq.nz. You are reading a web page. Covered in the next section.
- Information inside Clerq. A licensed immigration practice uses Clerq to run its files. The personal information in those files belongs to the relationship between that practice and its clients. Clerq acts as the practice's agent — we hold and process that information on the practice's instruction and may not use it for our own purposes. If you are an applicant whose adviser uses Clerq, your privacy relationship is with that practice, and its privacy statement governs.
This website
There is no analytics tag, no advertising pixel, no embedded video, no chat widget, and no social button.
Hosting. Cloudflare hosts this site. Our website host records standard technical request logs (an IP address, a timestamp, the page requested) in the ordinary course of serving the site. We do not combine those logs with anything else, and we do not use them to build a profile of you. If we ever add analytics, this page will say so before we do.
The typeface. The site is set in Massilia, which Adobe Fonts (Adobe Inc., United States) serves to your browser. To do that, your browser connects to Adobe when a page loads, so Adobe receives your IP address and the address of the page, and counts page views for its font licensing. Adobe describes how it handles that information in its Adobe Fonts privacy notice.
Early-access sign-ups. If you sign up for early access, we collect the email address you give us and, if you choose to answer them, how many advisers your practice has, which system it uses today and what you would like from practice software. We also record the page you signed up from and the time. We use this only to contact you about early access to Clerq. The form is handled by Cloudflare, which passes each sign-up to our team inbox by email. We keep a sign-up only for as long as we need it to contact you about early access, and we delete it sooner if you ask at privacy@clerq.nz.
If you email us, we hold your message and your address so we can reply to you and keep a record of the conversation. Mail sent to an @clerq.nz address passes through Cloudflare, which forwards it to our team inbox.
The practice onboarding form
A practice that is joining Clerq may complete the onboarding form at clerq.nz/practice-onboarding. We use the information given in the form to set up the practice’s account.
Information the form collects
- The name, job title, work email and, optionally, phone number of the person completing the form.
- The practice’s details: its names, business numbers, addresses, opening hours, fees and the way it operates.
- For each colleague who will sign in to Clerq: that person’s name, work email, job title and intended role and, for a licensed immigration adviser, the adviser’s IAA licence number, licence type and supervisor. We check each licence against the public IAA register before we record it.
The form does not request passwords, logins, bank account numbers or any client’s personal details, and asks that none of these be entered. The person completing the form confirms that they are authorised to provide these details and that their colleagues are aware that their names and work emails are being provided to us.
Before the form is submitted
Your answers are stored in your own browser (in its local storage, not in a cookie) so that you can return to the form and complete it later. Nothing is transmitted to us until the form is submitted. A draft is cleared when the form is submitted or when you select “Start again”. Where a draft has not been changed for 30 days, the form does not load it again and removes it the next time the form is opened. If you are using a shared computer, select “Start again” when you have finished.
“Save and finish later” can also provide a private link with which the form can be completed on another device. That link contains the answers you have given up to that point, including your colleagues’ names and emails, in readable form. The link is not transmitted to us, but any person to whom you give it can read its contents. The form ceases to accept a link 7 days after the link was created. The link should be shared only with yourself or a colleague.
When the form is submitted
Your answers pass through our website host (named on the sub-processor page) in transit to our own account in Clerq. They are held there in the same way as the rest of Clerq’s data, as described below. An email alert containing the first part of a summary of the answers is sent to our own mailbox; the answers to the questions that ask for your colleagues’ names or emails are omitted from that summary. We use your answers only to set up your practice in Clerq and to communicate with you about that set-up. We retain them as part of our records of setting up your practice. You may ask us to correct them, or to delete those we no longer need, by writing to privacy@clerq.nz.
When the form is submitted, our website host also passes to Clerq the internet (IP) address from which the form was submitted. Clerq uses the network portion of that address only to limit the number of submissions accepted from one network within an hour, and keeps a count against it for that purpose. The address is not recorded with your answers.
When your practice uses Clerq
What is held
Whatever the practice puts in: client contact details, matter and case records, deadlines, documents and their extracted text, correspondence and messages, appointments, file notes, engagement agreements, and the practice's own staff and licensing records. Immigration files routinely contain identity documents, health information, relationship evidence and financial records, and the system is built on that assumption rather than hardened for it afterwards.
Where it is held
On servers in New Zealand, in Amazon Web Services' Auckland region, with an encrypted backup copy of the database kept in Sydney, Australia for emergencies only. Each practice's data is isolated from every other practice's, and that isolation is enforced by the database on every query rather than by application code remembering to filter.
Some services are not offered in New Zealand yet. Three things affect every practice, so rather than leave them to the fine print: email is sent and received through Sydney, because Amazon does not run its email service in Auckland; an encrypted backup copy of the database is kept in Sydney, for emergencies only, because there is no second New Zealand region; and AI drafting sends tokenised text to a provider in the United States — with identifying details removed first, and only when someone uses an AI feature. All three are named, with everyone else, on our sub-processor page.
Inbox forwarding. If your practice forwards a shared mailbox (for example info@yourfirm.co.nz) to Clerq, each forwarded email is received by our email provider, Amazon Web Services, in Sydney, Australia, scanned there for spam and viruses, and held there in encrypted storage only until Clerq has moved it to our servers in Auckland, New Zealand — normally within minutes. It is then deleted from Australia; anything not moved (for example during an outage) is deleted from Australia automatically within about two days. After that, the email and its attachments are stored in Auckland, and the email itself, which is held in the database, is also in the encrypted backup copy of the database kept in Sydney. Practices that do not use inbox forwarding are not affected by this.
Facebook Messenger and Instagram
A practice can connect its Facebook Page and the Instagram professional account linked to it, so messages sent to them arrive in its Clerq inbox. When it does, Clerq receives from Facebook: the Page's name and identifier, the linked Instagram account's identifier and username, and an access token that lets Clerq receive the Page's messages and send the practice's replies. The token is stored encrypted and is never shown to anyone.
From then on Clerq receives each message sent to the Page or Instagram account, with any attachments and the identifier Facebook or Instagram gives the sender, and sends the replies the practice's staff write. That information is stored in Auckland like the rest of the practice's data, used only so the practice can answer the people who wrote to it, and never sold, used for advertising, or used to train AI models. Disconnecting the Page in Clerq stops all of this at once. To have what was received deleted, see deleting your data.
A practice can connect its WhatsApp Business number through Meta's own signup window, so messages sent to it arrive in its Clerq inbox. The number can stay on the WhatsApp Business app on the practice's phone. When it connects, Clerq receives from Meta: the identifier of the practice's WhatsApp Business account, the phone number's identifier, its display number and verified business name, and an access token that lets Clerq receive the number's messages and send the practice's replies. If the number is not on the WhatsApp Business app, Clerq also sets the number's two-step verification PIN. The token and the PIN are stored encrypted and are never shown to anyone.
From then on Clerq receives each message sent to the number, with any photo or document attached and the sender's WhatsApp phone number, and sends the replies the practice's staff write. A message from someone who is not yet a client of the practice is recorded as a new enquiry so the practice can follow it up. A practice can also write message templates, its own wording for reminders and follow-ups, which Clerq submits to Meta for approval. All of this is stored in Auckland like the rest of the practice's data, used only so the practice can answer the people who wrote to it, and never sold, used for advertising, or used to train AI models. If the practice turns on automatic replies, message text is tokenised before it reaches our AI provider, as described below.
When a number stays on the WhatsApp Business app, Clerq asks Meta, at the moment of connection, to share the phone's contact list and recent chat history; Meta allows this only once. Clerq does not keep either today: both are discarded as they arrive, and this page will say so before that changes. Disconnecting the number in Clerq stops all of this at once. A practice's WhatsApp conversations are its own, so a request to delete them goes to the practice, or to privacy@clerq.nz, and we act on the practice's instruction. How to disconnect a number and have what was received deleted is set out in deleting your data.
Google: Calendar, Drive, Gmail and signing in
Every Google connection is optional. A person at the practice makes it for their own Google account, on Google's own consent screen, and Clerq asks Google only for what that feature needs.
- Google Calendar. Clerq reads only the times you are busy over the next 90 days, so your booking page does not offer them. It does not read the titles, attendees or details of your events. It adds appointments booked through Clerq to calendars you own, with a Google Meet link for video consultations, and changes or removes them when the booking changes. It also reads the email address of the Google account you connected, so Clerq can show which account it is.
- Google Drive. Clerq can open only the files and folders you pick in Google’s file picker, and copies them into Clerq. That includes a Google Meet recording you pick, which Clerq transcribes and files on the case. It cannot see anything else in your Drive, and it does not change or delete anything there.
- Gmail. When a mailbox is connected, Clerq reads its mail to show it in Clerq Mail and file it to your clients’ records. It sends mail from that mailbox only once sending is turned on for it. It does not delete or change anything in the mailbox.
- Signing in with Google. Clerq receives your Google account’s identifier and email address, and uses them only to sign you in to your existing Clerq account.
What Clerq copies (busy times, the bookings it made, files you picked, mail) is stored in Auckland like the rest of the practice's data. The sign-in Google gives Clerq is stored encrypted and is never shown to anyone. Your Google account itself stays with Google, under Google's terms. Clerq does not sell Google data, does not use it for advertising, and does not use it to train AI models. Nobody at Clerq reads it unless your practice asks us to for support, it is needed for security, or the law requires it. If someone at your practice uses an AI feature on it, the AI provider receives only what is described below under "What the AI provider actually sees".
You can disconnect any of these in Clerq at any time: your calendar in Settings, Calendar & booking; a mailbox in Mail settings; Drive in Files, Import. Disconnecting stops Clerq reading from or writing to it, and a disconnected calendar's busy times are deleted. Anything already copied into Clerq stays on the practice's records and is kept and deleted like the rest of them. You can also remove Clerq's access from your Google Account at any time, at myaccount.google.com/permissions.
Clerq's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Who else is involved
We use a small number of service providers. The categories are below; every one is named individually, with what it does and where it is, on our sub-processor page — that page is the authoritative list, and it is the one we keep current.
- Cloud infrastructure — Amazon Web Services, in New Zealand, for storage, databases and compute, with an encrypted backup copy of the database (not of document files) kept in Sydney for emergencies only; and its email service, in Sydney, for sending and receiving mail.
- An AI provider, outside New Zealand, for drafting assistance — under commercial terms that prohibit training on customer content and require deletion after termination. See the next section for what it actually receives.
- Services a practice chooses to connect, such as its own email provider, calendar, document store or messaging accounts. None of these are engaged unless someone at the practice connects them.
When a payment is made through Clerq — a practice paying for its subscription, or an applicant paying a practice's invoice through the client portal — the payment processor engaged is Windcave. Card details are entered on Windcave's own hosted payment page and never reach us: Clerq never sees or stores the card number. Windcave receives the amount and the invoice number, not the file. Windcave is listed, with its location, on the sub-processor page.
We do not sell personal information. We do not disclose it for marketing. We do not share one practice's information with another.
What the AI provider actually sees
Before any text is sent for drafting assistance, identifying details are replaced with placeholder tokens inside our own infrastructure, and the real values are restored on the way back. If that step is unavailable, the request fails rather than proceeding unprotected.
We are deliberate about what this does and does not achieve. Tokenising names and dates reduces risk; it does not, on its own, make a detailed file note anonymous, because identity in free text is often carried by a combination of attributes rather than by a name. We have tested this against realistic material, and the document types that do not survive the test are not sent at all.
Content sent for drafting assistance is not used to train any model. That is a contractual term with our provider, not an assurance we are asking you to take on trust.
Clerq keeps its own record of some AI requests and the replies to them, in the tokenised form in which they were sent, so that a change of AI model or provider can be tested before it reaches your practice. That record is held with the rest of your practice’s data and is not shared with any other practice.
How long it is kept
Retention of client files is the practice's decision, not ours — a practice has its own professional obligations, and we hold the files under its instruction. Clerq provides the tools to state and apply a retention period, and our suggested wording is ten years from the closure of a file.
When a practice leaves Clerq, it can export its data for 30 days. We then delete the practice's data, not just its login, within a further 30 days, and copies in our backups expire when the backup cycle runs out.
Backups are kept for up to 12 months and then destroyed: daily backups for 35 days and monthly backups for 12 months, in Auckland and in the encrypted backup copy in Sydney alike. So information deleted from Clerq can remain in a backup for up to 12 months before it is destroyed.
Security
- Data encrypted in transit and at rest.
- Tenant isolation enforced at the database layer, so a defect in one feature cannot expose another practice's file.
- Personal information held separately from operational records, with the operational side referring to people by opaque identifiers rather than by name.
- A tamper-evident audit log, hash-chained so that a record altered or removed after the fact is detectable.
- Access limited to the smallest set of people who need it, for the shortest time.
No system is beyond compromise. If a notifiable privacy breach occurs, we will notify the affected practice promptly so it can meet its own obligations under sections 114 and 115 of the Privacy Act 2020, and we will notify the Office of the Privacy Commissioner where we are required to.
Requests from government agencies and public authorities
Sometimes a government agency, regulator, court or other public authority asks a company like Clerq for information it holds about people. This is how Clerq Trading Limited handles those requests for information it holds for the practices that use Clerq, including messages clients send to a practice through a messaging account it has connected. Requests about information we hold for ourselves, such as account and billing records, go through the same checks.
- We point them to the practice first. A practice's information belongs to the practice, not to us. Where the law allows, we ask the authority to make its request to the practice directly. Unless the law or a court order forbids it, we tell the practice before we disclose anything and give it a chance to respond, or, if a warrant is being executed, as soon as we can.
- We check every request is lawful. A request must be in writing, say who is making it, and name the legal power that requires us to comply, such as a production order or search warrant issued under the Search and Surveillance Act 2012, or a notice under another New Zealand statute. A director of Clerq Trading Limited reviews each one, with legal advice where it is needed, before we disclose anything, or as soon as possible if a warrant is being executed. We do not answer informal requests, and we do not hand information over voluntarily. If we learn of a serious threat to someone's life or health, we tell the practice straight away so it can decide whether to disclose under the Privacy Act 2020.
- We challenge requests that are unlawful or go too far. If a request has no proper legal basis, asks for more than the law allows, or comes from an authority outside New Zealand without going through New Zealand's legal process, we refuse it, ask for it to be narrowed, or challenge it, as the case requires.
- We give the minimum. When we must comply, we disclose only the information the request lawfully requires, and nothing else from the practice's file.
- We keep a record of every request. For each one we record the date, the authority, the legal power it relied on, what it asked for, what we decided and why, who decided, and exactly what we disclosed. We keep that record for at least seven years.
Clerq Trading Limited is a New Zealand company and client files are stored in New Zealand, so a request made to us is decided under New Zealand law. Some of the companies on our sub-processor page, including Amazon Web Services, which hosts those files, are based overseas and may receive requests under their own countries' laws; their own published policies say how they respond. Text sent to our AI provider has client names and identifying details replaced with tokens before it leaves.
Questions about how we handle these requests go to privacy@clerq.nz.
Your rights
Under the Privacy Act 2020 you have the right to ask for access to personal information about you, and to ask for it to be corrected.
If you are an applicant or a client of a practice that uses Clerq, please direct that request to your adviser. They hold the information; we hold it for them, and it would not be right for us to release or change it without their instruction. We will support them in responding to you.
If you contacted us directly, for example by emailing us about the product or by submitting the practice onboarding form, write to privacy@clerq.nz and we will deal with it.
Complaints
If you think we have mishandled personal information, tell us first at privacy@clerq.nz. If you are not satisfied with how we respond, you may complain to the Office of the Privacy Commissioner at privacy.org.nz.
Changes
If we change this statement we will change the date at the top. Where a change materially affects how we handle information for practices using Clerq, we will tell those practices directly rather than relying on them to notice.
Contact
Clerq is a product of Clerq Trading Limited (company number 9459202), New Zealand.
Privacy enquiries: privacy@clerq.nz
Anything else: hello@clerq.nz