How Admitto looks after your clients' information.
Where client data is stored, who processes it, and how every assessment is sealed so you can show later that it has not changed.
At a glance
Where data is stored
In Sydney, Australia (ap-southeast-2), with Supabase. Data is stored outside New Zealand; the disclosure below covers this.
Encryption
AES-256 encryption at rest through our database provider. HTTPS in transit, TLS 1.2 or later, and TLS 1.3 where your browser and our hosts support it.
The audit seal
Each assessment is sealed with a SHA-256 hash over the client profile, the INZ sections retrieved, the rule results, the model output and the policy in force at the time.
Privacy and the Code
Built around the Privacy Act 2020 (IPPs 1 to 13) and the IAA Code of Conduct 2014. Citations are ranked by authority, statute first, so an adverse finding never rests on a web summary alone.
Privacy Act 2020: the Information Privacy Principles
How Admitto handles each principle, in line with our Privacy Policy. This is a summary, not legal advice.
| IPP | Principle | How Admitto handles it |
|---|---|---|
| IPP 1 | Purpose of collection | We collect personal information only to operate the assessment platform, authenticate advisers, bill subscriptions, and meet legal obligations, as described in our Privacy Policy. We do not sell data or use it for unrelated advertising. |
| IPP 2 | Source of personal information | Account and billing data come from you (or Stripe for payment metadata). Client case data is entered by the licensed adviser on behalf of their client. Technical logs may be generated automatically when you use the service. |
| IPP 3 | Notification of collection | Our Privacy Policy and Terms describe what we collect and why. We do not operate a separate “collection notice” beyond those documents and in-product disclosure; advisers remain responsible for their own client-facing privacy notices. |
| IPP 4 | Manner of collection | Information is collected through the web application (forms, uploads) and standard HTTP requests. We do not use covert tracking or third-party advertising pixels for client case data. |
| IPP 5 | Storage and security of personal information | Data is stored with Supabase, encrypted at rest, and sent over HTTPS. Each adviser can reach only their own applications, enforced in the database. Passwords are handled by Supabase Auth and never stored in plain text by us. Admitto is not certified to SOC 2 or ISO 27001. |
| IPP 6 | Access by individuals to personal information | Advisers can see their own account and client records in Admitto. For a formal Privacy Act access request, email hello@admitto.co and we will respond within the time the Act allows. |
| IPP 7 | Correction of personal information | Advisers can update account and case data in the product where the UI allows. For corrections to information we hold outside self-service, contact hello@admitto.co. |
| IPP 8 | Accuracy of personal information | We rely on advisers to supply accurate client information. The product may surface inconsistencies (for example between profile fields and extracted document text); final accuracy remains the adviser’s professional responsibility. |
| IPP 9 | Retention of personal information | Retention periods are set out in our Privacy Policy (including post-closure and assessment record retention). We do not retain personal information indefinitely without a stated basis. |
| IPP 10 | Limits on use of personal information | We use personal information only to provide and improve the service, bill, communicate operationally, comply with law, and secure the platform: not for unrelated sale or profiling, as stated in the Privacy Policy. |
| IPP 11 | Limits on disclosure | We disclose personal information only to sub-processors necessary to run the service (listed on this page), when legally required, or as you direct. We do not sell personal information. |
| IPP 12 | Disclosure outside New Zealand | Primary hosting is outside New Zealand (Sydney, ap-southeast-2; see Data residency). Sub-processors in the United States and other jurisdictions process data under our agreements and, where applicable, standard contractual terms. |
| IPP 13 | Unique identifiers | We use technical identifiers, such as account and application IDs, only for sign-in, access control and audit logs. We do not use them to combine information about a person from unrelated sources. |
IAA Code of Conduct 2014: where Admitto helps
You remain responsible for meeting the Code. Admitto keeps your records consistent and traceable for parts of the work; it does not replace your judgement or your duties to clients. See the Terms of Service.
| Clause | Topic | How Admitto helps |
|---|---|---|
| cl. 4 | Confidentiality | Admitto is software used by licensed advisers. It is not an immigration adviser. Passport numbers and dates of birth are held in the adviser record and are not included in the profile sent to the assessment model. Documents you upload are sent in full to our AI subprocessor to be classified and read, including any identifiers they contain. Advisers keep their duty of confidentiality over all client information they hold. |
| cl. 26 | Record-keeping | Each assessment keeps its findings, the sources cited and a snapshot of what it relied on. A SHA-256 seal over that record shows whether anything has changed, and Admitto can check the seal before it produces a PDF or RFI letter. |
| cl. 31 | Applications: no false or misleading documentation to the decision maker | Each finding is traced to the INZ instruction or legislation it rests on, and records which policy snapshot and engine versions were in force, so an adviser can check a finding before relying on it. What is lodged with INZ, and the completeness of the client file (cl. 26), remain the adviser's responsibility under the Code. |
The audit seal
When an assessment finishes, Admitto saves a snapshot of what it relied on: the client profile fields it used, a fingerprint of each INZ section it retrieved, the rule results, the findings, and the thresholds and model in force at the time.
A SHA-256 hash is calculated over that snapshot and stored with the assessment. Lists are put in a fixed order first, so a harmless change of order does not change the hash. Admitto can recalculate the hash later, for example before producing a PDF or RFI letter, and compare it. If anything in the record has changed, the hashes will not match.
Where data is stored
Client data and sign-in records are held by Supabase in Sydney, Australia (ap-southeast-2). Because data is stored outside New Zealand, the sub-processor list below is our disclosure under the Privacy Act 2020. Current as at 2026-09-09.
The application itself is served by Vercel from its global network. Data is encrypted in transit and at rest as described above and in our Privacy Policy.
Sub-processors
Personal information may be processed outside New Zealand. These are the services that process it, and what each one receives.
| Processor | What it does | What it receives |
|---|---|---|
| Anthropic (United States) | Reading documents, eligibility assessment, and drafting RFI and cover letters | Client profile details for assessment, without passport numbers or dates of birth. Documents you upload are sent in full to our AI subprocessor to be classified and read, including any identifiers they contain. |
| Voyage AI (United States) | Embeddings / reranking for retrieval | Search text built from the visa category and profile fields. Voyage AI's own privacy and data processing terms cover retention. |
| Supabase (Sydney, ap-southeast-2) | Postgres database, auth, storage, RLS | Account data, client profiles, assessment results, snapshots, and application metadata. |
| Vercel (global) | Application hosting, serverless functions, CDN | Web requests and responses, including sign-in tokens in transit. |
| Resend (United States) | Transactional email | Recipient address, subject, and message bodies for operational emails (for example assessment complete). |
| Stripe (United States) | Subscription billing | Payment and customer metadata handled by Stripe. Admitto does not store full card numbers. |
| Sentry (United States) | Error and performance monitoring | Error reports and request details. Admitto removes the personal details it recognises before a report is sent. |
If something goes wrong
We monitor Admitto for errors and outages through Sentry, and can check recent assessments against their audit seals. We treat these as incidents that may affect personal information: suspected unauthorised access to adviser or client data, exposed credentials, a long outage that stops you reaching your records, or audit seals that fail to match.
If a privacy breach happens, we notify affected advisers, and the Privacy Commissioner where the Privacy Act 2020 requires it, as soon as practicable, aiming for within 72 hours in line with the Privacy Commissioner's guidance.
Contact
Security and privacy questions: hello@admitto.co