QEMRA legal
Messaging & Consent Policy
This document explains the rules, responsibilities, and protections that apply when you use QEMRA.
1. Purpose
QEMRA is designed for expected, permission-based business messaging. This policy sets minimum standards for contact lists, consent, templates, opt-outs and automated messaging.
2. Before contacting a person
A business must have a valid basis to contact a person and must comply with applicable law and platform policy.
For WhatsApp, the business is responsible for satisfying WhatsApp’s current opt-in requirements, including ensuring that the person provided the relevant number and agreed to receive messages from the named business.
3. Consent records
QEMRA may record consent source, date/time, acquisition source, categories of messages, proof/reference information, and opt-out/re-opt-in history.
The customer remains responsible for the validity of its consent.
4. Prohibited lists
QEMRA does not permit purchased, scraped, harvested, unlawfully shared or otherwise non-consensual contact lists.
5. Business-initiated WhatsApp messages
Where WhatsApp requires an approved message template for a business-initiated message, the business must use a permitted template.
QEMRA may assist with creating templates, submitting templates, tracking approval/rejection/pause status, suggesting compliant revisions and using approved templates in workflows.
Meta/WhatsApp retains sole control over template approval and messaging eligibility.
6. Customer-service window
Where WhatsApp permits ordinary replies during a user-initiated customer-service window, QEMRA may send non-template messages consistent with the active conversation and platform rules.
The applicable window and platform rules are controlled by Meta and may change.
7. Marketing messages
Marketing/promotional messages may be sent only when the recipient has validly opted in where required, the message is lawful, the sender is accurately identified and applicable Meta/WhatsApp rules are met.
8. Opt-out handling
A clear opt-out such as “STOP”, “unsubscribe”, “don’t message me” or another unambiguous request will stop promotional messaging.
QEMRA may automatically mark the contact as opted out and suppress future promotional messages until a new valid opt-in is recorded.
Marketing opt-out does not necessarily block necessary non-promotional service messages such as booking confirmations, receipts, security notices or support replies where permitted.
9. Message frequency and expectations
Businesses should send only the type and frequency of messages a recipient would reasonably expect from the consent given.
High complaint, block or negative-feedback rates may lead to QEMRA restrictions and may also trigger Meta/WhatsApp enforcement.
10. Automation disclosure and human help
Automated or AI-assisted interactions should be disclosed clearly at the start of the interaction or when materially relevant.
Where the business provides human support, QEMRA should provide a clear path to request a person.
11. Sensitive messaging
Sensitive actions and high-impact topics require stricter controls. QEMRA may force review, safe fallback or human handoff where risk is higher.
12. Responsibility
The business customer—not QEMRA—is responsible for the legality and accuracy of its campaigns, claims, offers, consent records, customer relationships and message content.
