Client files at rest are held in Auckland, New Zealand, and are not replicated to any other region. They 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 exportable whenever you like.
Where your files live, and what the AI sees
Client files at rest are held in Auckland, New Zealand, and are not replicated anywhere else. 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 at rest
- Auckland, New Zealand, not replicated to any other region
- Model training
- Client files are never used to train any AI model. That is a contractual term.
- AI provider
- Zero data retention is enabled, so the provider does not keep what we send.
Your file is your file.
Stored in New Zealand, never used to train anything, exportable whenever you like. Leaving is a supported operation with dates attached to it, not a support ticket you hope somebody answers.
Terms of Service, cl. 9.3. Every sub-processor that can touch your data is published by name.
At rest
Auckland
And nowhere else
Client files at rest are held in Auckland, New Zealand, and are not replicated to any other region.
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 whole, then gone
Export the entire record whenever you ask, 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.
Privacy Act 2020
A client hands over a passport and a history. Where that goes should not be a question you cannot answer.
The four 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.
No cross-practice analytics, and every sub-processor that can touch your data is 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.
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 lands in the Auckland region. It is never written to a machine outside New Zealand on the way in.
Auckland
Encrypted at rest with AES-256 or better, held in Auckland, New Zealand, and not replicated to any other region.
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. 9.3
Export the whole record whenever you ask, in a format you can read without us. After you leave, your data is deleted on the timetable the contract sets.
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 at rest in Auckland, encrypted with your practice’s own key. Replicates them to another region, or 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
Exports the whole record, then deletes your data on the timetable the contract sets. Keeps a copy, or leaves your data sitting there after the login is closed.
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.