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.
Consent at the start, opt-out on any channel.
Two things the runtime does on every conversation: it discloses call recording before the call gets going, and it acts on “stop” the moment it arrives, whichever channel it arrives on.
Outbound.
Call-recording consent, at the start of every call.
The call proceeds on the record.
The recording is retained so the call can be audited.
Handled immediately. Contact flagged.
Handled immediately. Contact flagged.
Handled immediately. 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.
Built in Vancouver by Alexander Innovation Centre, Canadian-owned.
PIPEDA and CASL compliance built in.
“Stop” on any channel is handled immediately and the contact flagged.
Consent is disclosed at the start of every call, and recordings are 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