Security & data residency
Sensitive files, kept in Canada and under your control
Immigration files hold passports, police certificates, medical results and family histories. VisaNest is designed so that information is stored in Canada, stays inside your firm, and never goes anywhere without a practitioner’s say-so.
A client uploads a document
Encrypted in transit with TLS
It is stored in a Canadian region
Montréal or Toronto, encrypted at rest
Agents read it and draft
Inside your firm’s isolated workspace
A practitioner reviews
Nothing goes out without sign-off
Every step is logged
Who, what, when, and from which source
Where things stand. VisaNest is an early-stage product. This page describes how the platform is designed and how production hosting is planned. The demo you can open today has no backend: its fictional data lives only in your browser’s local storage.
Controls
Seven commitments built into the design
Each one answers a question a regulator, an insurer or a careful client might reasonably ask about where their information goes.
Canadian data residency
Production hosting is planned on Google Cloud’s Canadian regions in Montréal and Toronto. VisaNest is designed to store client records, uploaded documents and backups inside Canada, with one region serving as the other’s fallback.
- Primary and secondary regions both in Canada
- Database records, files and backups kept in-country
- Residency treated as a product requirement, not an add-on
Planned primary
Montréal
northamerica-northeast1
Planned secondary
Toronto
northamerica-northeast2
Encryption in transit and at rest
Every connection to VisaNest is designed to use TLS, and stored data, including documents and backups, is encrypted at rest with keys held in Google Cloud’s key management service.
- TLS for the workspace, client portal and integrations
- Encrypted databases, file storage and backups
- Short-lived signed links for document downloads
Role-based access control
Each person sees and does only what their role allows. Representatives, case managers and assistants get different permissions, and clients only ever see their own file through the portal.
- Separate roles for representatives, staff and clients
- Approval rights reserved for licensed representatives
- Access withdrawn the moment someone leaves the firm
Isolation for every firm
Each firm’s workspace, knowledge vault and client data are kept logically separate, and every request is scoped to a single firm. One practice’s templates or precedents are never visible to another.
- Per-firm scoping on every query and file
- Knowledge vault private to your practice
- Firm material never used to train AI models
AI output approved by a practitioner
Agents prepare drafts. Messages, forms, filings and charges wait in an approvals queue until a licensed representative releases them, and any agent can be paused or limited to specific workflows.
- Approvals queue for anything client- or IRCC-facing
- Each agent runs only the workflows you switch on
- Pause any agent with one click
An audit log of every agent action
Every read, draft, change and approval is designed to be recorded with who or what did it, when, and which documents it relied on, so you can trace how any form value or message came to be.
- Agent and human actions in one timeline
- Source documents linked to each change
- Exportable for your own records
Backups with alerting
Automated, encrypted backups are designed to run every day within Canadian regions, with monitoring that alerts the team to failed backups, service errors and unusual access patterns.
- Daily encrypted backups kept in Canada
- Point-in-time recovery for the database
- Alerts on failures and unusual activity
Shared responsibility
Software does its part. The practice stays accountable.
VisaNest is a tool for licensed practitioners, not a substitute for their judgment or their professional obligations.
VisaNest is designed to
- Store client data in Canadian cloud regions
- Encrypt data in transit and at rest
- Keep every firm’s data isolated
- Record every agent action in an audit log
- Hold agent output until a practitioner approves it
Your practice stays in charge of
- Deciding who on your team gets which role
- Reviewing and approving what agents prepare
- Client consent and your regulator’s record-keeping rules
- The advice you give and the applications you file
Questions from your compliance team?
Bring them to a walkthrough. We’ll go through where data lives, how access works and exactly what the audit log records.