The short version
- Two are engaged for every practice. Amazon Web Services, in Auckland, holds your files; they stay in Auckland. Only the database has an encrypted backup copy in Sydney, for emergencies. Amazon’s email service, in Sydney, carries your mail.
- Everything else is a choice you make. Nothing below the first table is engaged unless you use a feature, connect an account, or visit this website.
- This website uses two of its own. Cloudflare hosts clerq.nz and handles its early-access form, and Adobe serves its typeface. When the practice onboarding form is submitted, the answers also pass through Cloudflare in transit to Clerq.
- None of them train models on your data, and that is a term of our agreement with them, not a hope.
That summary is accurate but not complete. The detail is below.
What this page is
A sub-processor is any company we use that could, in the course of doing its job, hold or handle information belonging to your practice and your clients. Under the Privacy Act 2020 your practice remains the agency responsible for that information; we act on your instruction, and so does everyone on this page.
We publish the list because the alternative is asking you to take our word for it. If you are assessing Clerq for a practice, this is the page to send to whoever asks you where the data goes.
Engaged for every practice
These two are not optional. Using Clerq at all means using them.
| Sub-processor | What it does | Where |
|---|---|---|
| Amazon Web Services Amazon Web Services, Inc. | Runs the Clerq service and stores your client records, matters, documents and mail — compute, database, file storage, secrets and queues. An encrypted backup copy of the database is kept in Sydney for emergencies only; document files are not in that copy. | Auckland, New Zealand ap-southeast-6 Encrypted backup copy: Sydney, Australia ap-southeast-2 |
| Amazon Simple Email Service Amazon Web Services, Inc. | Sends and receives your practice email. Message content is stored in Auckland once received, and is also in the encrypted backup copy of the database kept in Sydney for emergencies; the transport happens in Sydney. If a practice uses inbox forwarding, each forwarded email is also held encrypted in Sydney until it is moved to Auckland, normally within minutes and never more than about two days. | Sydney, Australia ap-southeast-2 |
Why Sydney. AWS does not offer an email service in its Auckland region. No New Zealand provider can do this differently today — anyone claiming fully onshore email is either using a different definition of onshore or has not checked.
Engaged when you use an AI feature
| Sub-processor | What it does | Where |
|---|---|---|
| Anthropic Anthropic, PBC | Generates the drafts and analysis you ask for, and answers the questions you put to Clerq’s assistant — including when you ask it to read your inbox, a folder or a document to answer. In every case, client names and identifying details are replaced with tokens before anything is sent, and restored only after the response comes back. Our terms with Anthropic prohibit training on what we send. Any copy it keeps is kept only briefly, for safety checks, then deleted. | United States |
The replacement step is not a setting anyone can switch off in the course of using Clerq — it runs inside our own network, on our own servers, before any request leaves. If it cannot run, the request does not go. This is as true of the assistant as of a drafted letter: it can read your mail and files to answer you, but what leaves for the model is the tokenised version, never the names.
Engaged when a payment is made through Clerq
| Sub-processor | What it does | Where |
|---|---|---|
| Windcave Windcave Limited | Our payment processor. It is engaged when your practice pays for Clerq and, if your practice has its own Windcave merchant account set up with Clerq, when an applicant pays one of your practice’s invoices through the client portal — that money goes to your practice’s own account, never to Clerq’s. In both cases card details are entered on Windcave’s own hosted payment page — Clerq never sees or stores the card number. Windcave receives the amount, the currency and the invoice number so the payment can be matched back; it never receives your clients’ files or any matter data. | New Zealand |
Engaged only if your practice has the feature
Neither of these is engaged unless your practice has hosted email or the phone service set up with Clerq.
| Sub-processor | What it does | Where |
|---|---|---|
| SiteHost | Hosts your practice’s mailboxes, if your practice has hosted email with Clerq. SiteHost holds the mailboxes, their backups and their spam filtering. Clerq reads the mail from there into your practice file; mail you send from Clerq leaves through the email service in the first table. | Auckland, New Zealand |
| Amazon Connect Amazon Web Services, Inc. | Runs the phone service, if your practice has Clerq Connect. The calls your staff make and receive in Clerq, and the phone numbers on them, pass through it. AWS does not offer this service in its Auckland region. | Sydney, Australia ap-southeast-2 |
Engaged only if you connect the service
Each of these is off until someone at your practice connects an account, and can be disconnected at any time. Disconnecting stops any further exchange; it does not remove data the provider already holds, because that data is in their system under your relationship with them, not ours.
| Sub-processor | What it does | Where |
|---|---|---|
| Microsoft Microsoft Corporation | Staff sign-in with a Microsoft work account, and a connected Outlook calendar: Clerq reads when an adviser is free or busy, and adds the bookings made through Clerq to that calendar. Microsoft receives each booking’s time and a title that includes the client’s name; never the client’s file, passport details or matter contents. Also a connected Microsoft 365 mailbox: Clerq reads its messages into your practice file, and — only when your practice turns it on — sends your outgoing mail through it, which means the message you send passes through Microsoft to leave from your own mailbox and lands in its Sent folder. | The region your own Microsoft tenant is in |
| Zoho Zoho Corporation Pvt. Ltd. | Reads a connected Zoho mailbox so its messages appear in your practice file, and imports documents from a connected Zoho WorkDrive into your practice’s files. Clerq only reads from WorkDrive; it never writes to it. | The region your own Zoho account is in — we connect to the data centre your account already uses |
| HubSpot HubSpot, Inc. | Only if your practice is moving its records from HubSpot: Clerq reads your own HubSpot account, with a read-only key your practice creates, to bring your clients, cases, leads and their history into Clerq. Nothing is written back to HubSpot. | The region your own HubSpot account is in |
| Google Google LLC | Staff sign-in with a Google account, calendar availability, importing documents from Google Drive, reading a connected Gmail or Google Workspace mailbox so its messages appear in your practice file (and, only if your practice turns it on, sending replies through it), and — if an adviser starts a meeting on Google Meet from Clerq — hosting that consultation. The Meet call runs in your practice’s own Google account and its recording, if you make one, stays in that account’s Drive; Clerq never receives it. What Clerq sends Google is the meeting’s title and time, to create the calendar entry that carries the link. | United States |
| Meta Meta Platforms, Inc. | Sending and receiving client messages over WhatsApp, Messenger and Instagram, including any media attached to them. | United States |
| LinkedIn LinkedIn Corporation | Publishing posts your practice writes in Clerq’s marketing tools. Client file data is not involved. | United States |
| Xero Xero Limited | Raising your practice’s fee invoices in Xero, if you connect your Xero organisation and turn invoice push on, and then recording there the payments, credit notes and voids against those invoices, so the two systems agree. Xero receives each invoice’s lines and amounts, the client’s name as the Xero contact, and the case reference; never the client’s file, passport details, matter contents, client money (trust) records or bank data. | New Zealand (global cloud infrastructure) |
| Zoom Zoom Communications, Inc. | Holding the cloud recording of a consultation your practice runs on its own Zoom account, if you connect Zoom and your client consents to being recorded. This is the heaviest entry on this page and we would rather say so plainly: what Zoom holds is the consultation itself, not a fragment of it. The account is your practice’s own and the recording is made there whether Clerq is connected or not; what connecting adds is that Clerq downloads the audio, transcribes it on our own servers in Auckland and drafts a file note from it. Zoom never receives your clients’ files, passport details or matter contents from Clerq — nothing flows the other way. | United States |
| DigiCert DigiCert, Inc. | Dating the seal on documents signed in Clerq, if your practice turns e-signature on. The document is signed and sealed on our own servers in Auckland; what DigiCert receives is only a cryptographic fingerprint of the seal, from which nothing about the document, the signer or your practice can be recovered, and it returns a signed timestamp. Clerq also checks DigiCert’s published revocation lists for that timestamp’s certificate. No document, name or email address is ever sent. | United States (global network) |
| Twilio Twilio Inc. | Sending booking confirmation and reminder text messages, if your practice turns SMS reminders on. Twilio receives the phone number the client typed on your booking page and a short message naming the appointment time — never the client’s file, email or matter contents, and nothing flows back. | United States |
| TNZ TNZ Group Limited | Sending client text messages — appointment reminders and updates — through a New Zealand carrier, if your practice turns messaging on. TNZ receives the client’s phone number and the short message body your practice sends; never the client’s file, email or matter contents, and nothing flows back. | New Zealand |
| Browser notification relays Google LLC, Mozilla Corporation, Apple Inc., Microsoft Corporation | Delivering optional desktop notifications, such as new mail, a new booking or a deadline coming due, to staff browsers that turned them on. The relay belongs to whichever browser the staff member uses and carries only an encrypted, generic alert and a link back into Clerq; never message content, sender names or client names. | United States (global relay networks) |
This website
Cloudflare and Adobe are involved when someone visits the site.
Cloudflare hosts every page of clerq.nz and is accordingly involved whenever a page of this website is read. Cloudflare also carries the answers given in the practice onboarding form, which a practice completes before we set it up in Clerq, in transit to Clerq.
| Provider | What it does | Where |
|---|---|---|
| Cloudflare Cloudflare, Inc. | Hosts clerq.nz. When a page is loaded, Cloudflare receives the visitor’s internet (IP) address and the details of the request: the page requested, the time, and the information the visitor’s browser gives about itself. Cloudflare keeps standard request logs of these. Receives early-access sign-ups (an email address and optional answers about the practice) and passes each one to our team inbox by email. When the practice onboarding form is submitted, the answers also pass through Cloudflare in transit to Clerq. Our code running on Cloudflare forwards the answers directly to Clerq and does not store them. Forwards mail sent to @clerq.nz addresses. | United States (global network) |
| Adobe Fonts Adobe Inc. | Serves the site’s typeface, Massilia. When a page loads, Adobe receives the visitor’s IP address and the page address, and counts the page view for font licensing. | United States (global network) |
What is not on this list, and why
- The anonymiser. The service that strips client details before anything reaches an AI model is ours, and it runs on our own servers inside the Auckland region. It is not a third party and there is nobody else to name.
- Immigration New Zealand. Clerq never submits anything to INZ by itself. When your practice files something, that is your practice dealing with INZ directly.
- The Clerq for Immigration Online browser extension. It runs in the adviser’s own browser, fetches the case from Clerq, and fills in the Immigration Online form open in front of the adviser, who checks it and submits it. It sends nothing to anyone other than Clerq and that form.
When this list changes
We will give you at least 30 days’ notice before adding a sub-processor that would handle your practice’s data, and you have 15 days from that notice to object. If you object and we cannot resolve it — by using someone else, changing the arrangement, or letting you turn the feature off — you may end your subscription and we will refund the unused portion.
To be told when this page changes, email privacy@clerq.nz with the subject Sub-processor notifications. It is a list of email addresses we write to; it is not run by anyone else, because putting a mailing-list provider in the way of this particular page would be an odd choice.
Asking us about any of this
Questions about a specific sub-processor, or a request for what we hold on our arrangements with them, go to privacy@clerq.nz. If you are an applicant rather than an adviser, your privacy relationship is with the practice acting for you — ask them first, and they can ask us.
See also our privacy statement and terms.