Compliance

Compliance built in, not bolted on

HonkIO enforces Canadian anti-spam and privacy law at the API level for text messages and email, and stores push data in Canada with the rest. You cannot accidentally send a non-compliant text or commercial email.

01

CASL: Canada's Anti-Spam Legislation

S.C. 2010, c. 23 · In force since July 1, 2014

Enforced

CASL requires that every commercial electronic message (CEM) sent to a Canadian recipient must have the recipient's express or implied consent. Violations can result in administrative monetary penalties up to $10 million per violation for organizations. HonkIO enforces CASL requirements programmatically.

Express Consent

  • Recorded with timestamp, source IP, and description
  • Stored immutably in audit log
  • Never expires unless revoked by the recipient
  • Required for cold outreach / new contacts

Implied Consent

  • Applies to existing business relationships
  • Auto-expires: two years after a purchase, six months after an inquiry (CASL s. 10(10))
  • Expiry date tracked and enforced by API

Email falls under the same law. A receipt, a password reset or an account notice is transactional, and CASL does not ask for consent before it. A promotion is a commercial electronic message, and it does. HonkIO sends email as transactional unless you mark it commercial, and checks consent for the address when you do.

Commercial email

  • Consent recorded per email address, through the same consent API as phone numbers
  • No consent on file for the address: refused with HTTP 451, not charged
  • An unsubscribe footer and a one-click unsubscribe header (RFC 8058) on every commercial email
  • An unsubscribe stops commercial email at once; receipts and resets still arrive

Suppression and reputation

  • A hard bounce or a spam complaint suppresses the address for every email
  • Refusals name their reason: EMAIL_NO_CONSENT, EMAIL_OPT_OUT_BLOCKED or EMAIL_SUPPRESSED
  • Live email pauses for 24 hours when bounces or complaints run high, with a webhook and an email saying why
  • Unsubscribes and complaints arrive as signed webhooks, like SMS opt-outs

Push works differently. A push reaches only the phones and browsers your app registered, once the person has allowed notifications where the system asks for it, as iOS, Android 13 and later and browsers do. HonkIO keeps no consent record for a push. A text sent as a push's fallback goes through every SMS rule.

Push

  • Your app asks the person to allow notifications, then registers the phone or browser under your own user ID
  • A push goes only to that user's registered devices, and tokens that stop working are retired
  • A fallback text goes through every SMS rule: consent, opt-outs and sending limits
  • For a device that registered a key, optional encryption keeps Apple and Google from reading the content

Notify

  • Each text or email a notification tries goes through that channel's checks: consent, opt-outs, suppressions and sending limits
  • A refused channel moves the notification to the next one, and a recipient profile is never consent
  • Notifications are transactional by default: a commercial email needs CASL consent on file and carries an unsubscribe footer
SMS: STOP / UNSTOP keyword handling: When a recipient replies with STOP, STOPALL, UNSUBSCRIBE, QUIT, END, CANCEL, or the French ARRET (ARRÊT), HonkIO automatically opts them out within seconds, not the 10 business days allowed by law. START and UNSTOP keywords re-instate consent. Your webhook is notified of all opt-out events.

Pre-send gate

The API rejects any text to an opted-out number, and any commercial email to an address without consent or that unsubscribed, with HTTP 451 Unavailable For Legal Reasons. There is no way to override this from the API. Every blocked text, and every commercial email sent, is written to the audit log.

451Unavailable For Legal Reasons$0
{ "code": "NO_CONSENT",
  "message": "Message blocked: no valid CASL consent on record for this recipient.",
  "messageFr": "Message bloqué : aucun consentement LCSPC valide enregistré pour ce destinataire." }
02

CRTC Do Not Call List (DNCL): calls and faxes, not texts

Telecommunications Act · CRTC Rules on Unsolicited Telecommunications

The National Do Not Call List (DNCL) and the CRTC's Unsolicited Telecommunications Rules govern telemarketing calls and faxes. They do not govern text messages: section 41(2) of the Telecommunications Act takes commercial electronic messages, texts included, out of the CRTC's rules on unsolicited telecommunications, and CASL governs them instead. So a text is never checked against the DNCL, at HonkIO or anywhere else. What decides who you may text is CASL consent, which HonkIO checks before every send (see CASL above).

