Skip to content
Hosted in Australia

Your data lives in Australia.

All client data is encrypted at rest in Sydney. Documents on AU-pinned storage. Every organisation gets its own encryption key. Your data is sealed off from every other tenant.

Last updated: May 2026

SydneyDatabase region
AES-256-GCMPer-organisation keys
TLS 1.3In-transit encryption
One SessionPer user, enforced

Where your data physically lives

Every layer of the hot path runs in Australia.

Database, application servers and object storage are pinned to Sydney. Edge protection runs through a global network with TLS terminated at the closest Australian point of presence.

ComponentProviderRegion
DatabaseAWSap-southeast-2 (Sydney)
Application serversVercelsyd1 (Sydney)
Document storageCloudflare / AWSOC (Oceania, AU/NZ)
Edge / DDoS / WAFCloudflare, Vercel, AWSGlobal, AU PoPs primary

Defence in depth

Six layers between an attacker and your client data.

A breach has to defeat every one of these in sequence. We build assuming the layer above will eventually fail.

1

Layer 1

Edge & Transport

Cloudflare/Global, AU PoPs primary

  • TLS 1.3 enforced (no downgrade)
  • Always-on DDoS mitigation
  • Web Application Firewall (OWASP rules)
  • Bot management, automated rate limiting
  • DNSSEC and HSTS preload
  • TLS terminated at closest AU PoP
2

Layer 2

Application Runtime

Vercel/syd1 (Sydney)

  • Serverless functions pinned to Sydney
  • Encrypted environment secrets
  • Per-deployment immutable hashes
  • Auto-scaled, no shared instances
  • HTTPS-only enforcement
  • Integrated audit log
3

Layer 3

Database

AWS/ap-southeast-2 (Sydney)

  • AES-256 encryption at rest
  • Point-in-time recovery (PITR)
  • Automated daily snapshots
  • All queries parameterised (no string SQL)
  • Per-organisation row-level isolation
  • TLS 1.3 channel-bound connections
4

Layer 4

Application Authentication

ImmiIQ/Application layer

  • Passwordless magic-link sign-in
  • Sessions expire after 24 hours
  • One active session per user
  • Brute-force protection on every account
  • Sign-in activity log per user
  • IP allowlist for Enterprise teams
  • Sign in with Google or Apple
  • Strict tenant isolation on every request
5

Layer 5

Per-Member Access Control

ImmiIQ/Application layer

  • Three data scopes per member: all clients / their team / assigned only
  • Ten module switches per member to lock specific surfaces
  • Named role templates with bulk apply across the team
  • Sub-team grouping with optional default role + sync
  • Restrictions enforced at the database, not the UI
  • Direct API calls return the same restricted set the user sees
  • AI assistant honours the same scope on every tool call
6

Layer 6

Per-Organisation Encryption

ImmiIQ/Application layer

  • Industry-standard authenticated encryption
  • Unique encryption key derived per organisation
  • Sensitive client data encrypted at rest
  • Search remains fast on encrypted records
  • Integration credentials and session tokens sealed
  • Key rotation invalidates every prior ciphertext

Document access

No public document URLs. Ever.

Every uploaded passport, visa letter and financial record is stored behind a server-side authorisation check. Direct URLs to documents do not exist. When an authenticated agent opens a document, ImmiIQ mints a signed URL that expires in one hour. After expiry the link is permanently invalid.

Signed URLs only

Every download generates a unique, time-limited URL. Sharing the link does not share access beyond one hour.

Cross-organisation isolation

Even at the database level, no agent in one organisation can request a document URL belonging to another.

Australian primary placement

Documents on Cloudflare / AWS object storage with Oceania (Australia / New Zealand) primary placement.

Audit trail

Every document open, download and share is logged. Admins can review the full history.

Compliance

What we comply with.

Every claim on this page is implemented in code. Procurement teams who check the detail will find what we publish is exactly what we run.

  • Australian Privacy Act 1988 / Australian Privacy Principles
  • MARA Code of Conduct (privacy and confidentiality)
  • GDPR principles for any EU clients you serve
  • OWASP Top 10 aligned (parameterised SQL, input sanitisation, output encoding)
  • Cross-organisation data isolation at the request boundary
  • Role-based permissions (Admin / Member)

Shared Responsibility

Where our responsibility ends and yours begins.

ImmiIQ secures the platform. Your firm secures how it is used. The matrix below makes the line explicit so there is no ambiguity for procurement, compliance or your own internal policy.

ImmiIQ secures
  • AES-256-GCM encryption at rest with a per-organisation key derived such that ImmiIQ engineers cannot read sensitive fields by querying the database.
  • TLS 1.3 in transit on every network hop.
  • AU-only hosting (Sydney ap-southeast-2), AU-pinned document storage.
  • Notifiable Data Breaches scheme compliance, OAIC notification, breach runbooks.
  • Least-privilege engineer access; production access logged and audited.
  • Per-organisation tenancy - your data is sealed off from every other ImmiIQ customer at the database layer.
You secure
  • Account credentials for every user in your firm (strong password, no shared logins).
  • Multi-factor authentication once we ship it; until then, treat passwords like keys.
  • What you do with data once it leaves ImmiIQ - email forwards, exports to your laptop, screenshots in Slack, assistants you delegate access to.
  • Disclosure to government bodies and third parties at your discretion under your professional obligations.
  • Who in your team you grant access to which client records (use our roles and per-module toggles).
  • Revoking access promptly when a team member leaves your firm.

Liability

ImmiIQ is not liable for client data exposure that results from actions taken outside the platform - forwarding emails to unauthorised recipients, exporting documents to personal storage, sharing login credentials, or any downstream disclosure inconsistent with your professional obligations. The encryption protections described above apply to data at rest and in transit within ImmiIQ. Once data leaves the platform under your direction, your firm's own controls and obligations govern.

Frequently asked

Common questions about your data

The things procurement teams, Registered Migration Agents (still widely known as MARA agents) and law-firm partners ask before signing.

Security contact

Found something? Tell us.

Responsible disclosure welcome. We respond within one business day and credit researchers in our public security log if requested.

For procurement requests, please contact your account manager or [email protected].

Data Security & Australian Hosting | ImmiIQ Migration CRM | ImmiIQ