Client files are stored in Auckland, New Zealand. An encrypted backup copy of the practice database is kept in Sydney, Australia, for disaster recovery only; the files themselves are not in it. Files are encrypted at rest with AES-256 or better, and in transit with TLS 1.2 or better.
Trust · Privacy Act 2020
Your file is your file.
Client files are held in Auckland, never used to train anything, and yours to export.
Where your files live, and what the AI sees
Client files are stored in Auckland, New Zealand. An encrypted backup copy of the practice database is kept in Sydney, Australia. Before anything reaches an AI provider, identifying details are replaced with tokens inside Clerq’s own New Zealand infrastructure and restored on the way back. If that step is unavailable, the request is refused rather than sent unprotected.
- Client files
- Stored in Auckland, New Zealand
- Backup
- An encrypted copy of the practice database is kept in Sydney, Australia
- Model training
- Client files are never used to train any AI model. That is a contractual term.
- AI provider
- Our provider’s terms prohibit training on what we send. Any copy it keeps is kept only briefly, for safety checks, then deleted.
Your file is your file.
Stored in New Zealand, never used to train anything, and yours to export. Leaving is a supported operation with dates attached to it, not a support ticket you hope somebody answers.
Terms of Service, cl. 9.3. The sub-processors that handle your data are published by name.
At rest
Auckland
Where your files are kept
Client files are stored in Auckland, New Zealand. An encrypted backup copy of the practice database is kept in Sydney, Australia.
Training
Never
Used to train a model
No client file is used to train any model, as a contractual term rather than a setting you have to find and switch off.
On leaving
Yours
Exported, then deleted
Export any client file, whole, in a format you can read without us. After you go, your data is deleted on a timetable the contract sets rather than at our discretion, and encrypted backup copies expire within 12 months.
Privacy Act 2020
A client hands over a passport and a history. Where that goes should not be a question you cannot answer.
The six things worth asking about.
The answers a practice actually needs before it moves a client list into somebody else’s software, including the one that is not ideal.
Identifying details are replaced with tokens inside our own infrastructure and restored on the way back. If that step is unavailable, the request is refused rather than sent unprotected. Why that matters under the Privacy Act is in our note on using ChatGPT for client documents.
No practice can see another practice’s data, and the sub-processors that handle your data are published by name. What was read, by whom, and when is recorded in a trail that cannot be quietly edited.
Clerq never holds your Immigration New Zealand or RealMe credentials. A licensed adviser reviews the work and submits it, because that is the person the Authority licensed.
Sign in with your Google or Microsoft account, or with a password and a code from an authenticator app. Passkeys work too. Changing how you sign in asks for your password first, and you can see and remove the devices signed in to your account.
Your practice can connect its own tools with an API key, which only a Super admin or a Marketing user can issue or revoke. A key can add enquiries and have your automatic reply sent to them. It can read the names and email addresses of your enquiries and clients, and each case’s reference, stage and visa type, but it cannot open documents, notes or messages, or edit or delete a record. Keys do not expire and every key has the same reach, so give one only to a tool you trust and revoke it when you stop using that tool. We keep a fingerprint of each key rather than the key itself, which is why it is shown only once. A revoked key stops working on its next use, and the audit trail records which key added each enquiry.
Follow one record all the way through.
A file note is written on a Tuesday and read back two years later. This is every place it sits in between, and who can reach it at each one.
In transit
The note leaves the browser over TLS and is stored in Auckland.
Auckland
Encrypted at rest with AES-256 or better and held in Auckland, New Zealand. An encrypted backup copy of the practice database, which includes this note, is kept in Sydney, Australia.
Tokenised
Identifying details are replaced with tokens inside our own infrastructure before anything is sent to a model, and restored on the way back. If that step is unavailable the request is refused.
Terms of Service, cl. 18
Export the client file, whole, in a format you can read without us. After you leave, your data is deleted on the timetable the contract sets, and encrypted backup copies expire within 12 months.
What we do, and what we will not.
A privacy page is easy to write. These are the four commitments we would rather be held to in writing than asked about later.
Your client files
Holds them in Auckland, encrypted with AES-256. An encrypted backup copy of the practice database is kept in Sydney. Pools them with another practice’s.
Requests to a model
Replaces identities with tokens first, and restores them on the way back. Sends anything unprotected. If tokenisation is unavailable, the request is refused.
Filing with INZ
Prepares the work for a licensed adviser to review and submit. Holds your INZ or RealMe credentials, or files anything on your behalf.
The day you leave
Gives you 30 days to export, then deletes your data on the timetable the contract sets. Leaves your data sitting there after the login is closed. Encrypted backup copies expire within 12 months.
Smart about what the AI writes.
Two checks on what AI produces, before it reaches you.
Drafts are checked as they’re written
AI drafts are checked for promised visa outcomes and claims to be a licensed adviser, and anything flagged is held back.
Templates that can’t carry a client
A template made from a real letter is refused if any client detail survives the swap for placeholders.
More in Trust
Start with the file you are worried about.
We onboard one practice at a time, so the first conversation is a working one: your overdue dates, the documents you are still chasing, and what the system would have done about them.