CASL Compliance

Overview

MeetIndi is built for Canadian businesses that need controlled, auditable customer communication. Canada's Anti-Spam Legislation (CASL) can apply when a business sends a commercial electronic message, including email or SMS. CRTC guidance describes the core requirements as consent, sender identification, and an unsubscribe mechanism.

This page explains the CASL controls MeetIndi applies to product-generated SMS and email workflows. It is a product disclosure, not legal advice for every customer campaign or contact list.

Product Scope

MeetIndi's highest-risk CASL surface is automated follow-up after an inbound call, form submission, waitlist request, signup, test call, or support interaction. These messages may include SMS, email, or other electronic delivery channels configured inside the product.

MeetIndi does not validate a customer's entire historical marketing database. Customers remain responsible for the lawfulness of imported contacts, external campaigns, third-party CRM lists, and communication sent outside MeetIndi.

Consent Controls

MeetIndi requires a consent basis before product-generated commercial SMS follow-up is sent. Depending on the workflow, that basis may be:

• express opt-in through a customer-facing form;
• verbal consent captured during an inbound call;
• a customer-managed consent record imported from an approved source;
• an implied-consent business context that the customer is responsible for validating.

When MeetIndi cannot find a usable consent record for a product-controlled SMS path, the send path is designed to fail closed instead of sending first and auditing later.

Sender Identification

Product-generated commercial messages should identify the business on whose behalf the message is sent. Where space allows, messages also make the MeetIndi-assisted nature of the interaction clear.

For short SMS contexts, MeetIndi prioritizes clear sender identity and opt-out language over long-form legal copy. Longer disclosures can be linked from email, signup, or customer-managed policy pages.

Unsubscribe And Opt-Out

MeetIndi-supported SMS workflows currently recognize these application-level opt-out keywords:

• STOP
• UNSUBSCRIBE

Keyword matching is case-insensitive and whitespace-trimmed. When an opt-out is received, MeetIndi records the revocation and suppresses future commercial SMS from that tenant-controlled path unless fresh consent is later recorded.

Some carriers may intercept additional opt-out keywords before the message reaches MeetIndi. The MeetIndi application does not currently advertise CANCEL, END, QUIT, REMOVE, HELP, INFO, or ? as application-handled keywords.

Customers are responsible for honoring the same opt-out across non-MeetIndi systems they operate, including external CRMs, email tools, or manual outbound sequences.

Consent Records

MeetIndi records consent and revocation events with tenant context, source, event type, channel, and timestamp where available. Revocation is stored as a new event instead of deleting the earlier consent history, preserving an audit trail.

These records support customer review, complaint response, and operational audits. They do not replace customer-side legal review of consent collection language or list provenance.

Customer Responsibilities

Customers using MeetIndi should:

• use accurate opt-in language on forms and call scripts;
• avoid importing purchased, scraped, or unclear contact lists;
• keep consent evidence for contacts gathered outside MeetIndi;
• configure message templates that identify the sender and include opt-out instructions;
• make sure opt-outs are honored across all systems, not only MeetIndi;
• consult counsel for industry-specific CASL, privacy, or professional obligations.

Sources

Public CASL guidance is maintained by the CRTC. Relevant public resources include:

• CRTC CASL FAQ
• CRTC guidance on implied consent
• CRTC anti-spam legislation guidelines

Contact

Questions or reports can be sent to support@meetindi.com. MeetIndi reviews consent complaints and, where appropriate, helps the customer locate the relevant consent or opt-out record.