Messaging Compliance Policy

1. Consent Management (Opt-In)

All business and promotional messages dispatched through Fun Loop API's must be backed by documented consent from the recipient. Consent must be freely given, specific, and verifiable (via web form, contract, or prior business relationship).

2. Mandatory Opt-Out & DND Compliance

Under our built-in compliance framework, all campaigns must honor recipient unsubscribe requests:

• Automated STOP Recognition: Inbound messages matching STOP, UNSUBSCRIBE, QUIT, or DND automatically revoke the recipient's consent in ContactConsents and append the phone number to BlacklistDND.
• Immediate Block: Subsequent automated sends to blacklisted recipients are blocked at the engine layer before consuming API credits or reaching telecom networks.

3. Carrier & Provider Guidelines

• WhatsApp: Senders must adhere to Meta's WhatsApp Business Messaging Policy. Automated accounts must undergo gradual warm-up ramping.
• Telegram: Bots must respect Telegram's flood-wait limits (approximately 30 messages/second broadcast maximum) to prevent HTTP 429 penalties.
• SMS & DLT: Indian domestic traffic must provide registered Principal Entity IDs and Content Template IDs per TRAI TCCCPR regulations.