The DNCL lists telephone numbers only. Email is not on it; CASL consent and unsubscribes govern email instead.

03

PIPEDA / Privacy Act

Personal Information Protection and Electronic Documents Act · S.C. 2000, c. 5

In place

Canadian Data Residency

  • All data stored in Canada
  • Database & cache hosted in Beauharnois, Quebec
  • PostgreSQL & Redis in Beauharnois, Quebec, with encrypted database backups in Toronto
  • Canada-only carrier messaging profile
  • Sent and received email, with its attachments, stored in Quebec, with encrypted backups in Toronto
  • Push credentials, device tokens, content and logs stored in Beauharnois, Quebec, with encrypted backups in Toronto
  • Recipient profiles stored in Beauharnois, Quebec, with encrypted backups in Toronto
  • HonkIO Auth users, sessions, passkeys and sign-in history stored in Beauharnois, Quebec, with encrypted backups in Toronto

Data Minimization & Retention

  • Text and email bodies purged after 90 days by default
  • A received email's raw message and attachments deleted after 40 days
  • Configurable retention period per account
  • Audit logs retained separately (immutable)
  • Right-to-erasure API endpoint included
  • HonkIO Auth abuse data (IP addresses, device cookies, risk scores) kept 90 days, then deleted or reduced to counts
04

Quebec Law 25 (Loi 25)

An Act respecting the protection of personal information in the private sector · In full force since September 2023

In place

Quebec Law 25 (Bill 64) imposes GDPR-like obligations on organizations handling personal information of Quebec residents. HonkIO's architecture supports these requirements.

  • Privacy impact assessment (PIA) documented for data flows
  • Right to access personal information via API
  • Right to erasure endpoint wipes all PII for a number
  • Data portability: export all consent and message records
  • Privacy officer contact in all error communications
  • Incident notification procedures in place
  • HonkIO Auth: your privacy terms govern your users' data, HonkIO processes it on your behalf, and you can export your users at any time

Data stored in Canada

Your text messages, sent and received email, push notifications, phone numbers, email addresses, consent records and audit logs are stored in Canada, in Quebec, with encrypted backups in Toronto. Requests are processed in Quebec too, but a push goes through Apple's or Google's servers, so stored in Canada does not mean processed only in Canada.

Questions

This is how HonkIO applies these laws, not legal advice about your own messages.

Do I need consent to send a text message in Canada?
For a commercial text, yes. CASL requires express or implied consent before any commercial electronic message, texts included. HonkIO checks for a consent record before each message it sends to a number, refuses the send with HTTP 451 when there is none or the person has opted out, and a live key cannot skip the check. A verification code goes out without a consent record, since a code whose only purpose is signing in is generally not a commercial message.
Does the Do Not Call List apply to text messages?
No. The National Do Not Call List (DNCL) and the CRTC's Unsolicited Telecommunications Rules govern telemarketing calls and faxes. Section 41(2) of the Telecommunications Act takes commercial electronic messages, texts included, out of those rules, and CASL governs them instead. A text is never checked against the DNCL.
How long does implied consent last?
Implied consent from an existing business relationship lasts up to two years after a purchase or contract, and six months after an inquiry or application (CASL s. 10(10)). HonkIO works out the expiry from the last transaction date, or takes the one you set with expires_at, and refuses texts once it passes. Express consent does not expire unless the person withdraws it.
What happens when someone replies STOP?
HonkIO opts the number out as soon as the reply reaches it, rather than taking the 10 business days the law allows, and refuses every later text to it with HTTP 451. STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT and ARRET (ARRÊT) all count, START and UNSTOP reinstate consent, and your webhook is told of every opt-out.
Where is my data stored?
In Canada. The database and cache that hold your messages, contacts, consent records and audit logs are in Beauharnois, Quebec, where API requests are processed too, and encrypted backups of the database are kept in Toronto. The privacy policy lists the providers that process data outside Canada, such as the one that routes text messages.
Does Notify check consent?
Yes. Each text or email a notification tries goes through the same consent, opt-out, suppression and sending limit checks as the SMS and email APIs, and a refused channel moves it to the next one. A recipient profile is never consent.

Build compliance into your SMS, email and push

Get started free

HonkIO checks CASL consent for texts and commercial email by default. Create a free account and start building. Read the compliance docs →