Anti-Spam & Messaging Compliance Policy

The consent, registration, and content rules that keep your messaging traffic compliant across channels and markets.

Draft for legal review. Template for Azmarq Technovation Pvt. Ltd., incorporated into the Terms of Service and complementing the Acceptable Use Policy.

1. Purpose and scope

What this Policy governs.

This Policy sets out the messaging-specific compliance obligations for all traffic sent through Azmarq Technovation Pvt. Ltd. ("Azmarq") across WhatsApp Business API, Google RCS, SMS (including SMPP), Voice 360, email, and related automation such as Customer Journeys, Drip Campaigns, CTWA lead messaging, Unified Inbox outbound replies, and AI Agent Studio-assisted sends. It applies to every customer, user, and reseller. Compliance is a condition of using the Services. Channel-specific notes also appear in our Service-Specific Terms.

2. Consent

The permission required before you message anyone.

You must obtain and retain demonstrable consent from each recipient appropriate to the message category, and be able to produce evidence of it on request. Consent must be freely given, specific, and informed, and must not be assumed from the mere existence of a phone number or email address. Different categories (transactional/service versus promotional/marketing) carry different consent standards; apply the stricter standard where in doubt.

3. Opt-out and suppression

Honouring the recipient's choice to stop.

Every promotional message must offer a clear, working opt-out mechanism (such as STOP for SMS, or unsubscribe for email). You must process opt-outs promptly, maintain up-to-date suppression lists, and never message a recipient who has opted out, regardless of the channel through which they did so.

4. India — TRAI and DLT compliance

The specific regime for Indian traffic.

For traffic to Indian recipients, you must comply with TRAI's Telecom Commercial Communications Customer Preference Regulations and the DLT (Distributed Ledger Technology) framework. This includes registering your entity (Principal Entity), headers/sender IDs, and content templates on the DLT platform; sending only content that matches a registered, approved template of the correct category; respecting recipient preferences and DND registrations for promotional traffic; and observing permitted time windows for promotional communications. Azmarq is registered as a TRAI/DLT-compliant provider; you remain responsible for the accuracy and approval of your own headers, templates, and consent.

5. Channel policies

Rules imposed by the channels themselves.

Traffic must comply with the policies of the relevant channel and its provider, including Meta's WhatsApp Business and Commerce policies for WhatsApp traffic (template approval, quality ratings, the customer-service window, and category rules), RCS agent policies, and email sender requirements (authentication such as SPF/DKIM/DMARC, and anti-spam law). Violations can result in template rejection, quality-rating downgrades, number bans, or channel-level suspension outside Azmarq's control.

6. Content categories and integrity

Sending the right message under the right label.

You must correctly classify traffic (transactional, service, authentication, or promotional/marketing) and ensure content matches the declared category and any registered template. You must not disguise promotional content as transactional, forge sender identities, or use content designed to evade filtering.

7. Prohibited messaging practices

What is never acceptable.

Prohibited practices include: unsolicited bulk messaging (spam); use of purchased, scraped, or non-consented lists; snowshoeing or traffic distribution designed to evade registration or filtering; phishing, smishing, and fraud; grey-route or unauthorised international routing; and any content prohibited under our Acceptable Use Policy.

8. Monitoring, filtering, and enforcement

How we protect the ecosystem.

Azmarq and its operators and channel partners may inspect traffic and metadata to detect spam, fraud, and policy violations, and may filter, throttle, suspend, or block traffic and accounts that breach this Policy. We may report violations to operators, channel providers, and regulators. Repeated or serious breaches may result in termination.

9. Your responsibility and indemnity

Where accountability sits.

You are responsible for the lawfulness of your traffic, your consent records, your DLT registrations, and your recipient data. You agree to indemnify Azmarq against claims, penalties, and losses arising from your breach of this Policy, consistent with the indemnity in our Terms of Service.

10. Changes and contact

Updates and where to reach us.

We may update this Policy; the "Last updated" date reflects the current version. Compliance questions and reports: legal@azmarq.com / abuse@azmarq.com.