Service-Specific Terms

Product and channel terms that supplement the general Terms of Service for Azmarq Technovation Pvt. Ltd. (India).

Draft for legal review. Template for Azmarq Technovation Pvt. Ltd. These terms form part of the Terms of Service. An executed MSA or order form prevails in case of conflict. Not legal advice.

1. Purpose

How these terms fit with the rest of the agreement.

These Service-Specific Terms describe additional rules for individual Azmarq products and channels. They apply when you enable or use the relevant feature. General obligations in the Terms, Acceptable Use Policy, Anti-Spam & Messaging Compliance Policy, Privacy Policy, DPA, AI & Automated Processing Policy, and Data Retention Policy continue to apply.

2. WhatsApp Business API

Meta-dependent messaging.

WhatsApp traffic is delivered via Meta and is subject to Meta's WhatsApp Business and Commerce Policies, template approval, quality ratings, messaging windows, and category rules. Azmarq acts as a WhatsApp Business Solution Provider (BSP) / partner as applicable. Meta may reject templates, downgrade quality, or restrict numbers outside Azmarq's control. You must maintain valid WABA setup, business verification, and opt-in practices. Per-WABA or conversation fees follow your plan and Meta's pricing changes may flow through with notice where required.

3. Click-to-WhatsApp Ads (CTWA)

Ads that open chats.

CTWA connects Meta advertising with WhatsApp conversations. You are responsible for ad creative compliance, Meta Ads policies, lead handling, and downstream messaging consent. Lead data captured into Azmarq (for example into My CDP, Journeys, or Inbox) is Customer Content processed under your instructions. Azmarq does not guarantee ad delivery, cost-per-result, or conversion rates.

4. WhatsApp Commerce

Catalogues, orders, and payments features.

Where commerce features are enabled (catalogues, order updates, or payment-related flows), you remain the merchant of record for goods and services sold to end users unless a written agreement says otherwise. You must comply with applicable consumer, tax, and payments rules. Payment processors engaged for checkout are listed or referenced in Sub-processors when they process personal data on our behalf.

5. Google RCS

RCS Business Messaging.

RCS traffic must comply with Google RCS Business Messaging policies and any operator partner requirements for branding, consent, and content. Agent verification and throughput limits apply. Delivery depends on device and carrier RCS capability.

6. Messaging SMS and SMPP

SMS and enterprise connectivity.

SMS and SMPP services depend on telecom operators and aggregators. For Indian traffic you must complete TRAI/DLT Principal Entity, header, and template registrations and send only matching approved content. SMPP customers must secure binds, respect throughput, and not share credentials. Grey routes, spoofed originating addresses, and unregistered promotional traffic are prohibited.

7. Voice 360

Voice calls, IVR, and recordings.

Voice features may include outbound/inbound calling, IVR, and optional call recording or transcription. You must obtain any legally required consent for recording and for contacting recipients, and comply with telemarketing and Do-Not-Disturb rules. Call recordings and transcripts are Customer Content; retention follows your configuration and the Data Retention Policy.

8. Email Marketing

Transactional and promotional email.

You must authenticate sending domains (SPF/DKIM/DMARC as applicable), honour unsubscribes for marketing mail, and comply with applicable anti-spam law. Azmarq may suspend sending that harms shared reputation or triggers blocklists.

9. My CDP

Customer data platform profiles.

My CDP stores and segments profile and event data you ingest. You are the Data Fiduciary for end-user profiles. You must not upload special-category or unlawful data except as permitted by law and agreed in writing. You control syncs into Journeys, campaigns, and channels. Azmarq processes CDP data as Processor under the DPA.

10. Customer Journeys and Drip Campaigns

Automated multi-step outreach.

Journeys and Drips send messages based on triggers and schedules you configure. You remain responsible for consent, frequency capping, quiet hours, category labelling, and suppression. Automated sends that breach messaging rules may be throttled or blocked.

11. Fallback Solutions

Channel failover.

Fallback routes messages to an alternate channel when a primary channel fails or is unavailable. You must ensure each fallback channel has its own lawful basis, registrations, and templates. Failover does not guarantee delivery.

12. Unified Inbox

Shared agent access to conversations.

Unified Inbox allows authorised users to read and reply to customer conversations across channels. You must manage agent access, least privilege, and confidentiality. Message content visible to agents is Customer Content under your control.

13. AI Agent Studio

AI-assisted agents and automation.

AI Agent Studio features are additionally governed by the AI & Automated Processing Policy. Outputs may be inaccurate; you must supervise high-risk use cases and remain responsible for messages sent to end users.

14. Developer APIs and documentation

Programmatic access.

API use must respect authentication, rate limits, and documentation at developers.azmarq.com. You must not scrape, load-test production without permission, or share API keys. Sandbox and production environments may differ in SLA coverage.

15. Changes and contact

Updates and where to reach us.

We may update these terms; the "Last updated" date reflects the current version. Questions: legal@azmarq.com.