At Bluemessaggio, we are committed to maintaining the integrity, deliverability, and security of our business messaging ecosystem. All businesses utilizing our platform — including Bulk SMS, WhatsApp Business API, RCS Messaging, Email Solutions, SMPP Connectivity, and HTTPS APIs — must strictly adhere to these Sender Rules & Regulations. Non-compliance may result in immediate suspension of sending privileges and carrier-imposed penalties.

1. Consent-Based Communication & Anti-Spam Policy

Unsolicited business messaging degrades user trust and harms carrier routing networks. Senders must enforce a strict consent-driven workflow:

Prior Express Opt-In: Senders must obtain prior express consent from recipients before sending any promotional messages. Consent cannot be inferred, bundled, or purchased from third-party lists.
Explicit Consent Documentation: Senders must maintain clear records of how and when consent was gathered (e.g., opt-in timestamp, website checkbox, sign-up logs) and make these records available for audits within 24 hours of a Bluemessaggio request.
Quiet Hours: Promotional campaigns must only be transmitted during localized daytime hours (typically between 9:00 AM and 9:00 PM local recipient time) to respect customer privacy and comply with regulatory norms.

2. Opt-Out and Unsubscribe Requirements

Every business communication channel must feature a simple, clear, and functional opt-out mechanism:

SMS Opt-Out: Senders of promotional SMS campaigns must include standard opt-out keywords (e.g., "Reply STOP to cancel" or a valid opt-out URL link) at the end of every marketing text.
WhatsApp Opt-Out: Promotional WhatsApp template messages must include a clear, interactive quick-reply opt-out button (e.g., "Opt-out" or "Unsubscribe") to allow users to refuse future communications with a single tap.
Email Solutions: Senders using our Email Solutions must configure domain-level headers (List-Unsubscribe) and include an easily accessible, single-click "Unsubscribe" link in the footer of every commercial email.
Immediate De-registration: Once a recipient opts out, the sender must remove the recipient's phone number or email from all active outbound campaigns within 24 hours.

3. SMS Carrier & Regulatory Compliance (TRAI & DLT)

For senders routing Bulk SMS, transactional alerts, or OTP campaigns within regions requiring strict telecom registration (such as TRAI regulations in India):

DLT Registration: Senders must register their business entity, headers (Sender IDs), and content templates on an approved Distributed Ledger Technology (DLT) portal of local telecom operators.
Template Binding: Every outbound SMS must exactly match a pre-approved DLT content template, including header prefix mapping and designated variables (`{#var#}`). Messages failing DLT scrubbers will be rejected at the gateway level.
Sender ID Integrity: Sender IDs (Headers) must represent the sender’s legal brand name or registered trademark. Generic, misleading, or spoofed Sender IDs are prohibited and blocked.
International SMS: Senders routing messages across international borders must comply with local country codes, local carrier restrictions, and registration requirements for foreign Sender IDs.

4. WhatsApp Business API & RCS Compliance

Communications routed through rich-messaging networks are subject to platform owner regulations:

Meta Policies: WhatsApp Business API users must strictly comply with the WhatsApp Business Policy and Commerce Policy. Prohibited items (e.g. tobacco, drugs, gambling) cannot be marketed.
Template Classification: Template messages must be categorized accurately under Utility, Authentication, or Marketing according to Meta guidelines. Intentional misclassification will lead to Meta blocking the template.
Quality Rating Checks: WhatsApp numbers and RCS profiles must maintain a "High" or "Medium" quality rating. If a sender's profile falls to a "Low" rating due to high user block/report rates, Meta/Google will throttle sending limits or suspend the business profile.
RCS Verification: Senders using RCS Messaging must verify their brand identity with Google/carriers and use registered Agent profiles with clear branding assets.

5. Promotional vs. Transactional Messaging

Senders must logically segment their messaging traffic to prevent service disruption:

Transactional Messages: Used exclusively for critical notifications, one-time passwords (OTP), shipping alerts, and order confirmations. These messages bypass DND (Do Not Disturb) restrictions in most regions, provided they match transactional templates.
Promotional Messages: Marketing broadcasts, special offers, and discount codes. These are subject to strict opt-in checks and must respect national DND registries. Attempting to disguise promotional content as transactional (e.g. adding coupons to an OTP template) will result in immediate gateway suspension.

6. API Security, SMPP, and Technical Integrity

To secure our server infrastructure and prevent API hijackings:

API Credentials: HTTPS API keys and SMPP credentials must be kept secure. Do not expose keys in client-side code repositories or public forums.
Rate Limit Compliance: Senders must respect API rate limits. Flooding the gateway with un-throttled requests that return HTTP `429 Too Many Requests` status codes is considered abusive behavior.
Production Server Load: Senders must coordinate high-volume SMPP campaigns with the Bluemessaggio infrastructure team. Load testing or stress testing production endpoints without explicit approval is strictly prohibited.

7. Prohibited Content Categories

The transmission of messages containing the following categories of content is strictly prohibited on the Bluemessaggio platform:

Phishing & Fraud: Unsolicited messages claiming to represent banks, utility providers, or retail brands designed to harvest user credentials or personal data.
Illegal Substances & Goods: Marketing of illicit drugs, prescription pharmaceuticals without authorization, weapons, ammunition, or regulated explosive items.
Unregulated Financial Services: Cryptocurrency promotions, high-interest microloans, unregistered payday loans, and multi-level marketing (MLM) schemes.
Adult & Hate Content: Sexually explicit material, offensive content, harassment, hate speech, or harassment targeting race, religion, gender, or sexual orientation.
SHAFT Content: Content promoting Sex, Hate, Alcohol, Firearms, or Tobacco, unless restricted by carrier approvals, age gates, and regional regulations.

8. Abuse Monitoring, Suspension & Account Termination

Bluemessaggio employs automated anomaly detection and manual security audits to catch spam and unauthorized campaigns. Senders will be subject to account review or immediate suspension under the following circumstances:

High Bounce Rate: Any outbound campaign producing a hard bounce rate greater than 5.0% (for email or SMS) will trigger an automated sending hold for audit.
Spam Complaint Threshold: Spam complaint rates exceeding 0.1% (1 complaint per 1,000 messages) on WhatsApp or email channels will result in immediate campaign suspension.
Carrier Penalties: Senders are responsible for any fines, carrier penalty fees, or legal damages passed down by telecom operators or regulators (e.g., TRAI, Meta) due to spamming or non-compliant template routing on the sender's account.
Zero Tolerance: Phishing, brand spoofing, or spamming bank OTP templates will lead to immediate, permanent termination without refund, and credentials will be reported to telecom authorities.