Anti-Spam & Responsible Messaging

1. Scope and responsibility

These rules apply to customers and authorized users sending email, SMS/MMS, in-app messages, browser notifications or automated alerts through MigiHub. They supplement the customer agreement and applicable law.

The sender is responsible for the recipients, purpose, content, consent and legal basis. Availability of a messaging feature does not establish permission to contact someone.

2. Classify the message

A commercial electronic message promotes a product, service or commercial activity. A service notice communicates operational information, such as a booking change or security alert. Adding promotion can change the legal treatment of an otherwise operational message.

Do not assume that an existing account, public email address or “transactional” label creates a blanket exemption. Assess Canada’s CASL, applicable U.S. email/SMS rules, and EU/UK privacy and electronic-communications rules according to the sender, recipient and message.

3. Collect and prove permission

Use clear, affirmative consent for marketing as the baseline. Explain the sender, purpose, channel and withdrawal method; do not pre-check optional boxes. Keep consent separate by channel where appropriate. Double opt-in can help validate addresses.

If relying on implied consent or a statutory exception, document its exact conditions and any expiry. A publicly listed address is not automatically permission. Purchased, rented, harvested or scraped recipient lists are prohibited for unsolicited campaigns through MigiHub. A request for consent may itself be a commercial message and requires its own lawful basis.

4. Identify the sender and destination

Use accurate sender names, headers and subjects. Identify the organization and, where required, the person on whose behalf it is sent. Include the required mailing address and a valid contact method. Keep required contact information and unsubscribe mechanisms valid for the legally required period.

Use recognizable links and truthful content. Never include phishing, malware, deceptive claims, disguised destinations or content that infringes privacy or other rights.

5. Unsubscribe and suppression

Provide a clear, free and readily usable unsubscribe method where required. Do not require a login, payment or unnecessary personal information. Under CASL, give effect to an unsubscribe request without delay and no later than 10 business days. Apply any shorter deadline required elsewhere.

Maintain channel-appropriate suppression records and check them before every send. Deleting an unsubscribed contact must not cause the address to be re-imported and contacted again. Marketing withdrawal does not automatically block legally necessary service notices, which must be assessed separately.

6. SMS and automated programs

Before enabling SMS, confirm the provider, sender registration, opt-in wording, message frequency disclosure, applicable carrier charges, opt-out and help handling, and local quiet-hour rules. Support STOP/HELP or the applicable provider’s equivalent where required.

Test suppression and delivery handling before launch. Do not rotate sender identities to evade blocking or send sensitive appointment, health or payroll details unnecessarily in notifications.

7. Records and pre-send checks

Retain proportionate evidence of consent type, source, date, wording/version, purpose and channel; applicable expiry; unsubscribe and complaint dates; and relevant send records. Do not collect unnecessary device or identity data merely to build a consent log.

• Confirm recipient eligibility and suppression status.
• Check sender identity, lawful purpose and unsubscribe behavior.
• Remove unnecessary sensitive information.
• Review frequency, recipient time zone, message volume and delivery limits.
• Verify configured consent, bounce, opt-out and audit capabilities; availability depends on the tenant and messaging provider.

8. Complaints, enforcement and updates

Report suspected messaging abuse to support@migihub.com; use security@migihub.com for phishing or security threats. Provide the sender, date and a non-sensitive example. Senders should promptly suppress complainants and investigate the source and campaign.

Misuse can lead to warnings, rate limits, feature suspension or account termination under the agreement, and legally required reporting. These guidelines may change with law or provider requirements. They do not replace a sender’s jurisdiction-specific assessment.