Everything your onboarding clerk needs, in one place.

Data residency

Client production data is hosted in Canadian regions, named per engagement in the statement of work. This website itself is static, sets no cookies and runs no third-party trackers: there is no visitor data to reside anywhere.

Encryption

TLS for all data in transit. Encryption at rest on the client systems we provision.

Access control

Least-privilege access: people get the minimum access their role requires, and no more. Multi-factor authentication on all administrative access. When someone leaves an engagement, access is removed within one business day.

Subprocessors

Published per engagement in the statement of work, so you approve the list before work starts. None are embedded in this website.

Backups and retention

Backup schedules and retention periods are defined per engagement in the statement of work. At contract end, client data is returned or destroyed on request, and we confirm in writing.

Incident response

If an incident affects client data, we notify affected clients without undue delay and cooperate fully with municipal and provincial reporting obligations.

Privacy law posture

PIPEDA governs our commercial work. For public-sector work, MFIPPA and FIPPA obligations flow into our contracts, and we support records requests within contract timelines.

What we do not claim

We hold no third-party security certifications today, and we do not pretend otherwise. What you get instead is a small firm where the people who hold the credentials are the people doing the work, contractual commitments on everything above, and answers to your security questionnaire from the principals, in writing, before award.

Status verified August 2026

Scope by default

Deployments are informational-only. No automated administrative decisions: the system never approves, denies, prioritizes or adjudicates anything. A human decides, always.

Grounding

Retrieval-only over curated, client-approved sources. Every answer cites its source, so staff and residents can verify it. The system declines questions outside its corpus rather than guessing.

Human in the loop

Every deployment includes an escalation path to a named human. When the system cannot answer, or the visitor asks for a person, it hands off rather than improvising.

Testing

Bias and accuracy testing before launch, then monthly in production, with results reported to the client. Accuracy is measured against the approved corpus, not against impressions.

Residency

Models and data are configured for Canadian residency per engagement, named in the statement of work.

Ownership

Clients own the prompts, configurations and outputs of their deployment. There is no lock-in by design.

Alignment

Our deployments are designed to align with the federal Directive on Automated Decision-Making and the federal FASTER guiding principles for generative AI. Because our systems make no administrative decisions, they sit deliberately below the Directive's risk thresholds.

Statement prepared August 2026

Where these commitments ship

This statement is not aspirational. It describes two priced offers you can buy today.