Canadian data residency, Canadian compliance.
Alebex is built in Vancouver and Canadian-owned, and the data the platform handles stays in Canada. Consent and opt-out are part of the runtime rather than a policy written next to it.
Configurable consent and opt-out controls.
Two controls the runtime gives you on every conversation: a configurable call-recording consent disclosure, and configurable opt-out controls across channels.
Outbound.
Configurable call-recording consent disclosure.
The call proceeds on the record.
The recording is retained so the call can be audited.
Configurable opt-out controls. Contact flagged.
Configurable opt-out controls. Contact flagged.
Configurable opt-out controls. Contact flagged.
Stored in Canada.
Arrangement, not to scale. The drawing shows order and routing; it states no duration.
Stated exactly as they are, with nothing added.
Each one is something the platform does, not something it intends to do.
Recordings, transcripts and customer information are held in Canada.
A Vancouver-based Canadian AI company, incubated at the Alexander Innovation Centre.
Designed to support PIPEDA, CASL and applicable CRTC requirements, with configurable consent, disclosure, opt-out and retention controls. No certification implied.
Configurable opt-out controls across channels, with the contact flagged.
Configurable call-recording consent disclosure, with recordings stored for audit.
PIPEDA and CASL.
If a framework is not named here, Alebex is not claiming it.
“We felt good that Alebex is built in Canada and the data is stored here. As an educational institution, compliance is important for us, so this was helpful when we decided to use Alebex.”
The four documents below describe how this works in writing.
They are drafts pending review by counsel, and each one says so on its face.
Security questions
Send security and privacy questions to the team in Vancouver. Answers come back as what Alebex does today, not as what it plans to do.
Subject: Security