Clientaly
Security

Your clients’ data stays
in Canada, and stays yours

You hold health answers, financial details and identity documents. That is not ordinary CRM data, and it should not sit on ordinary CRM terms.

Isolation is enforced by the database, not the screen

Most multi-tenant software keeps practices apart by filtering queries in the application. That works until one query forgets the filter. Clientaly enforces separation at the row, underneath the application, so a mistake in the interface cannot expose another practice’s book.

Row-level isolation enforced in the database, not in application code
Write protection across every table that holds client data
An agency admin sees their agency — never another practice
Access to sensitive records is logged and reviewable
Multi-factor authentication available on every account
Encrypted in transit and at rest
isolation · enforced in the database
not a filter in the app

Hosted in Canada. Not “mostly” in Canada.

Data residency is the first question an insurer or MGA asks in a review, and ‘our provider has a Canadian region’ is not the same answer as ‘our data is in it’.

Canadian region

The database runs in the Canadian Central region and the client records live there. This is a deliberate choice, not a default we inherited.

Your data is yours

Your book belongs to you. Export is available, and we will not hold your client records hostage if you decide Clientaly is not for you.

Backed up, and recoverable

Backups run automatically. The question that matters is not whether backups exist but whether they restore, and that gets tested rather than assumed.

Written down, not just claimed

Versioned legal terms

Terms, Privacy Policy and Data Processing Terms are versioned, published, and accepted in-app against an immutable record. The page you read here is the same text you accept inside the platform.

A breach register that exists

PIPEDA requires you to record breaches of safeguards whether or not they are reportable. Clientaly gives you somewhere to do it, rather than leaving it to a document nobody created.

Access logging on sensitive data

Who opened a client record, and when. It is uncomfortable to look at and exactly what you want to have when a question is raised.

Consent as a record, not a setting

Consent has a version and a history. You can show what was agreed, and when it changed, without reconstructing it from email.

What we will not claim

Clientaly is not SOC 2 certified and we are not going to imply otherwise with a badge. It is a Canadian platform built by a practising advisor, with the controls described on this page in place and in use. If your MGA has a security questionnaire, send it — you will get straight answers to it, including where the answer is “not yet”.

Send us your security questions

Including the awkward ones. We would rather answer them now than have them surface during your review.

Book a walkthroughSee pricing